MS-DEFCON 4: A “sort of” quiet February

Topic

New Reply

ISSUE 21.09.1 • 2024-02-27 By Susan Bradley The February updates have generally been well behaved, with one major exception: gamers. Otherwise, things
[See the full post at: MS-DEFCON 4: A “sort of” quiet February]

Susan Bradley Patch Lady/Prudent patcher

9 users thanked author for this post.

Perq, jburk07, L95, CADesertRat, deuce120, DKThompson, DLivesInTexas, lmacri, abbodi86

Reply | Quote

Replies

On that advice, I decided to bite the bullet and move from Windows 11 22H2 to 23H2. All set with book and Whiskey, it was so fast it seemed it must have hit a problem and stopped. Winver confirms 23H2 and I still only had two sips of Whiskey.

Reply | Quote

At least as of yesterday, KB5034441 was still being pushed out via Windows Update.

The system I was working on tried to install but couldn’t (too small RE partition and it was the first partition on the drive).  Blocked further tries.

Reply | Quote

Microsoft confirmes Windows 11 KB5034765 fails to install with error code 0x800F0922

See:
https://www.bleepingcomputer.com/news/microsoft/windows-february-2024-updates-fail-to-install-with-0x800f0922-errors/

 

Also See:
https://www.neowin.net/news/microsoft-confirmes-windows-11-kb5034765-fails-to-install-with-error-code-0x800f0922/

1 user thanked author for this post.

MrToad28

Reply | Quote

Yes, I just encountered that issue on my Win 10 22H2 laptop – KB5034763 (my error originally listing the wrong KB – sorry) would not install.

I use WUMGR and have never had an issue. It downloaded the update “successfully” and when I restarted, it went through an attempt to install and then a loop saying “Couldn’t complete installation, undoing changes, trying again” – twice and then finally rebooted. The update screen seemed to stall at about 94% and then said it couldn’t install.

It also did a weird thing to WUMGR when I  tried to see if the update indeed did install or fail. When I started WUMGR again, the info was blank – no record of any updates being installed – no history, and when I checked again for updates, it then listed ALL of the many I had hidden over the time I’ve used it, plus KB5034763.

I tried it all a second time – same thing. So I rolled back my Macrium backup and now things appear back to normal. WUMGR shows everything and all seems OK.

Since I use WUMGR, I never got any error messages except the ones saying that it couldn’t complete the install and was undoing changes. This update will not install on Win 10 22H2. I have another Win 10 22H2 laptop that I am not going to try to install this on – waiting to see if there is a solution.

 

3 users thanked author for this post.

Perq, MrToad28, jburk07

Reply | Quote

February 13, 2024—KB5034765 (OS Builds 22621.3155 and 22631.3155)
Windows 11 version 22H2, all editions Windows 11 version 23H2, all editions

It looks like KB5034763 is the February Cumulative update for Windows 10 22H2

The question is why was KB5034765 offered to you on a Win 10 system?

 

 

1 user thanked author for this post.

LHiggins

Reply | Quote

JC Zorkoff wrote:

It looks like KB5034763 is the February Cumulative update for Windows 10 22H2

Yes, correct I copied the wrong KB number. It was KB5034763.

Too many notes – LOL!

Sorry about that.

Reply | Quote

Is this not a Win 11 issue? How did it happen on your win 10 system?

Reply | Quote

Yes, KB 5034765 is a Win 11 issue. I mistyped the KB in my original post, now corrected. The right one that didn’t install on the Win 10 laptop is 5034763, as I noted above

LHiggins wrote:

Yes, correct I copied the wrong KB number. It was KB5034763. Too many notes – LOL! Sorry about that.

So it seems that there are issues with 5034763 on Win 10 as well – no solutions but several questions on various sites.

LHiggins wrote:

So… should we just hide this KB5034763 until whatever issue that prevents it from installing is fixed?

Reply | Quote

Thank you for clarifying for me. Yes there are some rather strange issues. Some will not install like in your case, others have missing taskbars. There seems to be no consensus on whats causing it, I see everything from EU compliance changes to the game controller issue suggested in the Defcon update here. As this is a very serious issue for me I am now considering remaining paused until the march updates. I can wait until the 16th, but that is of course also a risk for another bad update. Windows update is headache inducing as usual.

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

… It also did a weird thing to WUMGR when I tried to see if the update indeed did install or fail. When I started WUMGR again, the info was blank – no record of any updates being installed – no history, and when I checked again for updates, it then listed ALL of the many I had hidden over the time I’ve used it, plus KB5034763.

LHiggins wrote:

So… should we just hide this KB5034763 until whatever issue that prevents it from installing is fixed?

Hi LHiggins:

Like Susan, I’m not aware of widespread issues with installation of the Win 10 KB5034763 cumulative Quality Update (OS Build 1904x.4046) that was released on 13-Feb-2024, and there’s nothing about installation failures mentioned in the Known Issues section of the release notes <here> for KB5034763. In contrast, the release notes <here> for the Win 11 KB5034765 cumulative Quality Update of Feb 2024 (OS Builds 226xx.3155) were recently revised to provide a possible workaround if installation of this Win 11 update fails to run to completion.

Before you rolled back your system with Macrium Reflect did you check your installed updates at Control | Programs | Programs and Features | View Installed Updates to see if KB5034763 had actually installed? It’s always possible that the “Couldn’t complete installation, undoing changes…” message you saw after restarting your system was for another update like the problematic KB5034441 WinRE Parition update released last month on 09-Jan-2024 that is still failing to install correctly on many Win 10 machines – see camelia’s 13-Feb-2024 Error KB5034763 do not let me install KB5034763 How do I fix it? in the TenForums where this was the case.

If the problem occurs again the next time you try to install KB5034763 with WUMgr there are a few suggestions in the MiniTool article What if Windows 10 KB5034763 Fails to Install? Solve It in 6 Ways! that might help. I don’t use WUMgr so I don’t know if the first suggestion to run the built-in Windows Update troubleshooter would provide any meaningful information while WUMgr is actively managing your updates (or might even cause some odd behaviour if it tries to “repair” Windows Update components managed by WUMgr), but some of the other suggestions (e.g., running sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth scans in an elevated command prompt with Administrator rights to check for damaged system files, manually installing KB5034763 for Win 10 v22H2 using the standalone .msu installer available <here> on the Microsoft Update Catalog, etc.) might  solve your problem.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

jburk07

Reply | Quote

Hi Imacri and thanks for the information. It is puzzling and raises a few questions for sure.

Here’s what I have done so far.

lmacri wrote:

Before you rolled back your system with Macrium Reflect did you check your installed updates at Control | Programs | Programs and Features | View Installed Updates to see if KB5034763 had actually installed?

I didn’t check there, but in WUMGR that update shows in the update history twice as “aborted” and it is still being offered there and in Windows Update listing itself, so I am pretty confident that it didn’t install. And I didn’t try to get the .NET update –  KB5034685 – yet, but I may try that first to see if it will download and install.

lmacri wrote:

If the problem occurs again the next time you try to install KB5034763 with WUMgr there are a few suggestions in the MiniTool article What if Windows 10 KB5034763 Fails to Install? Solve It in 6 Ways! that might help.

Thanks! I did find that article, and I ran the Troubleshooter – which showed no problems. I haven’t gone further with the other suggestions there yet.

I also posted this question at the MS community, where I did find several other questions about this KB causing issues – especially not installing. It matches the behavior of KBKB5034765 in Win 11 – so the reply I did get from one of their moderator agents was to delete the hidden folder C:$WinREAgent – which was created yesterday 2/27/24 when I was trying the update – and to reboot and try the update again.

I haven’t done this yet as I was waiting for the answers to a few questions about doing that – like why is that folder still there if I rolled back to the backup created BEFORE I attempted this update?

I guess I am also wondering if I needed to have last month’s KB5034441 to be able to successfully download this one. I never got that one as per Susan’s advice – didn’t even try that.

I also wonder if my AV software – ESET – could be causing the problem as the minitool article suggests, so next time I try it, I am going to disable that and probably Malwarebytes too just in case.

Once I hear back from MS about the C:$WinREAgent file questions, I’ll probably try it again and if it still fails, I guess I can try a few other suggestions in the minitool article as well.

I am reluctant to do too much to make significant changes to my system, since other than this issue, it has always worked well and gotten updates with out any problem. If I can’t get this to install and just hide it in WUMGR what is the downside of that? Can it just be skipped until next month?

And I have another Win 10 laptop that I am not going to even attempt to update until I get this sorted out!

Thanks for the help – I appreciate all of the information rather than just “no one else has had this problem” – which according to this reply in the MS community to the same question, which was posted mid-Feb, is not the case:

Many people report problems with the update, there is no problem with your system, you should wait for the developers to solve the problems with this update, the best alternative is to pause the update for 7 days.

In a Feb 27 reply in that posting, the problem still exists on 2/27, so I guess I am just one person who has encountered it.

I will post back after I try the update again and let you know if deleting the C:$WinREAgent is the solution in case anyone else has this problem.

Thanks again and have a great day!

LH

 

 

1 user thanked author for this post.

jburk07

Reply | Quote

LHiggins wrote:

I guess I am also wondering if I needed to have last month’s KB5034441 to be able to successfully download this one. I never got that one as per Susan’s advice – didn’t even try that.

Hi LHiggins:

Sorry, I don’t have a definitive answer since Windows Update successfully installed the KB5034441 WinRE update on my Win 10 Pro v22H2 laptop with my other Jan 2024 Patch Tuesday updates, even though I did not have 250 MB of free disk space in my WinRE partition.  See my 16-Jan-2024 post # 2628138 in Susan Bradley’s Ready for the new patching year? for further details.

However, I don’t know of any prerequisite updates that need to be applied first before the Win 10 Feb 2024 KB5034763 cumulative Quality Update will install [unless the Servicing Stack Update (SSU) v19045.3989 that is bundled with the KB5034763 installer is considered a “prerequisite”].  I also would have expected to see a lot more Win 10 users reporting problems with the installation of KB5034763 if last month’s KB5034111 WinRE update had to be installed first, given how many Win 10 users had KB5034441 fail to install in Jan 2024.

LHiggins wrote:

I also posted this question at the MS community…It matches the behavior of KBKB5034765 in Win 11 – so the reply I did get from one of their moderator agents was to delete the hidden folder C:$WinREAgent …

