corrupt windows 10 64bit most likely try sfc /scannow but sometimes windows will have to be reinstalled to fix corrupted files

djsabreblade wrote on 2023-12-18, 03:31:

corrupt windows 10 64bit most likely try sfc /scannow but sometimes windows will have to be reinstalled to fix corrupted files

i have to reinstall windows then? =(

It sort of depends if sfc can fix all the potentially corrupted files. For example on my windows 11 laptop i cannot simply install windows from the dvd because its technically too corrupt and will crash while trying to update windows (although mostly everything still works so i don't bother) and the installer crashes eventually to if i use windows update. My laptop cannot be fixed without a complete reinstall of windows but like I said its still 99.5% useable so I don't bother. Only a few windows features are corrupt but can't be repaired by sfc. That means I am stuck on a windows 11 home insider preview build.

That's probably crappy Windows Defender quarantying your files as it slowly crawls your HDD and misidentifies old files as "risk" of some sort.
I have files archived from DOS software in zips, and Defender crawled in and deleted them over time.. You never know when it will suddenly decide they are a risk, even if it passes them ok the first time. An update could cause it to crap out again. Now I config Defender to ignore all my data drives to stop this madness.

Tell some files. Either they will be system files or game files.

I've never had much luck with the stability of Windows 10. I'm lucky to get any more than 2-3 days continual service out of it before some bug or another appears, requiring a reboot to fix it.

Honestly (at least in my opinion) you're better off running games on some older version of Windows, if you can.

Also, Defender can be used by Microsoft to delete anything they don't want you to have, even if it isn't dangerous. Case in point - Out of curiosity I downloaded a few text files that described how to bypass registration requirements, and Defender immediately went on the warpath and tried to delete them. Luckily they were in a read-only location, but it still got quite irate. In the end I didn't need the info and removed them myself.

If you suspect a component stor ecorruption, then do this.

From elevated command prompt, run in this order.
sfc /scannow
dism /online /cleanup-image /checkhealth (should give you message about component store health)
dism /online /cleanup-image /scanhealth (you will almost certainly still have corruptions)
dism /online /cleanup-image /analyzecomponentstore (make note of actual size of component store)
dism /online cleanup-image /startcomponentcleanup (might have to run 'analyze' again and compare)
dism /online cleanup-image /restorehealth

Reboot the PC
open elevated command prompt again
Run sfc /scannow - there should be a message about errors were found but repaired.

DISM /Online /Cleanup-Image /RestoreHealth

i'm afraid of doing all of that and the next time i reboot windows will be screwed =(

Nah, I just tried those things and sure enough it found and fixed a corruption, and Windows is still fine. But it didn't fix the crash I get with 7zip (even after reinstalling it).

ReignerDeustcher wrote on 2023-12-19, 02:27:

i'm afraid of doing all of that and the next time i reboot windows will be screwed =(

DISM is a tool designed by Microsoft to find and repair issues with the Windows image. It might not fix the problem, but it certainly won't make it worse.
I would greatly suggest running them in the order that listed.

Jasin Natael wrote on 2023-12-19, 02:42:

ReignerDeustcher wrote on 2023-12-19, 02:27:

i'm afraid of doing all of that and the next time i reboot windows will be screwed =(

DISM is a tool designed by Microsoft to find and repair issues with the Windows image. It might not fix the problem, but it certainly won't make it worse.
I would greatly suggest running them in the order that listed.

it says:

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

ReignerDeustcher wrote on 2023-12-19, 02:27:

Starting exam in the system. This process will take some time. […]
Show full quote

Starting exam in the system. This process will take some time.

Starting the verification phase of the system examination.
100% verification completed.

Windows Resource Protection found corrupted files, but some could not be repaired.
For online repairs, details are in the CBS log file located at
windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log. For repairs
offline, the details are in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====] The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /analyzecomponentstore

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====]

Component Store Information (WinSxS):

Declared size in Windows Explorer of component store: 10.08 GB

Actual component store size: 9.71 GB

Shared with Windows: 5.64 GB
Backups and features disabled: 3.71 GB
Cache and temporary data: 351.26 MB

Last cleaning date: 2023-11-13 18:50:45

Number of claimable packages: 3
It is recommended to clean the component store: Yes

The operation completed successfully.

C:\WINDOWS\system32>dism /online cleanup-image /startcomponentcleanup

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>dism /online cleanup-image /restorehealth

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

