1709 Failed

I have an older laptop that was upgraded to Windows 10 from W7. The last upgrade, 1709, failed. I paid not attention since it is a spare system and updates to the new releases usually mess up a few dozen things anyhow. That is Microsoft. But have a few spare moments I went to see if I could remedy the problem. Solution, just go to Google, NEVER and I mean NEVER go to Microsoft. There on Google I found thousands of people with the same problem.

Then, Microsoft has some "Engineer" telling folks how to remedy this. The best part of the response was:

Method 4:

1. Open registry editor by running regedit.exe
2. Back up the registry first before making changes to it
3. Navigate to HKLM\System\CurrentControlSet\Control\Session Manager
4. Check if PendingFileRenameOperations exists under the Session Manager key
5. If it exists, please remove it
6. Restart computer and check if issue persists

If the issue persists,  please follow the steps below and send the CBS log to the e-mail address in private message.

1. Rename the CBS.log(%systemroot%\Logs\CBS\CBS.log) to CBS.old
2. Manually update the computer again and restart computer if needed
3. Send the new generated CBS.log.

If anything is unclear, please feel free to let me know.

 Now for those of you who would dare to change a Registry, let me tell you, it is the holy of holies in Windows OS. It is where Microsoft places millions of landmines. Make one small change and not all others required and CRASH! Yep, down goes the machine and unrecoverable.

So my question is: where is the Class Action suit lawyers in this case. It has likely taken more productivity from our economy than anything Congress could screw up! 

If Microsoft were a real company in a competitive market they would not last a femto second. They would have to remedy this. But alas, we all know where this is going. No where. Pity!