Your Event Viewer should have logged an event that showed the error code generated when your Win 10 KB5034763 update failed (e.g., like the error code 0x800F0922 that most Win 11 users are seeing logged in their Event Viewer if their KB5034765 update fails).

For example, I found one topic in the MS Answers board at windows10 KB5034763 update fail where the OP strpy had an error code 0x80073bc3 logged when KB5034763 failed to install on their system, which supposedly suggests “issues with boot-related files or insufficient disk space“. Unfortunately, that information was probably removed from your Event Viewer when you re-imaged your hard drive with Macrium Reflect.

Are you posting in the MS Answers forum at KB5034763 Won’t Install as user TN2012?
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

jburk07, LHiggins

Reply | Quote

Hi Imacri,

lmacri wrote:

Are you posting in the MS Answers forum at KB5034763 Won’t Install as user TN2012?

Yes, that’s me. Waiting for more info from the MS rep.

I tried to look in the event viewer, but it is probably a combination of I can’t find any reference to the error message and/or I don’t really know how to use it.

I believe the advice to delete the C:$WinREAgent was based on the error code from the Win 11 KB. That does look like a boot/disk space issue, but I am not sure that applies.

I’ll take a look through that topic you sent and see if anything might be relevant. I do have 323 GB of free space on my hard drive, and my internet connection is OK – never had any issues before.

Not sure where to go from here – I hate to try it all again and end up with the same issue, especially if it is a disk space issue, but I’m not sure how to check that. And as to any boot issue – I’ve never had one, so no idea if that could be the issue.

Thanks for the help. I will post back if I come up with anything.

LH

Reply | Quote

LHiggins wrote:

I will post back after I try the update again and let you know if deleting the C:$WinREAgent is the solution in case anyone else has this problem.

In case you haven’t yet tried to delete the $WinREAgent folder, I took a look inside it after installing this month’s Windows 10 22H2 update, and the folder itself has a sub-folder in it (labeled “Scratch”) that is completely empty. I’ve always deleted it after successfully installing the monthly updates and have never had a problem because of doing so.

So, take a look inside your copy and see if it’s indeed completely empty, including the sub-folder labeled “Scratch”. The best way to do this is to make sure that Explorer is set to show all hidden items AND to make sure that View options are set to show all protected operating system files (Folder Options>Click on the View tab>Under “Advanced settings” box scroll down and clear the check box labeled “Hide protected operating system files (Recommended)”). Now, go into the $WinREAgent folder and verify that it and the “Scratch” sub-folder are indeed empty. Once you’ve done so, please re-enable the hiding of protected operating system files by putting a check back in the box that you cleared a bit ago.

If the folder in question is indeed completely empty save for the sub-folder, you can choose to delete it if you wish and reattempt the installation of KB5034763 as you wish.

It’s good of you to not automatically follow that advice, of deleting the folder, because that is intended, obviously, for Windows 11 installation issues. I’m curious to hear what the MS rep in the Answers forum tells you to do at this point.

3 users thanked author for this post.

Cijan, jburk07, LHiggins

Reply | Quote

Thanks Bob99,

I am hoping to try the update again this morning after I get everything in order – backups and restore points made, etc.

Bob99 wrote:

I’m curious to hear what the MS rep in the Answers forum tells you to do at this point.

The MS rep said that deleting the file is one solution that may or may not work, but worth a try. He also said to try turning off the AV when doing the download and install, so I think I’ll try both of those things.

He also said:

Considering that the known issues don’t mention the update package you’re having problems with, if this doesn’t solve your problem, you may need to report the issue and wait for a fix from the development team.

So, if it still doesn’t work, I think I may just give up and hide it and wait till next month to see what develops. And report it to MS and see if they ever figure out a fix.

Will post back on the progress!

Thanks again for the info and encouragement!

LH

Reply | Quote

And now I can’t find that $WinREAgent folder. I have hidden files showing and it isn’t there. When I did see it earlier, the Scratch folder was empty, and I have restarted several times, so maybe it just was deleted in that process.

 

I am going to go ahead and try the update again anyway. Maybe just turning the AV off will help?

Reply | Quote

Just FYI…

The $WinREAgent folder is created/used during the standard Windows update process as a “temporary” storage location for the old versions of the files being updated.

If the update fails, it uses those files to roll back Windows to the previous version.

If the update succeeds, it deletes all those files.

However, for strange some reason (that probably only makes sense to Microsoft), it doesn’t remove the folder and sub-folder after deleting all the files?!?!

2 users thanked author for this post.

jburk07, LHiggins

Reply | Quote

Yes, after the failed update, I was surprised to find that file with the date of the attempt. Weird that it was there and now gone.

Will see what a new attempt does…

Reply | Quote

Given the WIN11 problem, I’m gonna use stop start delay strategy to push updates into next month on my Win11 laptop.

Reply | Quote

441 was somewhat fixed, at least when the recovery partition is at the end of the disk.

My notebook has a new partition 100mb larger, no single patch was installed apart the cumulative monthly. 3 reboot.

Reply | Quote

I am wondering, the disappering taskbar issue only happens if a controller is connected to the PC right? If I am understanding this correctly.

Reply | Quote

We have run into a problem installing 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

We have tried multiple times and keep getting the message, “There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643)”.

We are running:

• Windows 10 Pro
• Version 22H2
• Installed on 2/7/2023
• OS build 19045.4046
• Experience Windows Feature Experience Pack 1000.19053.1000.0

Reply | Quote

Hi, Susan,
Sorry if this is in the wrong place, I’m not sure how to post a new topic but the KB’s mentioned are also ones I’m not sure about regarding my subject..

As Microsoft warns us, this problem isn’t likely to go away..
Many of us have older computers running on Windows 10 or 11 and can not afford to buy new computers or wish to continue using our old ones productively even if that means never going on line with them again.

If we could maybe get a Forum column or M.S. Patch Updates warning entries going forward to learn which updates, moments, enablements or KB’s to not install if anyone figures out how to avoid those that triggers the system shutdown to never boot again, it would give us time to gather the resources to fund the new systems that we will need..
(probably many new ones as it looks like “Lather, rinse and repeat”
with all the new AI systems, upgrades and requirements looming on the horizon already..)

Thanks again for everything you you all do for us, I recommend AskWoody and paid accounts as often as I can to those that might benefit and receive thanks from most I have spoken to about it.
Seekr

Reply | Quote

So, no patch should ever cause a system to not boot.  Seriously.  I have older Windows 10 machines that run just fine.

If there is EVER an update that causes that for massive amounts of people you will see the site go to Defcon 1, I will have Will send out an alert and I’ll be freaking out.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I warn users against upgrading to Windows 11 unless their laptop fully passed all aspects of  the upgrade test. Even then they are told to check with the manufacturer for potential consequences.  Dell has a walkthrough ; HP has instructions; presumably every other major brand will have something. I know if you upgrade a fully compliant Dell to Windows 11 from 10, in some cases Dell no longer support the laptop with drivers updates. Dell advise Microsoft update update drivers in such cases.

First and foremost, anyone who upgrades should ensure BIOS is up-to-date. Maybe that’s second. Creating a bare metal image is also strongly advised.

1 user thanked author for this post.

Alex5723

Reply | Quote

So… should we just hide this KB5034763 until whatever issue that prevents it from installing is fixed?

Reply | Quote

https://support.microsoft.com/en-us/topic/february-13-2024-kb5034763-os-builds-19044-4046-and-19045-4046-f1c993e4-32b3-4cc8-947a-69e70ae124d5 That KB installs for the vast majority of people.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

OK – but it won’t install for me, so what should I do? There has to be some reason that it won’t – right?

Reply | Quote

I too am having a problem with KB5034763. It downloaded ok and appeared to install ok until time to reboot. After clicking on reboot, the computer went to the blue screen and said getting things ready, do not turn off your computer. After a bit it said restarting. Then the screen went blank and then into standby. The power button is still illuminated a steady white but nothing else appears to be happening. Light for SSD drive not on or flickering. Been this way for over an hour. I have not tried to manually restart with the power button or anything else. Sometimes I act too quick without thinking things out and make the situation worse. I wanted to see what others advised. This is a Dell refurbished computer that has run perfect since August 2022. It has a Intel Quad-Core i7-4790, 16GB RAM, 1TB SSD running W10 Pro 22H2. It is updated for January 2024. I did run File History and ran Back Up and Restore (win7) from control panel and made a full back up and disk image before trying to update. I have not installed or attempted to install KB5034441. Wushowhide indicated it was still hidden before I started the update attempt.

CT47   2024 03 03   11:23 pm

Reply | Quote

Kathy Stevens wrote:

We have run into a problem installing 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

This has been discussed lengthily after Jan. updates.
Hide KB5034441 or use some partition app to change Recovery partition size.

Reply | Quote

Alex5723

Yes, it was a problem after January updates and it remains a problem today.

Reply | Quote

It put my clock in Eastern time zone UTC-05 I’ve always been at UTC-08. The time zone was set to automatic after the update. I don’t know if it was set there prior to update and if I leave it there the time reverts to UTC-05. So the time zone is now turned off. I never had this issue before. Windows 10 Home 22H2

Reply | Quote

We have run into a problem installing 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

This is a known issue that started with the January updates.  It’s an update for the Recovery RE partition and Microsoft has not issued a fix yet.  It’s safe to ignore, but there are workaround options if you have the time for a deep dive.

https://www.askwoody.com/2024/kb5034441-and-kb5034440/

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

Updated and had no problems.

2024-02 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5034765)
2024-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5034467)
Windows Malicious Software Removal Tool x64 – v5.121 (KB890830)

Windows 11 Pro
Version 23H2
OS build 22631.5189

Reply | Quote

Is the warning that “Gamers using a controller on their Windows PCs may find that Windows Explorer fails to load the task bar after the installation of Windows 11 KB5034765” somehow connected to MS saying in the KB article that “This update addresses an issue that affects explorer.exe. It might stop responding. This occurs when you restart or shut down a PC that has a controller accessory attached to it“?

Does anyone know if disconnecting the controller before applying the update can help to avoid this issue?

Reply | Quote

WIN10 22H2  KB5034763 (cumulative) & KB5034685 (KB5034468 – .NET 3.5 and 4.8) no issues

