KB5034203 is a hot mess!

After installing it my laptop was taking about 15 minutes to fully load everything. Normally takes about 10-12 seconds. I immediately uninstalled the update but that did not solve the problem recently created. I had to use system restore to restore the laptop to normal rapid boot-up and everything loaded. For some reason system restore took almost an hour. Thinking perhaps this was some kind of fluke I tried to install the update again and the same thing happened although this time system restore only took about ten minutes.

I am blocking all updates for the maximum 35 days and will probably renew for another 35 days. Perhaps a newer update will work.

22H2 19045.3930

Berton said:

Not having any issues on Win10 Pro with KB5034203 installed on Notebook on 1/25/2024 and Desktop on 1/25/2024. Desktop has an HDD drive and Notebook has an NVMe drive.

So what you are telling me is the update does not cause failure 100% of the time. That doesn't mean much because not very many updates are that bad! Why this particular update is a problem with my laptop I have no idea. Never had this problem with previous updates. My Acer doesn't have anything out of the ordinary in its configuration and no sign of hardware failure.

- - - Updated - - -

Try3 said:

Perhaps there's some guidance available in
KB5034203 Windows 10 Cumulative Update Preview build 19045.3996 (22H2) - TenForumsNews


Denis

I am afraid I did not find anything useful.

Berton said:

When seeing issues some things I do, first is to run Error Checking on the Boot/System drive, second is to Optimize [defragment] the drive and assure there's sufficient free space on the drive, I prefer at least 20% be available. On HDDs the Optimize/Defrag moves all the parts of a file close together so the read/write heads don't have to search as much to load a file, improves performance, SSDs don't need that as they have no moving parts.

I also have to keep in mind with working with clients that the only time 2 or more computers are alike is when still on the shelf before being sold, after they have been set up something will be different between them such as when a program is installed so when updates come along there may be an effect [good or bad] on one that won't be seen on others. Sometimes it is a program that causes issues, important to note what it is.

And if having a problem with an update there's always the Feedback Hub to let Microsoft know about issues with updates so they can fix them since we volunteers don't know when or even if Microsoft follows support forums. The more reports they receive maybe the quicker the fix.

SSD and it gets optimized regularly. Freespace available: approximately 65%. Yes something is different on my laptop compared to the person who reported no problem with the update. There have been no new programs installed for the last few updates. There are no programs that I would suspect of being beta or flaky. The hard drive shows no error and with the previous version of windows and system restore having been run everything is rock solid. I have to say something is wrong with the update -- who knows what. In the fairly distant past I have had problems with certain updates and I uninstalled them and blocked updating as long as I could and a newer update would install with no issues.

I should have tested by starting in safe mode -- didn't even think of that at the time -- MY BAD! I don't think I want to go through the whole experiment again at this time though.

Guess I will give them feedback.

idgat said:

It is not uncommon for some updates (Microsoft/Windows or otherwise) to be co-incidental with system or hardware failures - quite often the update is simply the tipping point of something the might have been going to happen eventually, update or not.

One of the most common thing is disk failure - updates use/need certain address blocks on the drive which are currently unused but unbeknownst to a normal operating system are failing/failed. But the list goes on and on. Similarly, the update could involve failed/failing system software components

Obviously again, another possibility is a simple borked update process (through no faut of the user)

Obviously, the list is endless and the options open for a solution are endless

You could run a check on the drive (use freebie CrystalDiskInfo)

For mine, me, I would whip out the old drive (keeps it intact, it can always be put back in fully operational - failed update aside - and try a new drive with a clean install and all updates, just to see what happens

It is a laptop so not quite that simple to just throw a new SSD in there. A new drive with clean install would not really prove what the problem is. Could be a weird bug in the update somehow incompatible with something in my software somewhere. I am 98% confident that a later update will work fine, just as reinstalling the previous update along with system restore to repair whatever else was happening worked both times after installing the latest update. So I delayed updates 35 days. It was an optional preview update anyway. In 35 days I will see what newer update is available and try that. As I think I had explained, I have had to do this in the past and then had no problems for quite some time. The SDD HAS been checked and shows no errors.