Is 24H2 fixed?
Is 24H2 fixed?
So, the main issue seems to involve C++. The required "Microsoft Visual C++ 2022 X86 Minimum Runtime" (and the X64 version) isn't installing properly. It keeps reporting a network resource isn't available. I removed the versions listed in the Control Panel and downloaded the latest from Microsoft, but they mention an "older version can't be uninstalled without contacting technical support." Intel Driver and Assist won't work without it either. Adobe also won't run without it, which accounts for about half of my tasks. It's unclear what to do next.
If you haven't, consider using DISM and SFC to fix any corrupted Windows files. You'll need to obtain the most recent Windows ISO for your current version.
1. Double-click the .ISO file to mount it.
2. Launch 'Windows Powershell' or 'Command Prompt' with admin rights (right-click → Run as Administrator).
3. Begin by checking system health using these commands:
3.1 dism /online /cleanup-image /scanhealth
3.2 dism /online /cleanup-image /checkhealth
3.3 dism /online /cleanup-image /restorehealth
4. If you encounter an error about the restore health, use the mounted ISO to identify the correct file and proceed with repairs.
5. Execute the following command (replace X with your drive letter):
DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
6. Next, address any system file damage:
5.1 sfc /scannow
Additional tips before reinstalling:
- It may help to run the command line, which can resolve issues with MSI installers that sometimes freeze.
- Use msiexec.exe /a "package name" during an admin install from an elevated prompt. Installing the latest redistributable packages has often helped with various problems.
- Testing in safe mode can prevent running apps from interfering or forcing a refresh.
- You might need to edit the registry, removing any old installer entries under CurrentVersion in Microsoft/Windows. These remnants could be causing the new installer to reject the update.
It was a clean installation. Mostly, considering the recent BIOS updates from last year, the machine has stayed reliable. The update appeared to function well during Remote Desktop use. Last night I was assembling a new system from used components and found the Andy Warhol effect ongoing. I went back and rolled the update, except for the issue with proper framerate. I tested various cables and inputs, but the laptop kept insisting it wasn’t related to the monitor or cable.
Currently, the PC operates adequately except for a C++ error and its inability to maintain the correct framerate. I doubt SFC/DISM will help since C++ is an add-on. I’m planning another attempt at the update in case it fails again, which would also cost me a day of pay.
The moment it loads in those new drivers for the iGPU, the Warhol starts. I'm currently on the desktop without a driver, but soon it will automatically reinstall it. I plan to try a few quick things if it allows me. I need to check the C++, but I still can't set the proper refresh rate with or without the driver.
DISM doesn't locate anything to fix, while SFC reports everything is fine. The C++ packages still can't be reinstalled because it keeps failing to find the resource or uninstalling the old version. I'm planning to research online to understand the registry steps and decide whether to proceed with a clean install or restore everything from scratch.
I restored the system using the previous 23 load. I didn’t rely on the backup since I thought it might still have the problem. The only bothersome part was how MS seems to be acting strangely about the activation key. After activating the system and registering it with my MS account, they now claim there’s no key left, which prevents activation. I plan to rebuild my old spreadsheet to organize all my keys properly. This process previously cost me a lot of time on this same system, and I wasn’t sure exactly which key I was dealing with.
If you insert an activation key, create a clone on a basic SSD and store it at the end.
Well, let's start over again.
After everything, Windows keeps pushing this update onto me repeatedly. A fresh, untouched backup image was created just once, so it can't be immediately recreated and cause that problem later. I really wish I could avoid all this trouble again.