Windows 11 Update 24H2: More errors appeared

“ScanNow” and more

Windows 11 24H2 is not yet running completely smoothly. After two major problems were already known, new ones are now being added.

Shortly after the release of the function update to version 24H2 for Windows 11, two more serious problems became known. On the one hand, the cache, which is full after the update, cannot be deleted. On the other hand, numerous users reported disappearing cursors under certain conditions. We have summarized the reports of problems with 24H2 from the day before.

File validation bug

But that doesn’t seem to be the end of the story. Because now another error has been reported that is related to the system file checker program, which can be triggered via the admin command sfc / scannow. With every new scan, so-called “corrupt files” are found, i.e. defective files or file elements. Despite the display that all files have been repaired, they are shown as defective again when scanned again. The problem was already discovered in a beta and has now crept into the final version. The problem is already known to Microsoft.

Problems with current updates

Then there are further problems with the first updates for Windows 11 24H2. For example, update KB5044284 is a comprehensive security update and the first for 24H2. Numerous users report installation problems that are acknowledged with the error messages 0x800736b3, 0x80070005, 0x800f0838 or 0x8007371b. Other users report that the update process simply freezes at 40 percent progress.

However, there is a workaround for this problem that seems to work.

  1. It Microsoft Update Catalog call.
  2. Click on Download directly next to the Windows version you are using.
  3. Next are the two updates “windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu” and “windows11.0-kb5044284-x64_d7eb7ceaa4798b92b988fd7dcc7c6bb3947 6ccf3.msu” downloaded.
  4. To execute, simply start the installation process by double-clicking on the msu files in the above order.

Next, the system needs to be restarted twice. The system should now run as Windows 11 in build 26100.2033.

Error with OpenSSH

And as if all that wasn’t enough, another error in Windows 11 KB5044284 is also reported. OpenSSH, a program package for file transfer, does not run smoothly. The nasty thing: No error message is output. But the directory should help here C:\ProgramData\ssh\logs delete or rename.

As long as there are no official solutions, it is possible to remove the updates, at the expense of some of the security updates included: simply open the settings, go to “Windows Update”, click on “Update history” and uninstall the updates that are no longer desired.

Source: www.connect.de