1 user thanked author for this post.

jburk07

Reply | Quote

Just noticed that new installations of Skype and Calculator occurred, on at least one of our Windows 10 Pro computers, during the update process on 2/27/2024.

Reply | Quote

Kathy Stevens wrote:

Just noticed that new installations of Skype and Calculator occurred, on at least one of our Windows 10 Pro computers, during the update process on 2/27/2024.

Hi Kathy Stevens:

Do you mean that those apps were previously uninstalled and were unexpectedly reinstalled without your permission?

The apps you listed are Microsoft UWP (Microsoft Store apps) and, if installed, are automatically updated in the background by the Microsoft Store app, not Windows Update. I checked the library in my Microsoft Store app and both my Calculator and Skype UWP apps were updated today, and those updates were logged in my Windows Reliability Monitor (see attached images). If UWP apps updated on some of your computers at the same time that Windows Update was running it’s likely just a coincidence (i.e., because your system happened to be idle for a long period of time while you were waiting for your Windows Update session to run to completion).
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

Just noticed new installations of Microsoft OneDrive, Skype, Clock, Calculator, Phone Link, Media Player, and Spotify Music occurred, on one of our Windows 10 Pro computers, during the update process on 2/28/2024.

Reply | Quote

Susan Bradley wrote:

vast

KB5034763 installation failed for me too (also on Win10 22H2).

I recently used ViveTool to revert Windows Search search string format entry to the old (better) method by disabling the Windows ‘feature’ that changed it.

Could this be the problem, Susan Bradley? (If so I could re-enable the ‘feature’ and try again.)

LHiggins wrote:

Yes, I just encountered that issue on my Win 10 22H2 laptop – KB5034763 (my error originally listing the wrong KB – sorry) would not install.

I use WUMGR and have never had an issue. It downloaded the update “successfully” and when I restarted, it went through an attempt to install and then a loop saying “Couldn’t complete installation, undoing changes, trying again” – twice and then finally rebooted. The update screen seemed to stall at about 94% and then said it couldn’t install.

It also did a weird thing to WUMGR when I  tried to see if the update indeed did install or fail. When I started WUMGR again, the info was blank – no record of any updates being installed – no history, and when I checked again for updates, it then listed ALL of the many I had hidden over the time I’ve used it, plus KB5034763.

I tried it all a second time – same thing. So I rolled back my Macrium backup and now things appear back to normal. WUMGR shows everything and all seems OK.

Since I use WUMGR, I never got any error messages except the ones saying that it couldn’t complete the install and was undoing changes. This update will not install on Win 10 22H2. I have another Win 10 22H2 laptop that I am not going to try to install this on – waiting to see if there is a solution.

 

Moderator Edit: to remove HTML. Please use the “Text” tab when you cut/paste, or use “Paste as Text” from the menubar.

Asus N53SM & N53SN 64-bit laptops (Win7 Pro & Win10 Pro 64-bit multiboots), venerable HP Pavilion t760 32-bit desktop (XP & Win7 Pro multiboot), Oracle VirtualBox VM's: XP & Win7 32-bit, XP Mode, aged Samsung Galaxy S4, Samsung Galaxy Tab A 2019s (8" & 10.1"), Blu-ray burners, digital cameras, ext. HDDs (latest 5TB!), AnyDVD, Easeus ToDo Backup Home, Waterfox, more. Me: Aussie card-carrying Windows geek.

2 users thanked author for this post.

jburk07, LHiggins

Reply | Quote

Hi BigBadSteve,

Thanks for posting that you also had a problem with this update.

Here’s some info in my recent reply to Imacri’s many suggestions.

Maybe you’ll find something there that will be helpful. I will post any solutions I find as well.

LH

Reply | Quote

Have you had any luck with this update?

I haven’t been able to at all.

Good luck and please post if you’ve found a solution!

Thanks!

Reply | Quote

Just noticed new installations of Microsoft Solitaire, Photos, Skype, Clock, Calculator, FeedBack Hub, Phone Link, Media Player, and Spotify Music occurred, on another of our Windows 10 Pro computers, during the update process on 2/28/2024.

1 user thanked author for this post.

jburk07

Reply | Quote

Hi Kathy,

Kathy Stevens wrote:

Just noticed new installations of Microsoft Solitaire, Photos…

Not sure if this is relevant, but in searching for issues with KB5034763, I came across this posting in the MS Community.

Notably:

After downloading the latest Windows 10 update, KB 5034763, I find that I cannot open pictures in MS Photos although the program itself opens.

Wonder if your new installation has anything to do with that KB? Have you downloaded it?

1 user thanked author for this post.

Kathy Stevens

Reply | Quote

lmacri wrote:

However, I don’t know of any prerequisite updates that need to be applied first before the Win 10 Feb 2024 KB5034763 cumulative Quality Update will install [unless the Servicing Stack Update (SSU) v19045.3989 that is bundled with the KB5034763 installer is considered a “prerequisite”].  I also would have expected to see a lot more Win 10 users reporting problems with the installation of KB5034763 if last month’s KB5034111 WinRE update had to be installed first

KB5034111 is hidden on my Windows 10 22H2 and I had no problems installing all Feb 2024 updates including KB5034763.

2 users thanked author for this post.

jburk07, LHiggins

Reply | Quote

Alex5723 wrote:

KB5034111 is hidden on my Windows 10 22H2 and I had no problems installing all Feb 2024 updates including KB5034763.

Wherever KB5034111 is mentioned, is this a typo for KB5034441?

1 user thanked author for this post.

Alex5723

Reply | Quote

@Kathy-Stevens and @LHiggins –

I’ve had both of my machines have updates available for most of their installed Windows Store apps both yesterday and today, exactly as you have described.

BUT, I have not yet installed any of the patches for February, so I firmly believe what you’re seeing is a “normal” part of the behind-the-scenes app servicing that the Microsoft Store is supposed to do for those apps. If you have the Store app set to not allow automatic updates, then that’s a different story, in that the Store app has somehow overridden your settings.

In my case, I went to the Store app and sought out updates to install, and allowed them to install one by one. I have the Store app set to not install app updates automatically.

Hope this helps!

3 users thanked author for this post.

jburk07, LHiggins, Kathy Stevens

Reply | Quote

Bob99

Before this round of updates I had not focused on updates from the Microsoft Store.

I learned something new by participating in this Topic.

Reply | Quote

Just updated one of my Desktops and KB 5034685 .NET and KB 5034763 W10 22H2 cumulative updated fine. KB5034441 failed in January but was not offered again for me. Got 2 more computers to update so hopefully they go as well as this one did.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

1 user thanked author for this post.

jburk07

Reply | Quote

Just updated 1 of 2 machines with Windows 10 22H2. Install went smoothly for all 3 updates, which I installed in the following order: Malicious Software Removal Tool (KB890830), 2024-02 Cumulative Update for .NET Framework 3.5, 4.8, 4.8.1 (KB5034685), and finally 2024-02 Cumulative Update for Windows 10 22H2 (KB5034763). Only the Windows monthly update required a reboot, the .NET update didn’t.

For those who’ve had download issues in the recent past, I had a download speed of 13-17 Mbps for the .NET update, and 20-25 Mbps with occasional spurts to 60 Mbps for only two seconds (if that long) for the Windows monthly update. These speeds are with a 200Mbps connection from my ISP, and are “normal” for me since the late November time frame. Before that, all speeds were consistently 25-30 Mbps with spurts to 35Mbps for several seconds.

2 users thanked author for this post.

jburk07, CADesertRat

Reply | Quote

I don’t have your connection speeds but WU ran at about the same speeds for me which is quite an improvement from previous WU speeds.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

I was able to get KB5034441 to successfully install this month.  It did not install last month,  and this month it initially gave me a “download error”.  However then it gave me an option to click on “Retry”.   So I clicked “Retry” and it successfully installed,  and it went very quickly (it only took about a minute).   All the other updates for February also installed successfully.

I have Windows 10 Professional, Version 22H2.

1 user thanked author for this post.

jburk07

Reply | Quote

Update on the failed install of KB5034763.

This update just won’t install on my laptop. I tried it several times today – using WUMGR, using Windows Update, with AV turned off, after the .NET updates were successful – and it was the same each time – it would get to 94% and then say that it couldn’t complete the process and was undoing the changes.

I didn’t get any error codes when I tried using Windows Update – it isn’t even listed in the history as a failed update. And later, Windows Update was saying that my laptop is up to date.

Also interesting – I did try to update the .NET KB which worked fine, so it isn’t just a complete fail of the update process.

However – in my control panel list of installed updates, it lists 3 that were installed today.

One – KB5034122 was NOT on the update list and was not the one I was trying to install, but for some reason it is showing as being installed today 2/29.

lmacri wrote:

However, I don’t know of any prerequisite updates that need to be applied first before the Win 10 Feb 2024 KB5034763 cumulative Quality Update will install [unless the Servicing Stack Update (SSU) v19045.3989 that is bundled with the KB5034763 installer is considered a “prerequisite”].

Also interesting, Servicing Stack v19045.3989 is showing as being installed today. If, as noted above, it is bundled with KB5034763, I wonder why it could be installed but not the KB itself.

After seeing those updates showing as being installed, I tried KB5034763 one more time on the off chance they would allow it to be installed – no luck!

So, at this point, I am going to just give up and say that hopefully the March updates will be better and override whatever is causing this issue.

Thanks for the help and many suggestions – too bad nothing seems to have worked.

LH

Reply | Quote

Interesting. KB5034122 is the Jan. 2024-01 CU. Strange it should be installing today.

1 user thanked author for this post.

LHiggins

Reply | Quote

Yes, I thought so too. Strange, but didn’t seem to change anything regarding the current KB install unfortunately.

Reply | Quote

LHiggins wrote:

One – KB5034122 was NOT on the update list and was not the one I was trying to install, but for some reason it is showing as being installed today 2/29.

KB5034122 is the Patch Tuesday CU for January. Does your Windows Update > View update history show this KB for when you did the January updates?

A user reports a problem with installing KB5034763 that sounds similar to yours <here>.

Reading this might give you some leads on tracking down an error code.

1 user thanked author for this post.

LHiggins

Reply | Quote

WCHS wrote:

KB5034122 is the Patch Tuesday CU for January. Does your Windows Update > View update history show this KB for when you did the January updates?

