Bork Tuesday, Any Problems Yet?

I only delete that folder if an endpoint is having issues getting Windows updates. Other than that, I tend to leave it alone.

 

no, because i dont experiences issues where to stop the update service and delete this folder.
if windows throw errors 0x8007... then this may help, only then.
in some cases DISM is needed to repair windows but for sure user has damaged its windows for no reason. leave windows alone, no cleaners, tuners or similar, and windows will work like charme.
in special HOME users are more concerned with issues than PRO users. Guess why.

 

OK, thanks a lot for the documentation. There doesn't seem to be a "law" against it. I think I can recall one instance where a cumulative update was affected in some way by deleting the folder's contents but this has not arisen again. Can't recall specifics but it must not have been that important.

I guess it's "do what you want" but there may be unforeseen risks, as with any other "non-mainstream" clean up.

 

OK, thanks very much, Trooper and Brummelchen. Yes, it's prob. riskier to delete than not. To each his/her own.

 

Thx! I have there empty index-dir folder, probably because I don't use Edge.

 

Nice only one update for Win 10 this month?

 

I have installed Windows 11 and Office 2019 updates and haven't encountered any problems so far.

 

There was a .NET 6.0.16 security update (KB5025221) but that probably depends on what you have installed.

 

Thanks @stapp and @xxJackxx

 

No issues with Win 11 updates.

 

No issues so far with Window 11. Updated about a dozen computers at work.

 

Phased updates for my Win 10 machine this time. A regular automatic update check brought no updates available. I run the check manually and it returned the removal tool update. After the update I had to run the check again to bring up the cumulative update. Strange but both updates went fine without any apparent subsequent issues. I wonder if this was a hiccup only or it somehow related to the empty LCU folder where btw RollupFix folder of 1GB was created after the cumulative update.

 

No problem with W10 CU downloaded from Windows Catalog and manually installed on aging i3 laptop w/ fast SSD. Checking updates afterward, no .NET or MSRT was offered. My latest .NET is 4.8.

ETA: On-screen notification for caps lock and num lock are now gone. There's no LED for those keys, so I had to turn on sounds from the accessibility menu.

ETA 2: The problem resolved after 2 restarts and seems OK today. Just one of the mysteries of Microsoft

 

Only on one Win 10 Pro machine, persistent 0x80073701 error with KB5025221.

No joy with sfc or dism health commands, nor WU Troubleshooter or NVT Win Update Fixer.
However, for once MS support site actually provided the solution (for me): running dism /online /cleanup-image /startcomponentcleanup did the trick.

 

Monthly "C" updates for Windows 11 & 10 released today:
https://www.wilderssecurity.com/thr...fications-for-april-2023.451042/#post-3143185

 

Preview and NET patches installed trouble free here on Win 10. Both required a reboot.

 

No problems with today's patch on my two Win10 machines.

 

Yup, painless as always here.

 

Same here!

 

+1