Repairing Windows 10

Forum Moderators: open

Message Too Old, No Replies

Repairing Windows 10

Repairs needed so soon?

IanCP

9:16 pm on Sep 5, 2015 (gmt 0)

Alert readers will know I upgraded the Desktop PC to Windows 10 as recent as 13th August - that's only 25 days so far.

Reading something almost unrelated, and more on whim that anything else I was prompted to run SFC /Scannow. I used to do that periodically with Windows 8 versions. I like health checks.

Under command prompt (administrator) I ran SFC /Scannow and got this message:

"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log."

Oh dear, here we go. Looking elsewhere for the solution I was again, yes once again, reminded to run:

Dism /Online /Cleanup-Image /RestoreHealth

All files were repaired.

Corrupt files after 25 days? Who would have thought? The same commands apply to Win 7, 8, and 8.1

No matter what your Windows OS - give yourself a "Health Check".

Hoople

3:26 am on Sep 14, 2015 (gmt 0)

Excellent tip! As long as a PC can open a DOS box it can be repaired without an OEM manufacturer's recovery CD.

The CD's/USB's are rather pricey these days, upwards of $75 USD for Windows Vista/Windows7/Windows8.x.

IanCP

7:33 am on Sep 14, 2015 (gmt 0)

How to create a Windows 10 recovery disk
A range of options from Windows and a third-party solution...

[techradar.com ]

J_RaD

3:39 am on Oct 2, 2015 (gmt 0)

you sure you don't have a dying disk? files randomly corrupting for no reason sure is a red flag.

keyplyr

7:18 am on Oct 2, 2015 (gmt 0)

I've had zero Windows 10 problems on 3 machines. Installs (upgrades) were flawless and no issues after 6 months of use.

IanCP

8:37 am on Oct 2, 2015 (gmt 0)

you sure you don't have a dying disk?

For the OS it's a SSD under twelve months old, healthy 100%. Samsung checked. Nary a problem since.

Just one of those things, but I recommend everyone conducts the scans out lined above, only costs a few minutes of time.

Hoople

7:06 pm on Oct 4, 2015 (gmt 0)

How to create a Windows 10 recovery disk
A range of options from Windows and a third-party solution... [techradar.com ]

Most of the OEM machines have a 1-2 recovery disk limit (using the media creation tool). If the user losses it and then needs it they get slammed by the OEM's dedication to license enforcement.

A few OEM machines only let you make a bootup repair disk - the full reinstall checkbox is greyed out! One can't take a bootup repair only recovery disk with a blank hard drive and make a usable machine! Re-installation disks are a different matter and are the pricier of the two. Talk about paying twice for a license!

Hoople

7:17 pm on Oct 4, 2015 (gmt 0)

Under command prompt (administrator) I ran SFC /Scannow and got this message:

"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log."

In that post link about DISM there is a disclosure about SFC stating that it can be run multiple times. Apparently it can only fix so much in each pass.

When an opportunity presented itself last week I ran it 3 times. The third time it completed without complaining about bad files!

J_RaD

9:33 pm on Oct 4, 2015 (gmt 0)

holy cow what is going on..... is your computer sitting on some kinda hex spot? Computer voodoo doll?

OEM recovery, BAH! hate it. My machines i get them patched updated and do a disk image.

IanCP

5:11 am on Dec 2, 2015 (gmt 0)

More on whim again than anything else, also because of a few niggling problems - I was prompted to run SFC /Scannow. I used to do that periodically with Windows 8 versions AND I had previously done it up above in September. I like health checks.

Under command prompt (administrator) I ran SFC /Scannow and again got this message:

"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log."

Oh dear, here we go. Looking elsewhere for the solution I was again, yes once again, reminded to run:

Dism /Online /Cleanup-Image /RestoreHealth

This time it went 100% and it ended with the message [in part]

Error: 0x800f081f

Source files could not be found... [Yadda...]

Back to the drawing board... What does your PC say?

IanCP

8:45 pm on Dec 2, 2015 (gmt 0)

In my case it's all about a file relating to graphics drivers [which don't affect me at all] opencl.dll - the interesting part is there are threads everywhere on the topic, with other different files similarly affected for many.

Why is it interesting? Because it all comes down to a variety of different updates over the last six months for Windows 7, 8 and 10. Here's one "typical example" topic.

[answers.microsoft.com ]

I think I'll forget about it until someone comes up with a real answer because I, and others are not certain SFC /Scannow is correctly reporting corrupt files. The files may not be corrupt. Sample line from the CBS.log:

2015-12-02 22:04:42, Info CSI 00004fa8 Hashes for file member \?\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

Others report confusing findings.