Recent content by RJARRRPCGP

When I had slowness like that, checked the SSD health and sure enough, the SMART reported bad blocks! I saw something like that with a faulty PNY CS900 SSD. Also, if you have a Samsung 870 Evo, it's faulty, 99.9 percent! TMK, it doesn't take nearly that long, if it's the usual bugs, especially...

Check the SSD health! Makes the SSD sus! I suspect a failing SSD.

There's the OOB update, but looks like it's fine:

Sounds like something that would happen with earlier Windows 10 versions, especially from before 2019. More so if <2018. Same with the "need to spam the retry button" bug for Windows to stop refusing to update.

I retired 23H2 today! I just wiped the Western Digital Black SN850 1 TB SSD and installed 24H2. The updates are usually fine off of a clean install. And that was the case for today.

In my case, IIRC, CBS also reported metadata corruption!

Yeah, it seems to be fine on 24H2, on my other PC. I suspect it's 23H2 with the bug.

Did you check the event log for any errors resembling what I got? You most likely have to do the long steps above with 23H2. The odds of update failure, OTOH, are likely lower with 24H2. In my case, it wasn't just "the Bluetooth file bug".

It went OK with my 24H2 installation on my A320 build.

Issues with this update: You may receive an AppReadiness error with the following error: The Appx operation 'RegisterPackageAsync' on 'MicrosoftWindows.Client.CBS_1000.22700.1077.0_x64__cw5n1h2txyewy' failed for user 'S-1-5-21-3407992842-357079822-2026718286-1001' - Deployment Register...

Here it is after using DISM with restorehealth parameter, multiple reboots and then reinstalling patch-Tuesday: This wasn't smooth, unlike the April patch-Tuesday! :ffs:

Yes! It went smoothly like the March patch-Tuesday: I was thinking that it was going to be a rough one, based on what I saw days and days ago.

I use the scanhealth option.

You only need restorehealth if corruption was found.

Went smoothly! Not a stressful patch Tuesday.