This suggestion is a perfect example of what's wrong with the majority of software we are trying to use.
Basically, Badunit suggests I "try something" with no clue whether it will work, what the ramifications of doing so are, or any idea why it will work. Even though
our computers are incredibly fast and do literally billions of things in a second, that doesn't mean it's magic or that there is some uncertainty about what will happen.
DON'T JUST TRY STUFF AND SEE IF IT WORKS!!!!
Here's why:
- How could you possibly test every scenario in every program, even just the important ones, to see what the effect of "trying something" could be? You can't, so you may get unpredictable behavior later.
- Because you aren't aware what any of this stuff is doing, you don't know what may be going on without any indication,. Data corruption??? Who knows.
- Even if you are brave, and are willing to "just try it", you can relatively easily get yourself in a situation where the environment becomes a mess and doesn't work, hangs, or crashes. Yes, even from deleting the file. It can happen. If you don't make a backup of your system and test that backup method regularly so you know it works, you might be rebuilding your PC.
- You are letting the software author off the hook for documentation he/she should have provided.
I've been developing software since 1978 and I've watched as the quality of applications has slid. Microsoft and Apple write bloated, undocumented, relatively unstable code that only functions as it does because of the speed and efficiency of the hardware masking it.
Badunit even hints that he knows this because he wants me to post how it went. I respect that, and I would happily share any information I get about this process. But, I use this system and I'm not about to make it a guinea pig for the incompetent software developer who neglected to document their software sufficiently to troubleshoot it.
STOP THE MADNESS!!! STOP ACCEPTING THIS AS A VIABLE TROUBLESHOOTING METHOD AND INSIST THAT SOFTWARE COMPANIES DOCUMENT THEIR SYSTEMS!!!
We shouldn't have to do their job for them on our important systems. One of the reasons Apple has an edge on Microsoft is that they have a relatively controlled operating environment. Most software and hardware in an OS X environment comes from Apple and there are strict rules about how to code into the environment. The downside is that you are really at their mercy to fix it.
In this case, Apple has little incentive to make this easy to troubleshoot because they'll tell you it works better on a Mac so you should buy one. But if there IS an Apple guy on here who would be willing to share, could you give us some concrete technical information on ubd.exe, distnoted .exe and iCloudServices.exe and how they work together so that we can troubleshoot and/or make resource decisions?