No – it isn’t listed anywhere but in the Control Panel with today’s date.

I have seen the article you mentioned – I don’t think it is a disk space issue – I have plenty of disk space, but I can look into the boot issues, though not really sure how to do that according to the directions.

Thanks for the help!

Reply | Quote

LHiggins wrote:

Also interesting, Servicing Stack v19045.3989 is showing as being installed today. If, as noted above, it is bundled with KB5034763, I wonder why it could be installed but not the KB itself.

Because although it’s part of the bundle that’s downloaded from the servers, it’s actually a separate item that gets installed first, right before the actual monthly update gets installed.

This is based upon my having repeatedly observed (on BOTH of my machines) that the download percent indication in Windows Update gets to 100%, but the connection to the MS servers keeps going for quite a while longer (3-5 minutes), with the download percentage “stuck” at 100%. Once the connection to the server is broken, then the installation starts, usually progressing rather quickly (30 seconds to maybe a full minute) from 10 or 15 percent installed to 100% installed. Right after that, the percent installed amount then drops to 10% and much more slowly progresses towards 100%, with stops at 21%, 44 or 45%, 73%, 74% and then up to 100%. I’ve attributed that first, quick trip from 10 (or 15)-100% to be the installation of the servicing stack and the subsequent much slower trip from 10-100% to be the installation of the actual monthly update.

So, since the servicing stack was successfully installed today, it’s therefore listed on the list of installed updates. BTW, the other “Update for Windows (KB5034468)” is the update for .NET in case you were wondering.

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

One – KB5034122 was NOT on the update list and was not the one I was trying to install, but for some reason it is showing as being installed today 2/29.

Hi LHiggins:

One question.

If you open a Run dialog box (Windows key + R) and enter winver does it show you now have the OS Build 19045.3930 delivered with KB5034122 (i.e., the Jan 2024 cumulative Quality Update)?

One observation.

The image of your installed updates in post # 2643512 shows you installed KB5034468 (Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 22H2: Feb 13, 2024). My installed updates show I received KB5034466 (Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 22H2: Feb 13, 2024). Have you received KB5011048 (MS .NET Framework v4.8.1) that was pushed out to my Win 10 v22H2 machine with my Oct 2024 Patch Tuesday updates (see image below), or have you used WUMgr to hide KB5011048?

lmacri wrote:

If the problem occurs again the next time you try to install KB5034763 with WUMgr there are a few suggestions in the MiniTool article What if Windows 10 KB5034763 Fails to Install? Solve It in 6 Ways! that might help… (e.g., running sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth scans in an elevated command prompt with Administrator rights to check for damaged system files, manually installing KB5034763 for Win 10 v22H2 using the standalone .msu installer available on the Microsoft Update Catalog, etc.) might solve your problem.

Two suggestions.

Run sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth scans in an elevated command prompt with Administrator rights and post back if either scan finds an issue with your system files. Note: If Dism /Online /Cleanup-Image /ScanHealth finds a problem with your component store run Dism /Online /Cleanup-Image /RestoreHealth to attempt a repair. From my Win 10 Pro v22H2 (OS Build 19045.4060) machine:

If you haven’t already done so, I’d also suggest you disable Fast Startup as instructed in Option # 1 of Brink’s TenForums tutorial How to Turn On or Off Fast Startup and then re-boot a few times to ensure the setting change takes effect. The Fast Startup power option (also known as hybrid boot-up / hybrid shutdown) is enabled by default in Win 10 and Win 11 but it can sometimes interfere with the loading and initialization of drivers and services at boot-up and cause all sorts of unexpected glitches and problems with third-party antivirus programs and a variety other of software, including Windows Updates (see the MS Learn article Updates may not be installed with Fast Startup in Windows 10).  If you previously disabled Fast Startup just check to make sure it’s still disabled.
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

Perq, LHiggins

Reply | Quote

lmacri wrote:

The image of your installed updates in post # 2643512 shows you installed KB5034468 (Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 22H2: Feb 13, 2024). My installed updates show I received KB5034466 (Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 22H2: Feb 13, 2024). Have you received KB5011048 (MS .NET Framework v4.8.1) that was pushed out to my Win 10 v22H2 machine with my Oct 2024 Patch Tuesday updates (see image below), or have you used WUMgr to hide KB5011048?

While .NET 3.5 exists on all Windows 10 PC’s (it’s “integrated” into the OS), .NET 4.8 & 4.8.1 were optional updates and .NET 4.8.1 replaced .NET 4.8.

That means it’s impossible to get both updates; you’ll only get the update for the specific version of .NET (4.8 or 4.8.1) that’s installed on your PC!

For example, my Desktop has .NET 4.8 and only got the KB5034468 update while my Laptop has .NET 4.8.1 and only got KB5024466.

1 user thanked author for this post.

LHiggins

Reply | Quote

n0ads wrote:

That means it’s impossible to get both updates; you’ll only get the update for the specific version of .NET (4.8 or 4.8.1) that’s installed on your PC!

Hi n0ads:

I understand that. I was only asking LHiggins if they know the reason why the KB5011048 (MS .NET Framework v4.8.1) that was automatically delivered to my Win 10 Pro v22H2 machine by Windows Update back in Oct 2023 has not been delivered to their own Win 10 v22H2 machine by WUMgr (e.g., if KB5011048 is currently hidden by WUMgr on their system).

KB5011048 is listed in my Windows Update history under “Other Updates” (see attached image) but it was not offered as an “optional” update – it was installed by Windows Update with my other October 2023 Patch Tuesday updates. See my 13-Oct-2024 post # 2593792 in Susan Bradley’s October updates – here comes Copilot.

If LHiggins has deliberately hidden KB5011048 or it’s listed as an optional update in WUMgr then that’s fine, but if that MS .NET Framework v4.8.1 update has never been offered by WUMgr then perhaps that’s a sign that there were problems with their Patch Tuesday updates as far back as Oct 2023.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

lmacri wrote:

If LHiggins has deliberately hidden KB5011048 or it’s listed as an optional update in WUMgr then that’s fine, but if that MS .NET Framework v4.8.1 update has never been offered by WUMgr then perhaps that’s a sign that there were problems with their Patch Tuesday updates as far back as Oct 2023.

As I said in another post, the changes that the “undoing” of the failed install made deleted all of my WUMgr history, but I looked at my other laptop, which did get the same updates as this one, and I don’t see KB5011048 listed. I do see KB5030180 which is the .NET for 3.5, 4.8 and 4.8.1 listed on 10/1/23 if that helps?

I guess a question is – is there something wrong with my WUMgr program along with this inability to install the current KB. Losing that update history is a concern since it doesn’t show in Windows Update history since I don’t use that.

Reply | Quote

Thanks so much for the detailed reply. Sorry I didn’t post back last night – kind of burned out on the whole issue LOL!

lmacri wrote:

If you open a Run dialog box (Windows key + R) and enter winver does it show you now have the OS Build 19045.3930 delivered with KB5034122 (i.e., the Jan 2024 cumulative Quality Update)?

Yes – I have Build 19045.3930.

lmacri wrote:

Have you received KB5011048 (MS .NET Framework v4.8.1) that was pushed out to my Win 10 v22H2 machine with my Oct 2024 Patch Tuesday updates (see image below), or have you used WUMgr to hide KB5011048?

I don’t think I received that one, but I know I didn’t hide it. Since this issue developed and the failed KB install “undid changes” my WUMgr no longer shows my entire download history, and since I use that, none of the updates are listed in the Windows Update page. So I don’t know for sure, but I will check my other laptop and see if it is there, since both laptops have the same update history.

lmacri wrote:

Run sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth scans in an elevated command prompt with Administrator rights and post back if either scan finds an issue with your system files. Note: If Dism /Online /Cleanup-Image /ScanHealth finds a problem with your component store run Dism /Online /Cleanup-Image /RestoreHealth to attempt a repair.

I will try to do this later today and will post back with any results. I hate to mess around with things like that, and will make a backup first in case something else happens.

lmacri wrote:

If you previously disabled Fast Startup just check to make sure it’s still disabled.

I don’t think I can make that change. I have no option to turn Fast Startup on or off:

I can’t think of any reason that this issue would have suddenly appeared, but I do appreciate your help with possible ways to address it. I will post back later with anything relevant.

LH

Reply | Quote

LHiggins wrote:

… I will try to do this later today and will post back with any results. I hate to mess around with things like that, and will make a backup first in case something else happens.

Hi LHiggins:

If you wish, run the command sfc /verifyonly, which only scans for problems with your system files but does not attempt to perform a repair. If no problems are detected then there is no need to run sfc /scannow to attempt to repair damaged or missing system files. See the Lifewire article Sfc Command (System File Checker) for more information.

The command Dism /Online /Cleanup-Image /ScanHealth will only scan for component store corruption. No repair will be attempted unless you run Dism /Online /Cleanup-Image /RestoreHealth.

LHiggins wrote:

… I don’t think I can make that change. I have no option to turn Fast Startup on or off:

I’m not sure about that one. I’ve found a few posts suggesting that the “Change settings that are currently unavailable” link to display your Fast Startup setting will not appear if the user account you use to log in to Windows does not have Administrator rights and/or you have disabled UAC (User Account Control) in your user account as instructed in the Lifewire article How to Disable UAC in Windows 10.

Just FYI, when I log in to Windows as a Standard user with the UAC setting for that account set to the default “Always Notify” I am able to see the “Change settings that are currently unavailable” link (see attached image), so being logged in as an Administrator is not required on my Win 10 Pro v22H2 machine.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

Perq, LHiggins

Reply | Quote

lmacri wrote:

when I log in to Windows as a Standard user with the UAC setting for that account set to the default “Always Notify” I am able to see the “Change settings that are currently unavailable” link

Just to update – I am signed in with Admin rights, and “Always Notify” is set – and I can see the link to “change settings that are unavailable” – but when I click that – the choice for Fast Startup is not there – only Sleep and Lock.

 

Reply | Quote

If hibernation has been disabled Fast Startup won’t be displayed.

2 users thanked author for this post.

lmacri, LHiggins

Reply | Quote

cyberSAR wrote:

If hibernation has been disabled Fast Startup won’t be displayed.

Hi LHiggins:

Kudos to cyberSAR for that reminder.

