![]() ![]() That means, if you simply trash the app and think the removal is done, you’re wrong. Additionally, some apps may create supporting files, caches, login files scattering around the system directory. General knowledge: Once installed, an app is typically stored in the /Applications directory, and the user preferences for how the app is configured are stored in ~/Library/Preferences directory. If you have no clue how to do it right, or have difficulty in getting rid of MozyHome 2.16.1, the removal solutions provided in the post could be helpful. ![]() This page is about how to properly and thoroughly uninstall MozyHome 2.16.1 from Mac. ![]() Removing applications on Mac is pretty straightforward for experienced users yet may be unfamiliar to newbies. Of course, if you have more than 10 or 20 GB of backup data, that week-long window of functionality is less time than it takes to make a successful full backup.Perfect Solutions to Uninstall MozyHome 2.16.1 for Mac Did so, it worked for less than a week before the same problems came back. Once I finally got through to a "Mac" support person, the troubleshooting advice was to wipe out everything and start from a clean install. I clearly described a problem with the Mac OS X version and they responded with Windows troubleshooting steps. Uninstalling again.ĭon't tell me to contact Support - last time I tried to work with them was a nightmare. ![]() I opened Activity Monitor and found that the MozyHomeBackup process was using about 100% CPU (maxing out one of my MacBook Pro's dual cores), heating up my Mac when it was supposed to be doing nothing! Force Quit that. And, my fans kicked into gear once it showed that it HAD stopped. Oh, when I clicked Stop it took several minutes to do so. Find something else would be my recommendation - it's clear to me that whoever is developing this software cannot build a product that runs well on Macs. In short, still the same slow, bloated mess. The Console.app shows the following error multiple times: CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length 7, native = no) After examining files for a half hour, it showed that it was starting a backup, which involved another ten minutes of "Communicating with server." MozyHome.app crashed the first time I tried to open it. I have mine throttled as far as upload, but that didn't stop it from immediately attempting a backup process. Still _KILLS_ the performance on your computer. Just tried this new version after having it not installed for a couple months (and totally non-functional for a couple before that!). Fixed an issue for some users that prevented the proper rotation of the backup software log files.Fixed an issue for users of MozyPro or MozyEnterprise that caused the backup process to fail if the administrator changed the encryption key type in the default configuration and also selected the option to enforce changes.Fixed an issue that caused the backup software in some situations to display incorrect values for file sizes and the number of backed up files.Fixed an issue for users of MozyPro or MozyEnterprise that caused the Use a personal key option to be available when selecting an encryption key option, even though this option was disabled by the administrator.The characters were, carriage return (\r), line feed (\n), and trailing spaces. Fixed an issue that caused the backup process to fail if you backed up a file with certain special characters in the filename and then deleted the file.Fixed an issue that prevented the restore window from opening if you clicked Restore Files within the Summary tab and then clicked somewhere outside the backup software before the restore window opened.Note: Now requires a 64-bit Intel processor. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |