Windows 10 1803 Update Error 0xc1900101

The show-hide utility only blocks for 35 days you have to run it once a month, I wait a few months and the try to update to 1803 so far no luck sticks at 43%

That's the thing, since Windows 10's inception it has been an up & down affair for me. One Feature Update may install fine (maybe the next) but then it gets out of sync and all hell breaks loose. For example, two of my PCs accepted 1607 then failed miserably w/1709, both required a wipe because the update incapacitated both machines. Then 1803 installed fine on both. Have several other computers that have been all over the map too.

Might have to try your suggestion to prevent my machines from updating but there really shouldn't be the need to do that if MS changed their ways, again never going to happen. And that is exactly why, if I need a Windows PC, we are reverting back to Win7. At least the user has the option to install updates, or not.

I have given up trying to update, Ver. 1709 is just fine. I had to update from Ver. 1607 because after many failed attempts my Laptop would not revert to the previous operating system. I had to reformat my HD and use an ISO to install Ver. 1709. As I have good backups I didn't lose any personal files, but it's a tedious process. I use this to prevent my Laptop from trying to update:

download/wushowhide - Microsoft Community

My Laptop is a HP ENVY 17t-3200 CTO  A6U49AAR with a intel i7 1st. Gen. I have a backup Dell Laptop which mirrors my HP it's slow compared to my HP. but I use it to keep my HP running. I used to design AV rooms for a company in NY but now I am retired so I don't care. But it bugs me that Win-10 has these problems. There again is the problem, you would think MS could come up with an answer.

The problem is, there is no concise answers when it comes to errors if an update fails to install. I've had errors that mirrored many others yet their resolves rarely ever seemed to be mine. So one can try applying fixes yet there's no guarantee they'll hit pay-dirt. And IMO it'll more than likely turn into a cat-n-mouse game with the end results being a complete wipe anyway.

Have had several computers over the course of my dealings w/Windows 10 that were wiped to get an update installed because of the "failed loop", and minimal use afterwards. Along comes the next Cumulative Update and guess what? Yup you guessed it, same friggin' scenario. So what is MS doing as computers were working fine prior and seemed supported by previous update (once we got it installed)? Seems like they are always making changes to something that affects successful installs yet it's like pulling hen's teeth trying to figure out what these "something's" are.

I'll find a choice if need be because I refuse to let MS control me. Either we'll revert back to Windows 8.1 or earlier, MAC, or Linux. Been doing so already w/productivity ramping up and our stress levels going down. All I can say is "so much for Microsoft's attempt at advancements in technology" as it ain't working out too well in my opinion.