Also note that the intro to Shawn Brink’s TenForums tutorial at How to Turn On or Off Fast Startup in Windows 10 also states that “If you disable hibernate, then it will also disable fast startup. You must be signed in as an administrator to turn fast startup on or off.”

Have you tried running sfc /verifyonly and Dism /Online /Cleanup-Image /ScanHealth (diagnostic scans only, no repairs attempted) from an elevated command prompt with Administrator rights yet?
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

lmacri wrote:

Have you tried running sfc /verifyonly and Dism /Online /Cleanup-Image /ScanHealth (diagnostic scans only, no repairs attempted) from an elevated command prompt with Administrator rights yet?

Yes – I did both – more on that below.

OK – here’s an update on where I am with this issue.

This morning I checked WUMgr and there still was the history issue, so I decided that since this “problem” first came to light on 2/27 when I attempted the download of KB5034763, I might as well roll back to that backup again – made before the update attempt. I also decided to make a current backup of this morning in case. After that, I was ready to restart and go through the roll back when I noticed that the laptop had now “gotten” that update again and was waiting to restart to install it. I figured OK – try once more – which of course didn’t work.

So, after it went through the “undoing” cycle 3 times, it restarted and I rolled it back my Macrium backup from 2/27/24.

WUMgr now shows all of the history, and has pending downloads for KB5034763 and the .NET update KB5034685. It also shows that KB5034122 and KB5034275 were installed on 2/1/24.

OK – now to the scans. I ran sfc /verifyonly and got the following result:

It gave me a log file link, which I looked at and it is very large and really no idea what I’m looking for. Will running scan / now fix whatever the problem is – I didn’t try that yet.

I also ran the Dism /Online /Cleanup-Image /ScanHealth diagnostic. That showed this:

That didn’t show anything.

So, at this point things “seem” to be back to normal. Unless you think that one of the scans can address the possible problem – and who knows how long that may have been there – I think I am going to just restore my emails and things that were created between the 27th and today, hide that offending KB and just wait till next month and see how things look then.

Thanks to everyone for all of the help. This has been a pretty daunting problem, but at least I feel that things have been returned to the pre-update attempt state.

Please let me know if there is anything else to suggest at this point. I haven’t really looking into too many of the possible fixes in the articles about this KB, and maybe I don’t want to press my luck by trying other things?

Thanks again!

1 user thanked author for this post.

Cybertooth

Reply | Quote

Running sfc verifyonly found some problems.
Try running sfc /scannow and see if it will fix the problems.

 

2 users thanked author for this post.

lmacri, LHiggins

Reply | Quote

LHiggins wrote:

It gave me a log file link, which I looked at and it is very large and really no idea what I’m looking for.

Hi LHiggins:

One other hint. The Microsoft Learn article Analyze the log file entries that SFC.exe generates in Windows has instructions on how to view and interpret the contents of CBS.log file after running System File Checker (SFC). When you run sfc /scannow it will create entries in the CBS.log file that have a “[SR]” tag that you can extract using the findstr (find string) command.

For example, after I run sfc /scannow I can enter the command findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfcdetails.txt” (including the quote marks). This creates a .txt file on my desktop with details of each verification and repair operation performed by all my recent sfc /scannow scans.

If I enter the command findstr /c:”2024-01-30″ %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfcdetails2.txt” that would create a .txt file on my desktop that includes all activity logged in my CBS.log file on January 30, 2024. My CBS.log file always logs dates with the yyyy-mm-dd format, so others might have to tweak that command slightly if their own CBS.log file uses a different format when logging the date.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

LHiggins, WCHS

Reply | Quote

lmacri wrote:

I can enter the command findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfcdetails.txt” (including the quote marks).

I was curious to see what I would get with this command, since I have recently done a “sfc /verifyonly” and received a CBS.log message.

This is what I get: There seems to be something strange with the syntax.

But, if I run it as findstr /c:”[SR]” c:\Windows\Logs\CBS\CBS.log >c:\Users\MYUSERNAME\Desktop\sfcdetails.txt (substituting my actual username), it works — I get a sfcdetails.txt file on my Desktop.

In File Explorer, in the path field, if I type %windir%, the C:\Windows folder opens. If I type %userprofile%, my user folder opens. So, the variables are working as they should.

Reply | Quote

lmacri wrote:

For example, after I run sfc /scannow I can enter the command findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfcdetails.txt” …

WCHS wrote:

…There seems to be something strange with the syntax.

Hi WCHS:

Sorry, I should have been more specific and said that you should run those commands from an elevated command prompt with Administrator rights (i.e., not a PowerShell console) as instructed in the Microsoft Learn article Analyze the log file entries that SFC.exe generates in Windows.

See the output in the attached  sfcdetails.txt file after I run sfc /verfiyonly (which doesn’t really tell you a great deal unless you run sfc /scannow and it actually finds damaged or missing system files that it will attempt to repair).

————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

LHiggins, WCHS

Reply | Quote

Hi Imacri,

lmacri wrote:

One other hint. The Microsoft Learn article Analyze the log file entries that SFC.exe generates in Windows has instructions on how to view and interpret the contents of CBS.log file after running System File Checker (SFC).

Thanks for this hint. I will try to figure it out later on today.

I guess my concern about trying the KB update again after any “repairs” is that is isn’t clear what is really causing the issue – a possible disk space issue as the error code indicates, or a boot issue or something else. So the only way to know if it is “fixed” is to try the update again and see.

After finally getting back my WUMGr history with the restore I did yesterday, I am not sure that I want to try that update again and have to go through the restore process again.

I will try taking a look at the log files and run the scannow to see what is fixed, but I also have my other Win 10 laptop to try to update, so I may work on that first and see if the issue happens on that one too – not that it will give me any more information if it does.

And I may also try Bob99’s suggestion of resetting the software distribution folder, though again, the only way to know if that helps is to try the download again.

I’ll post back with questions, and thanks for all of the help.

Reply | Quote

LHiggins wrote:

Thanks for this hint. I will try to figure it out later on today. I guess my concern about trying the KB update again after any “repairs” is that is isn’t clear what is really causing the issue

Hi LHiggins:

You should run sfc /scannow to repair your damaged or missing system files, regardless of whether you try another install of KB5034763 (the Win 10 v22H2 Feb 2024 cumulative Quality Update for OS build 19045.4046) or not. Damaged system files could cause other glitches and odd behaviour on your system, even if it turns out those damaged files aren’t responsible for your KB5034763 installation failure.

The attached image I captured a few months ago shows the steps I took to diagnose and repair a damaged system file on 01-Nov-2023 using an elevated command prompt.  That includes:

1. A DISM /Online /Cleanup-Image /ScanHealth scan (which reported “No component store corruption”).
2. A sfc /scannow scan (which reported “Windows Resource Protection found corrupt files and repaired them“)
3. Assorted findstr commands to extract information about my sfc repair from my CBS.log file and save them in .txt files on my desktop (this step is optional – I was just curious what sfc /scannow had fixed).
4. A second sfc /scannow scan (which reported “Windows Resource Protection did not find any integrity violations”) and confirmed there were no more system files requiring a repair.

Once you have confirmed your system files have been repaired then it’s entirely up to you if you want to try installing KB5034763 again. It’s possible that fixing your damaged system files will allow KB5034763 to install successfully, but it’s also possible that KB5034763 will fail to install again because something else (e.g., a corrupted Windows Update component) is causing the installation failure.

LHiggins wrote:

… And I may also try Bob99’s suggestion of resetting the software distribution folder, though again, the only way to know if that helps is to try the download again.

Once you have used sfc /scannow to repair your damaged or missing system files I agree with Bob99’s suggestion that it might also be helpful to reset your Software Distribution folder as instructed in Susan Bradley’s 2000023: Resetting the software distribution folder, even if you decide not to try another install of KB5034763.  If there’s a problem with your Software Distribution folder chances are your upcoming March 2024 cumulative Quality Update is going to fail as well.

Note that the previously mentioned MiniTool article What if Windows 10 KB5034763 Fails to Install? Solve It in 6 Ways! also suggests a similar reset of your Windows Update components while signed in as an Administrator (see “Way 2. Reset Windows Update Components”).  The method described in that MiniTool article is much more complex and includes instructions on how to re-register all the related BITS (Background Intelligent Transfer Service) and Windows Update .dll files in your Windows registry.

In the past I’ve followed Susan’s method and simply reset the Software Distribution folder to fix a stubborn problem with Windows Update, but if you ever need to perform a complete reset of your Windows Update components on your Win 10 machine note that you can run the Reset_Reregister_Windows_Update_Components.bat batch file that Shawn Brink has posted in their TenForums tutorial How to Reset Windows Update in Windows 10 that automates the entire process.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

LHiggins, WCHS

Reply | Quote

Hi Imacri and thanks for all of your help and suggestions!

lmacri wrote:

You should run sfc /scannow to repair your damaged or missing system files, regardless of whether you try another install of KB5034763 (the Win 10 v22H2 Feb 2024 cumulative Quality Update for OS build 19045.4046) or not.

Yes, that does sound right since the scan/verify did show that there were errors. And even if I don’t try getting that particular update again, it is probably a good idea to have a “clean” system.

lmacri wrote:

…the steps I took to diagnose and repair a damaged system file on 01-Nov-2023 using an elevated command prompt.  That includes: A DISM /Online /Cleanup-Image /ScanHealth scan (which reported “No component store corruption”). A sfc /scannow scan (which reported “Windows Resource Protection found corrupt files and repaired them“)

So when I do this – I have already run the DISM scan which showed no issues, so should I run that again? And would I do that first before the scannow?

And I think I will try to run the “findstr commands” as you suggest to see what was fixed and if anything seems related to the issues that were suggested as possibly what caused the KB install to fail.

lmacri wrote:

Once you have used sfc /scannow to repair your damaged or missing system files I agree with Bob99’s suggestion that it might also be helpful to reset your Software Distribution folder as instructed in Susan Bradley’s 2000023: Resetting the software distribution folder, even if you decide not to try another install of KB5034763.  If there’s a problem with your Software Distribution folder chances are your upcoming March 2024 cumulative Quality Update is going to fail as well.

And yes, this sounds like great advice, too since I really don’t want to have any issues with updates again. This was enough – LOL!

I’ll run a backup and then work on these steps in the next day or so, and hopefully everything will be fine with the March updates.