ReignerDeustcher wrote on 2023-12-19, 18:41:

it says: […]
Show full quote

Jasin Natael wrote on 2023-12-19, 02:42:

ReignerDeustcher wrote on 2023-12-19, 02:27:

i'm afraid of doing all of that and the next time i reboot windows will be screwed =(

DISM is a tool designed by Microsoft to find and repair issues with the Windows image. It might not fix the problem, but it certainly won't make it worse.
I would greatly suggest running them in the order that listed.

it says:

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

ReignerDeustcher wrote on 2023-12-19, 02:27:

Starting exam in the system. This process will take some time. […]
Show full quote

Starting exam in the system. This process will take some time.

Starting the verification phase of the system examination.
100% verification completed.

Windows Resource Protection found corrupted files, but some could not be repaired.
For online repairs, details are in the CBS log file located at
windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log. For repairs
offline, the details are in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====] The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /analyzecomponentstore

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====]

Component Store Information (WinSxS):

Declared size in Windows Explorer of component store: 10.08 GB

Actual component store size: 9.71 GB

Shared with Windows: 5.64 GB
Backups and features disabled: 3.71 GB
Cache and temporary data: 351.26 MB

Last cleaning date: 2023-11-13 18:50:45

Number of claimable packages: 3
It is recommended to clean the component store: Yes

The operation completed successfully.

C:\WINDOWS\system32>dism /online cleanup-image /startcomponentcleanup

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>dism /online cleanup-image /restorehealth

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

Generally speaking Code 87 is a syntax error.

Try copying and pasting:

DISM /Online /Cleanup-Image /CheckHealth

You only need one space between each preceding letter and the "/" and no spaces.

Jasin Natael wrote on 2023-12-19, 18:56:

Generally speaking Code 87 is a syntax error. […]
Show full quote

ReignerDeustcher wrote on 2023-12-19, 18:41:

it says: […]
Show full quote

Jasin Natael wrote on 2023-12-19, 02:42:

DISM is a tool designed by Microsoft to find and repair issues with the Windows image. It might not fix the problem, but it certainly won't make it worse.
I would greatly suggest running them in the order that listed.

it says:

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

ReignerDeustcher wrote on 2023-12-19, 02:27:

Starting exam in the system. This process will take some time. […]
Show full quote

Starting exam in the system. This process will take some time.

Starting the verification phase of the system examination.
100% verification completed.

Windows Resource Protection found corrupted files, but some could not be repaired.
For online repairs, details are in the CBS log file located at
windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log. For repairs
offline, the details are in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====] The component warehouse can be repaired.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /analyzecomponentstore

Deployment Image Maintenance and Management Tool
Version: 10.0.19041.844

Image version: 10.0.19045.3448

[==========================100.0%======================= =====]

Component Store Information (WinSxS):

Declared size in Windows Explorer of component store: 10.08 GB

Actual component store size: 9.71 GB

Shared with Windows: 5.64 GB
Backups and features disabled: 3.71 GB
Cache and temporary data: 351.26 MB

Last cleaning date: 2023-11-13 18:50:45

Number of claimable packages: 3
It is recommended to clean the component store: Yes

The operation completed successfully.

C:\WINDOWS\system32>dism /online cleanup-image /startcomponentcleanup

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>dism /online cleanup-image /restorehealth

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

Generally speaking Code 87 is a syntax error.

Try copying and pasting:

DISM /Online /Cleanup-Image /CheckHealth

You only need one space between each preceding letter and the "/" and no spaces.

it worked but now restorehealth is stuck at 62.3%

ReignerDeustcher wrote on 2023-12-19, 20:14:

Jasin Natael wrote on 2023-12-19, 18:56:

Generally speaking Code 87 is a syntax error. […]
Show full quote

ReignerDeustcher wrote on 2023-12-19, 18:41:

it says: […]
Show full quote

it says:

Error: 87

DISM does not recognize the "cleanup-image" command line option.
For more information, run DISM.exe /? to see the help.

The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log

Generally speaking Code 87 is a syntax error.

Try copying and pasting:

DISM /Online /Cleanup-Image /CheckHealth

You only need one space between each preceding letter and the "/" and no spaces.

it worked but now restorehealth is stuck at 62.3%

You might have to click the command prompt window to make it active, and press space bar or a cursor to force the counter to update.