What is SweetPacksUpdateManager.exe?
SweetPacksUpdateManager.exe is part of SweetPacks Update Manager and developed by SweetIM Technologies Ltd. according to the SweetPacksUpdateManager.exe version information.
SweetPacksUpdateManager.exe's description is "Update Manager for SweetPacks"
SweetPacksUpdateManager.exe is digitally signed by SweetIM Technologies Ltd.
SweetPacksUpdateManager.exe is usually located in the 'C:\Program Files (x86)\SweetIM\Communicator\' folder.
Some of the anti-virus scanners at VirusTotal detected SweetPacksUpdateManager.exe.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
Vendor and version information [?]
The following is the available information on SweetPacksUpdateManager.exe:
| Property | Value |
|---|---|
| Product name | SweetPacks Update Manager |
| Company name | SweetIM Technologies Ltd. |
| File description | Update Manager for SweetPacks |
| Internal name | SweetIM |
| Original filename | SweetPacksUpdateManager.exe |
| Legal copyright | Copyright © 2008 SweetIM Technologies Ltd. |
| Private build | 001 |
| Product version | 1.1.0.8 |
| File version | 1, 1, 0, 8 |
Here's a screenshot of the file properties when displayed by Windows Explorer:
| Product name | SweetPacks Update Manager |
| Company name | SweetIM Technologies Ltd. |
| File description | Update Manager for SweetPacks |
| Internal name | SweetIM |
| Original filename | SweetPacksUpdateManager.exe |
| Legal copyright | Copyright © 2008 SweetIM Technologi.. |
| Private build | 001 |
| Product version | 1.1.0.8 |
| File version | 1, 1, 0, 8 |
Digital signatures [?]
SweetPacksUpdateManager.exe has a valid digital signature.
| Property | Value |
|---|---|
| Signer name | SweetIM Technologies Ltd |
| Certificate issuer name | VeriSign Class 3 Code Signing 2010 CA |
| Certificate serial number | 5e3bf2b52da9ea7f1b539a7f018f4ec6 |
VirusTotal report
4 of the 49 anti-virus programs at VirusTotal detected the SweetPacksUpdateManager.exe file. That's a 8% detection rate.
| Scanner | Detection Name |
|---|---|
| DrWeb | Adware.SweetIM.19 |
| ESET-NOD32 | a variant of Win32/SweetIM.F |
| Malwarebytes | PUP.Optional.SweetIM |
| VIPRE | Sweetpacks/SweetIM (fs) (not malicious) |
SweetPacksUpdateManager.exe removal instructions
The instructions below shows how to remove SweetPacksUpdateManager.exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the SweetPacksUpdateManager.exe file for removal, restart your computer and scan it again to verify that SweetPacksUpdateManager.exe has been successfully removed. Here are the removal instructions in more detail:
- Download and install FreeFixer: http://www.freefixer.com/download.html
- Start FreeFixer and press the Start Scan button. The scan will finish in approximately five minutes.
- When the scan is finished, locate SweetPacksUpdateManager.exe in the scan result and tick the checkbox next to the SweetPacksUpdateManager.exe file. Do not check any other file for removal unless you are 100% sure you want to delete it. Tip: Press CTRL-F to open up FreeFixer's search dialog to quickly locate SweetPacksUpdateManager.exe in the scan result.
C:\Program Files (x86)\SweetIM\Communicator\SweetPacksUpdateManager.exe 
- Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the SweetPacksUpdateManager.exe file.
- Restart your computer.
- Start FreeFixer and scan your computer again. If SweetPacksUpdateManager.exe still remains in the scan result, proceed with the next step. If SweetPacksUpdateManager.exe is gone from the scan result you're done.
- If SweetPacksUpdateManager.exe still remains in the scan result, check its checkbox again in the scan result and click Fix.
- Restart your computer.
- Start FreeFixer and scan your computer again. Verify that SweetPacksUpdateManager.exe no longer appear in the scan result.
Folder name variants
SweetPacksUpdateManager.exe may also be located in other folders than C:\Program Files (x86)\SweetIM\Communicator\. The most common variants are listed below:
- C:\Program Files\SweetIM\Communicator\
- C:\Archivos de programa\SweetIM\Communicator\
- C:\Programme\SweetIM\Communicator\
Other files also named SweetPacksUpdateManager.exe
SweetPacksUpdateManager.exe (64 votes)
Hashes [?]
| Property | Value |
|---|---|
| MD5 | 84a878d2d4a84cc73d53733f80fb57ce |
| SHA256 | b9b2c5e4b85c55de1aa4f02b30a7113c3013bfcad04366f9f188fef7865e77df |
Error Messages
These are some of the error messages that can appear related to sweetpacksupdatemanager.exe:
sweetpacksupdatemanager.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
sweetpacksupdatemanager.exe - Application Error. The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX". The memory could not be "read/written". Click on OK to terminate the program.
Update Manager for SweetPacks has stopped working.
End Program - sweetpacksupdatemanager.exe. This program is not responding.
sweetpacksupdatemanager.exe is not a valid Win32 application.
sweetpacksupdatemanager.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.
What will you do with the file?
To help other users, please let us know what you will do with the file:
What did other users do?
The poll result listed below shows what users chose to do with the file. 100% have voted for removal. Based on votes from 1 user.
| Votes | |||
|---|---|---|---|
| Keep | 0 % | 0 | |
| Remove | 100 % | 1 |
NOTE: Please do not use this poll as the only source of input to determine what you will do with the file. Only 1 user has voted so far so it does not offer a high degree of confidence.
Comments
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
No comments posted yet.