I am also going to try to get to my other laptop and see what it does with KB5034763. If the same thing happens on that machine, I have one other thought that has just occurred to me. Both laptops have a free 0Patch account and get some of their free patches – maybe something in one of those could be affecting things? But that is a topic for another discussion, if indeed it is the case that both laptops have the same reaction to that KB. Most likely not, hopefully. And not even something to think about unless KB5034763 fails on the second laptop in the same way.

Thanks again for al of the great advice!  Very much appreciated!

LH

Reply | Quote

LHiggins wrote:

So when I do this – I have already run the DISM scan which showed no issues, so should I run that again? And would I do that first before the scannow?

Hi LHiggins:

It’s not strictly necessary, but I always run a DISM /Online /Cleanup-Image /ScanHealth scan first just to check if there are problems with my component store (and if necessary, fix any problems that scan finds with DISM /Online /Cleanup-Image /RestoreHealth) before running sfc /scannow.

The ghacks.net article Use DISM to Fix Issues SFC Can’t is a useful resource and notes that if sfc /scannow is unable to repair a damaged system file (i.e., it reports “Windows Resource Protection found corrupt files but was unable to fix some of them“) then DISM /Online /Cleanup-Image /RestoreHealth can sometimes fix what sfc /scannow can’t.

LHiggins wrote:

I have one other thought that has just occurred to me. Both laptops have a free 0Patch account and get some of their free patches – maybe something in one of those could be affecting things?

I don’t use 0Patch to patch my Win 10 OS so I can’t say, but that’s a definite possibility.

I’m not sure 0Patch micropatches are really that beneficial for home consumers while Win 10 v22H2 is still supported by Microsoft.  Even 0Patch suggests <here> that you would typically use their product if you wanted to patch vulnerabilities in Win 7 or older Win 10 versions like v1803 or v1809 after their support has ended.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

2 users thanked author for this post.

LHiggins, WCHS

Reply | Quote

Good morning! Here’s an update of what I’ve done to try to correct the issue with this stubborn KB.

After a new backup, I did the following:

1. lmacri wrote:

   A DISM /Online /Cleanup-Image /ScanHealth scan

   – was successful, though I didn’t see any indication of errors that were fixed.

2. lmacri wrote:

   A sfc /scannow scan

   – which found errors and corrected them.

3. A second sfc /scannow which showed no integrity violations.
4. A DISM scan again which showed all was OK.

I had a problem being able to copy and paste into the CMD window for some reason – sometimes it worked and sometimes not, so I didn’t do the command to create the text files – too long to try to type in manually. It worked fine earlier, but won’t allow me to paste text into the CMD window today.

I guess my next step is to reset the Software Distribution folder and hopefully that will have addressed whatever the issue was. But I’m not sure, after all of this, that I am going to give installing KB5034763 another try since in the failed process of undoing changes, it seems to create problems.

lmacri wrote:

I don’t use 0Patch to patch my Win 10 OS so I can’t say, but that’s a definite possibility. I’m not sure 0Patch micropatches are really that beneficial for home consumers while Win 10 v22H2 is still supported by Microsoft.  Even 0Patch suggests that you would typically use their product if you wanted to patch vulnerabilities in Win 7 or older Win 10 versions like v1803 or v1809 after their support has ended.

I don’t believe it is 0Patch, since I did update my other laptop – an HP, also Win 10 22H2, with no problems this morning – so it doesn’t seem likely it is 0Patch. I ran the paid version, 0Patch Pro, on my Win 7 laptop for several years after its support ended, and somewhere along the line I got the free version for the HP laptop, and I decided to do it for this Thinkpad, too in preparation for using it when these run out of support. It never caused any issues on the HP in the past, and I agree that it probably doesn’t do much. But since one laptop is fine and one isn’t – I am guessing that 0Patch isn’t the culprit.

So, that’s where I am at this point. The only thing I have left to try is to get the .NET update, KB5034685, which I had downloaded before in this process and it was fine – just got removed when I rolled back to before the updates were first done. And it was successful on the HP, too.

Thanks again for all of the help and very detailed instructions. I could never have begun to figure this out without your patience and perseverance! Hopefully next month’s updates will go smoothly and I can put all of this behind me – but I have learned quite a few things that might help if there is another problem!

 

1 user thanked author for this post.

lmacri

Reply | Quote

LHiggins wrote:

I had a problem being able to copy and paste into the CMD window for some reason – sometimes it worked and sometimes not

Hi LHiggins:

One other hint if you’re having problems pasting long commands into a command prompt using the Ctrl+V key combination.

If you’ve copied a long command you don’t want to re-type into your clipboard (e.g., by highlighting the command in a support article and using using Ctrl+C)  then click your mouse in the command prompt where you want to paste the command, right-click anywhere in the title bar at the top of the command prompt to display the pop-up context menu shown below, and choose Edit | Paste.

————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

Perfect – thanks so much!

I did try the findstr command and it did create the text file. But if it was created after the repairs had already been made, will it show what was repaired?

I only see entries like this:

2024-03-04 10:10:34, Info CSI 00000006 [SR] Verifying 100 components
2024-03-04 10:10:34, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2024-03-04 10:10:34, Info CSI 00000008 [SR] Verify complete
2024-03-04 10:10:34, Info CSI 00000009 [SR] Verifying 100 components
2024-03-04 10:10:34, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2024-03-04 10:10:34, Info CSI 0000000b [SR] Verify complete

I guess that doesn’t tell much – but I’ll know how to do it next time.

Thanks!!

Reply | Quote

LHiggins wrote:

I only see entries like this:

Hi HLiggins:

Try running the command findstr /c:”2024-03-04″ %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfcdetails2.txt” to create a .txt file on your desktop that includes all activity logged in your CBS.log file on March 4, 2024. If the sfc /scannow scan that actually performed the repair was run yesterday on March 3, 2024 then search for the string “2024-03-03”.

When you search by date you might find extra details about your sfc /scannow repair of 04-Mar-2024 at ~ 10:10:30 AM that are not tagged with “[SR]”. For example, the attached .txt file is a small excerpt from my CBS.log for a sfc /scannow command I ran on May 30, 2022 at ~ 7:00 AM that detected and repaired some problems with security permissions / ownership of a few folders, and those lines are tagged in my scan log with “Warning” or “CSIPERF” instead of “[SR]”.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

lmacri wrote:

When you search by date you might find extra details about your sfc /scannow repair of 04-Mar-2024 at ~ 10:10:30 AM that are not tagged with “[SR]”. For example, the attached .txt file is a small excerpt from my CBS.log for a sfc /scannow command I ran on May 30, 2022 at ~ 7:00 AM that detected and repaired some problems with security permissions / ownership of a few folders, and those lines are tagged in my scan log with “Warning” or “CSIPERF” instead of “[SR]”.

Thanks! I tried running this today and didn’t find anything that had “Warning” or “CSIPERF”. I’ll take another look at it, but I guess for now – it all seems to be fine.

I still need to run the download folder reset, and then hopefully next month will be OK with new updates.

Thanks again for all of the help!

 

Reply | Quote

LHiggins wrote:

And I may also try Bob99’s suggestion of resetting the software distribution folder, though again, the only way to know if that helps is to try the download again.

Hi LHiggins:

I just noticed your post # 2647634 today in Susan Bradley’s When is a system beyond repair?.

Before you reset your SoftwareDistribution folder, you might want to run the Windows Update troubleshooter that is built in to your Win 10 OS at Settings | Update & Security | Troubleshoot | Additional Troubleshooters (link) | Windows Update (see image below) just to see if that diagnostic finds any problems that can be automatically repaired without a full reset of the SoftwareDistribution folder.

In your case, I doubt that running this troubleshooter will help since your problem installing KB5034763 (the Win 10 v22H2 Feb 2024 cumulative Quality Update for OS build 19045.4046) seems to be restricted to that one particular update (i.e., your other Feb 2024 Patch Tuesday updates installed successfully) but it might be worth a try.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

Hi Imacri!

Thanks for the thought. I did run that troubleshooter early on after that update failed, but did it again just now, and it doesn’t show anything.

Just thought I’d ask about the reset of that folder, since I never did it after I got the other Feb updates, and before I run into this again at the end of the month with the March updates.

Still remains a puzzle!

Thanks for the thought – I do appreciate all of the help with this issue.

 

Reply | Quote

Just came across information on How to Delete Old Windows Update Files that may help with this situation.

I gave it a try and it deleted 613 MB of old Windows Update files. Maybe that was why KB5034763 would only go so far and then undo changes – it needed a little more space, possibly?

In any case – no way to tell if that will help in the long run, but something that I did try now ahead of March updates.

Reply | Quote

LHiggins wrote:

Just came across information on How to Delete Old Windows Update Files that may help with this situation. I gave it a try and it deleted 613 MB of old Windows Update files…

Hi LHiggins:

That MakeUSeOf article How to Delete Old Windows Update Files lists three ways to delete your Windows Update files. You didn’t say which method you used but the third method in that MUO article (Method 3: Through SoftwareDistribution Folder) is similar to the instructions in Susan Bradley’s 2000023: Resetting the software distribution folder that Bob99 and I both recommended, and you would have essentially accomplished the same thing if you had followed Susan’s instructions.

I personally think that Susan’s instructions are a safer way to clear the files in the SoftwareDistribution folder and would have done a better job of resetting all your Windows Update components.
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

lmacri wrote:

You didn’t say which method you used

I only did the first one – using disk cleanup to do the windows update cleanup – seemed pretty easy. Not sure it if will do anything, but figured I’d give it a try!

Can I still do the reset as per Susan’s instructions?

Thanks!

Reply | Quote

LHiggins wrote:

Can I still do the reset as per Susan’s instructions?

Yes.

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

One – KB5034122 was NOT on the update list and was not the one I was trying to install, but for some reason it is showing as being installed today 2/29.

KB5034122 is Jan. CU.

Do you have C:\$WinREAgent folder ? Maybe try Windows 11 failed Feb. CU workaround and delete the folder and try again.

1 user thanked author for this post.

LHiggins

Reply | Quote

Alex5723 wrote:

Do you have C:\$WinREAgent folder ? Maybe try Windows 11 failed Feb. CU workaround and delete the folder and try again.

