New update 1607 will not install

I have had it with windows 10. I run a home business and my first encounter was that I told the update tool not to install windows 10. Then one morning I went to get ready and when I got back it had installed without my permission. I decided to try it an it has run perfectly through many small and major updates until 1607.

I hangs on the second reboot. Again I did not ask for this update and I have wasted several hours screwing around waiting for a spinning circle for over two hours before deciding it was not going to install. It finally returned me back to my previous Windows 10 version.

I wrote the error code and called Microsoft who said my machine was not Wiindows 10 compat. and their official response on that error was to take no action and if I had purchased Windows 10 my money would be refunded.

How can my system work for months and now be nt Windows compat? Do they not know people use their computers to run business and to force an update to to a non compat system costs people money in lost productivity? Or do they not care which is more like it.

I know on this forum the WIndows Butt-Boys will tell me all the reasons this is a good thing. So take your best shot. But who is going to compensate me and others for lost time and the resulting loss of income?

Fortunately I had an image of my Win 7 load and more time wasted in having to put this back on.

Thanks Microsoft for more great software and customer support.

And before you ask I have no Malware, uninstalled antivirus, tried ISO and media creation tool etc etc etc. After three tries strike out!

There have been many postings here (including mine) about problems completing the Anniversary Upgrade (AU). The bottom line seems to be this: either the upgrade works for your system, or it doesn't. If it works, then you are good to go with it. Most users seem to have to make some small adjustments to minor things, but overall if the AU installs and runs, your system is OK.

On the other hand, if the AU fails there is a very low likelihood that you can ever get it to work properly. In my case it left me with an unbootable system. After doing some unusual things (like rearranging the partitions on my boot drive) I was able to get it to restore my prior Win10 Build 1511 system after the AU failed, but that was the best I could ever do. So I have given up trying the AU and will simply wait for the next upgrade that will hopefully work better.

I am not the only one in this category. And yes, it is disappointing that there is no reliable way of identifying what the causes of AU failures are, or how to fix them. But it is what it is. I have several offline disk images of my current Build 1511 system that has been running solidly for quite a while, so no matter what MS does in the future I know I can restore something that works.

Welcome to the real world.