Recent content by RJARRRPCGP

Went smoothly! Not a stressful patch Tuesday.

I didn't remember seeing this in 2023, but by later on in 2024, there was the web site restructuring.

This seems like old news already. I knew about this transfer since sometime in 2024.

I get AWCC stuff, too, the only problem I have with it, are app crash errors in the event log. It gets installed, because of my Alienware AW3423DWF OLED monitor. I ended up having to remove an entry with Autoruns.

I have one for a spare, too. I tested it and can't find SMART problems. No bad sectors found. I got it in the very-late-2010s, IIRC. I also have a 500 GB Black and no problems found in tests, either. If there are no errors, just lots of power on time, then I would say, go for it.

Well, did Microsoft officially ban Comet Lake, thus treating them like they are Kaby Lake now? I hope that Microsoft didn't ban Vermeer!

Sounds like the "Bluetooth file bug", but I didn't have that issue this time around. That bug seems to happen more on 23H2 than on 24H2 now.

The 24H2 CU went smoothly on my ASRock A320M /ac + Ryzen 7 3700X build.

Well, you got an SSD that's probably better with writes than mine, because yours is 2 TB. But, there's also a read-only-cache, where I can see it helping with systems having a lot of RAM. I use mine to help with writes. Got a very small one configured right now. Now, I can see more RAM used...

It went totally smoothly:

I just got it today. Results looking good, so far.

Yep, updating the BIOS, is like the rabies shot for Raptor Lake!

I had to wipe the SSD and reinstall 24H2 weeks ago, because an update on the RP, borked DISM! Apparently, updating when on the RP channel, when patch-Tuesday overlaps, can severely corrupt Windows, even if not to the point of being unusable. Caused DISM restorehealth function to fail with the...

Mine wasn't perfect, it has the long-standing known issues for 23H2 and 22H2. Mainly CBS reporting corrupted Bluetooth system file(s) after a new CU was applied. It didn't have to be this way, the Bluetooth file issue started in summer, 2022 for 11 users. So, the issue was around since 21H2.

This update has the "Bluetooth file bug". If you uninstall and reinstall the CU, after doing dism /online /cleanup-image /restorehealth , then that issue isn't there.