Yes, I do now. I couldn’t find it when I started the update process – maybe I can give it one more try…that was the original MS rep advice.

Reply | Quote

Alex5723 wrote:

Do you have C:\$WinREAgent folder ? Maybe try Windows 11 failed Feb. CU workaround and delete the folder and try again.

And nope…same couldn’t complete updates, undoing changes loop again.

2 users thanked author for this post.

jburk07, Alex5723

Reply | Quote

February isn’t finished yet..

Moment 5 dribbling out for W11 22H2 and 23H2
See #2643518

Windows - commercial by definition and now function...

Reply | Quote

And one more update on the failed install of KB5034763.

I tried a few more things – one of which was to do a disk cleanup – that freed up about 5 GB of space, which I thought might do it – but no!

WCHS wrote:

A user reports a problem with installing KB5034763 that sounds similar to yours .

I also looked at the suggested fixes in that article, but didn’t find anything that might help.

I also found the error code in the event viewer: 0X800F0922 – and Googled that – also didn’t find something that might be a fix that didn’t involve a lot of “work”.

So – this remains a mystery and now I think I am really done trying, and will wait for next month’s updates to see if this goes away.

Reply | Quote

Well, perhaps it’s time for you to run “sfc /scannow” followed by “DISM /Online /Cleanup-Image /RestoreHealth” (running each command without the quotes, of course). Each one may take a bit of time to run and might appear “stuck” at a given point, so please give each one time to run. Do not try to run them simultaneously, but one at a time instead starting with the sfc command. Also, please note that there are spaces between the / and parts of the command, so it might be best of you copy/pasted them.

Both of those commands above should be run from a command prompt with administrator-level privileges, or what’s called an elevated command prompt.

EDIT to add: The other thing you could try (which may have been listed in one of the other links you’ve visited in your pursuit of solving the failed installation of this month’s Windows 10 update) is to reset your Software Distribution folder, which kind of resets Windows Update. The best overall instructions on how to do it are at the following link here on AskWoody: https://www.askwoody.com/forums/topic/2000023-resetting-the-software-distribution-folder/. This article is written by none other than Susan and is fairly easy to follow. It’s based on another article by Microsoft, but filtered by removing a lot of highly technical jargon and background info. I’ve done it and it definitely worked when I was having issues with WU not working correctly with respect to a specific update several months ago.

2 users thanked author for this post.

Perq, LHiggins

Reply | Quote

LHiggins wrote:

I also found the error code in the event viewer: 0X800F0922 – and Googled that – also didn’t find something that might be a fix that didn’t involve a lot of “work”.

Hi LHiggins:

As I mentioned in post # 2643086, error code 0x800F0922 is the same error code that Win 11 users are seeing logged in their Event Viewer this month if their KB5034765 (OS Build 226xx.3155, released 13-Feb-2024) update fails. See the Known Issues of the KB5034765 release notes <here>.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.0 * Microsoft Defender v4.18.24010.12-1.1.24010.10 * Malwarebytes Premium v4.6.9.314-1.0.2276 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

WUMgr Question – since the “undoing changes” by the failed KB install erased all of my WUMgr history, is it worth it to revert to the last backup that I have before all of this started – or should I just keep trying to figure this out and not worry about the update history? I just want to be sure that WUMgr is still working properly.

From my original post about this KB issue:

LHiggins wrote:

It also did a weird thing to WUMGR when I  tried to see if the update indeed did install or fail. When I started WUMGR again, the info was blank – no record of any updates being installed – no history, and when I checked again for updates, it then listed ALL of the many I had hidden over the time I’ve used it, plus KB5034763. I tried it all a second time – same thing. So I rolled back my Macrium backup and now things appear back to normal. WUMGR shows everything and all seems OK.

Thanks!

Reply | Quote

Might be good to uninstall/reinstall WUMgr, in case it is corrupted?
(Or, if you just want the history back, do a restore and start over.)

2 users thanked author for this post.

LHiggins, Mark

Reply | Quote

Hello PKCano:

Your advice is sound; I sometimes have problems with WUMgr, usually with downloads.  I find that switching to Windows Automatic Update solves the problem.  I should uninstall WUMgr also.

Edit: I notice that WUMgr has not been updated in over three years.  Is is time to let it go?  Perhaps it has been disabled by changes in WU.

Mark

 

Reply | Quote

Mark wrote:

Edit: I notice that WUMgr has not been updated in over three years. Is is time to let it go? Perhaps it has been disabled by changes in WU.

There is nothing wrong with WUMgr. It works for controlling Windows Update through the latest version of Win11. There is no need/reason to uninstall it or stop using it.

2 users thanked author for this post.

Cybertooth, JC Zorkoff

Reply | Quote

There is nothing wrong with WUMgr.

If there was nothing wrong with it, you wouldn’t have to uninstall/reinstall it. I just went with what you wrote.  It hasn’t always worked for me.

Mark.

Reply | Quote

Thanks!

PKCano wrote:

(Or, if you just want the history back, do a restore and start over.)

Yes, I would like the history back but doing a restore back to where it worked will then wipe out the couple of updates I was able to get – KB5034585 – so I guess it’s a toss-up. I can always get that one again if I was sure the history would come back.

Maybe do a few scans first and see if there are any issues with this computer suddenly.

Reply | Quote

LHiggins wrote:

WUMgr Question – since the “undoing changes” by the failed KB install erased all of my WUMgr history,

I think that if you run ‘check for updates’ you will get your history back.

ps. WUmgr is portable app. No need to install/uninstall.

1 user thanked author for this post.

LHiggins

Reply | Quote

Alex5723 wrote:

I think that if you run ‘check for updates’ you will get your history back.

Actually, all it shows when I check for updates is the very recent history from yesterday. My other laptop has a huge number of things listed in the history for several years since it was first installed. I was hopeful that it would come back – but whatever happened when the failed install went through the “undoing changes” – it has somehow erased all of the history. I think he only way to possibly get it back is to restore a backup from before this all happened.

I don’t run WUMgr as a portable app – it is installed on both of my laptops.

Thanks for the help!

Reply | Quote

Several of my problems continued to exist in February. The worst is the continued deleting of all my Edge Wallet passwords. I now keep an exported .cvs file to make it easier to import deleted passwords. I also now keep passwords in Edge Favorites that are not deleted. I keep searching for solutions or explanations, but only find more user complaints. I’ll wait and see if the latest preview update fixed anything, but this is mostly a waste of time. I now have 3 systems converted to Ubuntu (not with Windows 11 also installed) with full Windows capability and no problems there. I’d rather have a less buggy windows, but this is the worst windows since windows 95.

Reply | Quote

LHiggins wrote:

I don’t run WUMgr as a portable app

There in no install version.
WUmgr doesn’t hold a log of updates… the app gets its data from Windows update history/uninstall

Reply | Quote

Alex5723 wrote:

There in no install version. WUmgr doesn’t hold a log of updates… the app gets its data from Windows update history/uninstall

Guess I’m confused LOL! But I’m not sure that WUMgr doesn’t somehow keep a log of the updates. On my other laptop, which I haven’t tried to update yet – there are over 500 different updates showing in the history. In Windows Update History there are maybe 10 – so somehow it is keeping a record of what has been downloaded. And it is all there as soon as I open the program. On this “affected” laptop, it is blank when I firs start it and then only has the most recent 2 in the history – where it used to have many. And in the Windows update history on this laptop, at this moment I can’t even access that or see the history – which I know only shows a few that I got before I started with WUMgr.

Why Windows Update is no longer showing in my settings is a new mystery…

 

Reply | Quote

LHiggins wrote:

Why Windows Update is no longer showing in my settings is a new mystery…

There is a setting in WUMgr to hide/show Windows Update in the Settings App. Do you have it checked to hide it. If so, you can’t see it.

1 user thanked author for this post.

LHiggins

Reply | Quote

LHiggins wrote:

And it is all there as soon as I open the program.

There’s a setting in WUMgr to “Run in background” which is most likely enabled for the PC that always shows a history when you open WUMgr.

On the other one, you need to click the “refresh button” (the circling arrows on the left under Update History) for it to display them.

LHiggins wrote:

But I’m not sure that WUMgr doesn’t somehow keep a log of the updates.

WUMgr uses the “primary” Windows update log, not the View update history log.

FYI, updates only show up in “View update history” if Windows Update was used to install them. If they were installed by “other means” (i.e. WUMgr, manual download, etc.) you have to use the “Uninstall updates” option at the top left of the View update history window to see them (that option uses the “primary” Windows update log to display the updates just like WUMgr.)

BTW, at this point, I’d suggest you compare all the settings in the lower left side of WUMgr between your two PC’s and set them on the PC that’s not working the way you expect to match the settings on the one that does.

2 users thanked author for this post.

LHiggins, Cybertooth

Reply | Quote

Mark wrote:

There is nothing wrong with WUMgr.

If there was nothing wrong with it, you wouldn’t have to uninstall/reinstall it. I just went with what you wrote.  It hasn’t always worked for me.

Mark.

There is and never was anything wrong with WUmgr which by the way is portable and doesn’t need uninstall/install and files are never changed.
I use the app every month and there was no file changes since 2019.

Reply | Quote

I’m reading so many problems with Feb. updates that I’m just going to start stop pause updates on all PCs till next month [again..did this last month] and hope Microsoft sorts it out by then. You’d think with all this AI they could get this right..unless it’s intentional to get ppl to buy new PCs.

February 2024 Windows 11 Update Causing Chaos For Millions Of PC Users (forbes.com)

Reply | Quote

MrToad28 wrote:

February 2024 Windows 11 Update Causing Chaos For Millions Of PC Users (forbes.com)

Final paragraph:

It’s still worth installing the update as it has various other fixes and there’s a good chance it will have been installed without issue too.

Reply | Quote

I didn’t have any problems with the Windows 11 security update when I used Windows Automatic Update.  There were two reboots, but I think that I had the setting wrong. There should have been only one restart.

I did, however, have problems with WUMgr for the Win 11 security update.  It didn’t work – gave an error message.  It did install the other updates correctly.

Mark

Reply | Quote

Susan wrote: “My mantra — to have multiple browsers and keep one for specific uses, such as banking —”

Would you elaborate on why we should have multiple browsers?

Thanks.

Reply | Quote

I’m not Susan,  🙂  but I can offer at least a couple of reasons to have multiple browsers.

One reason, as Susan says, is to keep your banking and financial activity isolated from whatever else you might do on the Internet. This helps to minimize the risk of sensitive data being accessed by nefarious actors who might be lurking on other websites you visit.

Another reason is related but broader in scope: Compartmentalizing our Web surfing by browser helps to ensure that no single browser (or, more precisely, its developers and managers) will have a complete picture of what we do on the Internet.

You might of course feel differently or be less concerned about these things, but I did want your question to get an answer. Hope it was a useful one.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

280park

Reply | Quote

Cybertooth wrote:

’m not Susan, 🙂 but I can offer at least a couple of reasons to have multiple browsers.

If one is using the Firefox browser and uses the “Firefox Multi-Account Containers” extension to set up a container for each ‘sensitive data’ URL, doesn’t this keep the activity under each URL isolated from the other(s), i.e., each tab is a compartment isolated from the other(s), in other words, this works as if one were using multiple browsers?

1 user thanked author for this post.

280park

Reply | Quote

I haven’t tried that extension or looked into it, so I can’t offer any thoughts on it specifically. But I have to think that using separate browsers is going to provide at least as much isolation as anything this extension might do.

But beyond that, there’s the possibility of browsers crashing or freezing, as they are wont to do sometimes. If all my tabs were in the same browser (Firefox in this case), then if it crashed I would lose everything that was open at the time. I’d rather have some stuff open here and other stuff over there, to minimize the damage in case of a crash.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

280park

Reply | Quote

Cybertooth wrote:

But beyond that, there’s the possibility of browsers crashing or freezing, as they are wont to do sometimes. If all my tabs were in the same browser (Firefox in this case), then if it crashed I would lose everything that was open at the time.

In the event of a crash, if prior to the crash, you have had Firefox View on your TabBar (right-click “hamburger”> Customize > drag the ‘Firefox View’ icon to the left position on the TabBar), clicking on that when FF opens again will always give you a way to access recent browsing (e.g., open tabs, recently closed tabs, a history of open tabs).

I do agree with your Post #2644623, which applies to any browser, no matter how many you are using.

2 users thanked author for this post.

280park, Cybertooth

Reply | Quote

Thank you, I hadn’t heard of Firefox View.

According to this article, it requires a Firefox Account to use it. I have way too many online accounts as it is!  🙂

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Cybertooth wrote:

Thank you, I hadn’t heard of Firefox View.

Your choice, of course. With a FF account, you can sync among devices, too, including iOS ones.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Cybertooth – Thank you for the reply.

I like your idea of using multiple browsers to keep the browser developers from knowing all of my internet activity. I never thought of that.

I am very alert to nefarious actors obtaining sensitive information. Currently when I want to access a website that has some of my personal information I first close my browser before reopening it to access the website. When I am finished I close the browser again before doing anything else and have always thought that this routine would prevent nefarious actors from gleaning anything useful from the browser. However, I don’t always or even usually delete all the browser’s history after accessing such a website. Is the browser’s history where the nefarious actors would look to get sensitive information?

1 user thanked author for this post.

Cybertooth

Reply | Quote

IMHO that’s an excellent practice, closing the browser after doing something on a website that involves sensitive information. I believe that @bbearren will go from one website to the browser’s home page, and then move on from there to the next desired site: the idea is to avoid going directly from one site to another one.

If I understand it, the reason for this is that sensitive information could be stored in RAM and doing this clears it.

Then there is the browser cache, which some people will set their browser to clear after every session. I believe that’s another place where nefarious actors could find interesting tidbits about their target.

You mentioned the browser history. I’m not certain about this, but it wouldn’t surprise me to learn that malicious agents could access that remotely too. I’ve always viewed clearing the history as more of a privacy measure to protect against people sitting at our PC and checking out where we’ve been.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

280park

Reply | Quote

Ok, went ahead and installed Feb patches, kind of. Installed without issues the .NET, .NET Framework and MSRT updates. However, since the issue concerning Windows 11 KB5034765 and Windows 10 KB5034763 on systems with a controller is pretty unclear (at least to me), I decided to take the calculated risk of skipping these updates on my W11 and W10 machines respectively. Hopefully, whatever is causing the Windows Explorer error will be fixed with the March CU.

2 users thanked author for this post.

Cijan, LHiggins

Reply | Quote

I have a question: When is it safe to install Windows 11 23H3? I’m wondering about that and how to install it if it is safe to install?

 

The lifespan for 22h2 ends Oct 8th, so I was wondering if there is an article regarding Win 11 23h3 if its safe yet to install?

Reply | Quote

23h2 or 23h3? Sorry I forgot which one is the recent windows 11 update, but can you tell me if it is safe yet to upgrade to 23h2? Yep-that’s the one 23h2?

 

Anyone know if its safe yet to install 23h2 and how do you install it? Do you have to download a certain update to unlock it?

Reply | Quote

Susan’s Master Patch List says this:

I recommend Windows 10 22H2 and Windows 11 22H2 

• Windows 11 22H2: Recommended 

• Windows 10 22H2: Recommended

• Windows 11 23H3 only recommended if you want to fully embrace Copilot

Reply | Quote

I am also wondering about the disappearing taskbar issue.

I know there has been a new preview patch released for W11 that supposedly fixes it.

Have there been any developments for W10?

Do we know what causes this and what to do if it happens?

 

Reply | Quote

Ok, so I updated. Everything went normal and desktop is still there but now I have 2 KB5001716 updates installed. One from October and one from yesterday…. Very strange.

Reply | Quote

And even stranger the update is now in my Programs and Features list. (?).

Reply | Quote

Re: KB5034441

On March 7, following my usual routine for obtaining updates on my Windows 10 Pro machine, I removed the pause from Windows Update (I did not click on “resume updates”). I did not use wushowhide or any other update blocking tools. On March 8 Windows Update downloaded and installed the February cumulative update KB5034763 and the .Net update KB5034685. KB5034441 was not offered.

1 user thanked author for this post.

lmacri

Reply | Quote

Installed the February Tuesday patches today on two Win10/Pro 22H2 laptops without a hitch: KB5034685, KB5035119, KB5034763, and Feb MSRT.

BitLocker is turned off on both machines, but I was curious to see whether KB5034441 (2024-01) would “take”. It installed on the newer laptop (has a Partition-4 size of 990 MB), but failed on the older one (has a smaller Partition 4 size of 504 MB).

For the newer device, its Partition 4 size went from 786 MB used to 813 MB used, leaving 177 MB free in the 990-MB Partition 4 – meaning that the change in used space was a 27MB increase due to a new WinRE.wim file.

The older laptop had a smaller-sized Partition 4 (504 MB total size) of which 52 MB was free. But, KB5034441 failed for lack of sufficient space for the new new 27-MB WinRE.wim file to fit. The ‘Retry’ offer failed as well – too tight a squeeze, I guess.

2 users thanked author for this post.

280park, lmacri

Reply | Quote

LHiggins wrote:

Yes, KB 5034765 is a Win 11 issue … So it seems that there are issues with 5034763 on Win 10 as well – no solutions but several questions on various sites.

Hi LHiggins:

Just an FYI that Susan Bradley’s 12-Mar-2024 March Madness Begins notes that this month’s March 2024 KB5035853 (OS Build 226×1.3296) cumulative Quality Update for Windows 11 22H2 and 23H2 has fixed the error code 0x800F0922 that many Win 11 users saw when the installation of last month’s Win 11 Feb 2024 KB5034765 update (OS Build 226×1.3155) failed at 96% completion.

I still have not seen any documentation that would suggest that your 0x800F0922 error code you saw on your Win 10 v22H2 machine when you tried to install last month’s Feb 2024 KB5034763 (OS Build 19045.4046) cumulative Quality Update for Windows 10 v22H2 is related in any way to the 0x800F0922 error code that many Windows 11 users were seeing (and were able to circumvent by deleting their C:\$WinREAgent folder), or that this month’s March 2024 KB5035845 (OS Build 19045.4170) for Win 10 v22H2 includes any sort of similar bug fix that would eliminate your 0x800F0922 error.

I guess you’ll just have to try installing this month’s March 2024 KB5035845 (OS Build 19045.4170) cumulative Quality Update for Win 10 v22H2 and see if anything you’ve done to this point allows that update to install successfully.
———–
Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24020.7-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

LHiggins

Reply | Quote

lmacri wrote:

I still have not seen any documentation that would suggest that your 0x800F0922 error code you saw on your Win 10 v22H2 machine when you tried to install last month’s Feb 2024 KB5034763 (OS Build 19045.4046) cumulative Quality Update for Windows 10 v22H2 is related in any way to the 0x800F0922 error code that many Windows 11 users were seeing

I haven’t seen any either but I did find that in the event viewer once I figured out how to use that:

LHiggins wrote:

I also found the error code in the event viewer: 0X800F0922 – and Googled that – also didn’t find something that might be a fix that didn’t involve a lot of “work”.

I did also see a few people who had the same issue – I think two others posted here in this discussion, and there was also one who posted in the MS thread I started as well, so there are a few of “us” around.

lmacri wrote:

I guess you’ll just have to try installing this month’s March 2024 KB5035845 (OS Build 19045.4170) cumulative Quality Update for Win 10 v22H2 and see if anything you’ve done to this point allows that update to install successfully.

YEs, guess we’ll see what the March ones do and if there are any problems.

Thanks for the reply!

 

Reply | Quote

And just for some additional info – here’s what was posted in the MS Community forum in the thread I started there by someone else who had the same issue:

I’m running into this same issue. I’ve tried the following:

• Run Windows Update Troubleshooter
• Change the BITS service to start automatically instead of manually or delayed
• With RegEdit I changed HKEY_Local_Machine -> Software -> Policies -> Microsoft -> Windows -> click WindowsUpdate -> Delete or set value “0” to item: DisableWindowsUpdateAccess
• Right click Local Disk -> Properites -> Tools -> Error Checking then click Check
• Run HP Image Assistant (HPIA) – Firmware Pack was needed so I installed that.
• Removed the $WinREAgent folder

Not sure if any of these are germane, and I haven’t tried any except deleting the $WinREAgent folder, so I don’t know it any might help.

When I try the March updates, I am planning to again delete the $WinREAgent folder and also turning off my AV before starting.

Reply | Quote