Windows 10: Bad blocks reported on an SSD - or has parts of W10 got corrupted?

Several times a week when I switch on my W10 PC and before the desktop appears, I see a message saying "scanning and repairing". The percentage complete status of this always stays on "14%" for a good 5 minutes, before quickly finishing, and then I see the desktop. Once there, the Windows UI is extremely sluggish (unusable really) for at least another 5 minutes, before I am able to use the OS OK.

I had a quick look in Windows Event Viewer, and noticed hundreds of "bad block" errors. There are other listed, but by far the largest number are these bad block errors. I spoke to the shop who sold me the SSD HDD that I'm using for W10, and was told that SSDs don't have blocks, and that the problem could be Windows has got corrupted somehow. Either that, or the PC's RAM might be bad.

Any thoughts/comments/advice would be appreciated. Thanks a lot.

:)

 

Stop Error

The store didn't have a SSD !!

Will have to order one online.

I have used some software called - Crystal Disk Info to check the health of my SSD and it reports that it is 86% Good, and no reports of any bad blocks etc. As I type it has frozen again, always after about 10 to 15 minutes and sits in this frozen state
for about, well it is just sitting there. Cursor moves. no timer spinning round just that you can click on anything or use the Ctrl+Alt+Delete buttons.

 

Stop Error

The store didn't have a SSD !!

Will have to order one online.

I have used some software called - Crystal Disk Info to check the health of my SSD and it reports that it is 86% Good, and no reports of any bad blocks etc. As I type it has frozen again, always after about 10 to 15 minutes and sits in this frozen state
for about, well it is just sitting there. Cursor moves. no timer spinning round just that you can click on anything or use the Ctrl+Alt+Delete buttons.

 

Hi W10User123,

Let's treat a SSD the same as a HDD, to not get confused *Smile

To identify corruption in Windows, we'll need to run multiple scans for the system files and the integrity of the drive.





Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums





Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of SFC and post it.

 

Thanks axe0. I went to the hdtune website to get the software, and the supported OSes stated for it are up to W8, but it doesn't state W10. Does hdtune work OK in W10? Also, the download is a 15 day trial version. I guess if I don't want it after that time, I can uninstall this trial version.

 

Although it is outdated, HDTune works/worked fine on all systems I have used it on in the past few months *Smile

The free version has enough features to provide the results I've requested *Smile

 

Thanks axe0. I have started the tests that you suggest. The first batch of screenshots are below. I will try and complete all other tests asap, and report back with those screenshots too.

Health




Scan




Benchmark

 

Chkdsk (attachment included)

Please note that using W10, I pressed the Windows key and also the X key, then the A key to get to an Administrator command prompt box. Once there, I tried to run chkdsk with the /r parameter but Windows told me then that the drive was currently in use and could only run this test if a reboot was done. I rebooted, and the chkdsk operation was run.

 

sfc

I ran sfc, and its progress percent completed value appeared to get 'stuck' on 83% for about 5 minutes. Then it got stuck on 85% for about 30 minutes, at which point I closed the command prompt window, and rebooted the PC.

After this reboot, I reran sfc, and it completing the check. When it completed, I saw the error message that you mention saying that corrupt files had been found.

I then rebooted the PC again, and reran sfc for a third time, and this check also completed. As mentioned on the second run above, I saw the same error message saying that corrupt files had been found.

The following two log files dropbox links are the second and third sfc runs -

Dropbox - CBS (pass 2 of 3).log
Dropbox - CBS (pass 3 of 3).log

sfc screenshot




Thanks a lot for any comments on this data! *Biggrin

 

Although previous chkdsk have come up clean, the last one shows a lot of file system corruption.
I would recommend to run chkdsk another time, if it does not come up clean then there is a deeper problem with the file system.

Sfc shows 1 file missing and 1 file that it can't verify because the manifest is damaged.

Please try following command in an admin command prompt and post a screenshot of the result.
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote]
Code: 2016-12-13 12:32:48, Info CSI 00005759 [SR] Cannot repair member file [l:34]'Windows.Devices.PointOfService.dll' of Microsoft-Windows-Devices-PointOfService-WinRT, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing 2016-12-13 12:32:48, Info CSI 0000575a [SR] Cannot verify component files for Microsoft-Windows-Application-Experience-Mitigations-ACWinRT, version 10.0.14393.447, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (FALSE) 2016-12-13 12:32:48, Info CSI 0000575b@2016/12/13:12:32:48.403 Primitive installers committed for repair 2016-12-13 12:32:48, Info CSI 0000575c [SR] Cannot repair member file [l:34]'Windows.Devices.PointOfService.dll' of Microsoft-Windows-Devices-PointOfService-WinRT, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing 2016-12-13 12:32:48, Info CSI 0000575d [SR] This component was referenced by [l:80]'Package_1438_for_KB3201845~31bf3856ad364e35~amd64~~10.0.1.2.3201845-2919_neutral' 2016-12-13 12:32:48, Info CSI 0000575e@2016/12/13:12:32:48.434 Primitive installers committed for repair[/quote]

 

I've just noticed something - the chkdskresults log file is not being updated correctly/consistently. As per your request, I reran chkdsk, and then looked at the chkdskresults log file, and I notice that the last chkdsk run was logged a couple of days ago. So when chkdsk runs, it seems that sometimes it does not update/write to this log file. Is that a correct interpretation of this unexpectedly 'old' datestamp? I haven't uploaded this file again, as it seems to be the same size and content as the last uploaded file. Below is the DISM screenshot.

DISM

 

If we check the date of the last chkdsk from your upload, I'd say that chkdsk does write to the file.
Code: TimeCreated : 11/12/2016 09:30:20 Message : Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. Stage 1: Examining basic file system structure ... The USA check value, 0x5, at block 0x1 is incorrect. The expected value is 0x10a. The multi-sector header signature in file 0x7900 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30976. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x1d. The multi-sector header signature in file 0x7902 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30978. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x60. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x20e. The multi-sector header signature in file 0x7911 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30993. The USA check value, 0x6e, at block 0x1 is incorrect. The expected value is 0x82. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x4, at block 0x1 is incorrect. The expected value is 0x9. The multi-sector header signature in file 0x7914 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30996. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x9. The multi-sector header signature in file 0x7915 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30997. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xd. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x2d. The multi-sector header signature in file 0x791c is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31004. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x8e. The multi-sector header signature in file 0x791d is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31005. The USA check value, 0x4, at block 0x1 is incorrect. The expected value is 0x2. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x110. The multi-sector header signature in file 0x791f is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31007. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x312d, at block 0x1 is incorrect. The expected value is 0x177. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xcb. The multi-sector header signature in file 0x7932 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31026. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xf. The multi-sector header signature in file 0x7958 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31064. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7959 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31065. The USA check value, 0x32, at block 0x1 is incorrect. The expected value is 0xa0. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x18a2. The multi-sector header signature in file 0x795b is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31067. The USA check value, 0x8001, at block 0x1 is incorrect. The expected value is 0x14a. The USA check value, 0x32, at block 0x1 is incorrect. The expected value is 0x150. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x153. The multi-sector header signature in file 0x795e is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31070. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x2. The multi-sector header signature in file 0x795f is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31071. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x1b7. The multi-sector header signature in file 0x7998 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31128. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xfa. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xf9. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x2. The multi-sector header signature in file 0x799b is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31131. The USA check value, 0x60db, at block 0x1 is incorrect. The expected value is 0x2c. The multi-sector header signature in file 0x79a4 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31140. The USA check value, 0x34, at block 0x1 is incorrect. The expected value is 0x2a. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x9. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x79a7 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31143. The USA check value, 0x2e, at block 0x1 is incorrect. The expected value is 0x2a. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x18. The multi-sector header signature in file 0x79c1 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31169. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x79c2 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31170. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x17. The multi-sector header signature in file 0x79c3 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31171. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xf9. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xf9. The multi-sector header signature in file 0x799a is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31130. Deleted corrupt attribute list entry with type code 128 in file 94051. Unable to find child frs 0x799a with sequence number 0xb6. Deleted corrupt attribute list entry with type code 208 in file 94051. Unable to find child frs 0x799a with sequence number 0xb6. Deleted corrupt attribute list entry with type code 224 in file 94051. Unable to find child frs 0x799a with sequence number 0xb6. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7901 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30977. Deleted corrupt attribute list entry with type code 48 in file 101365. Unable to find child frs 0x7901 with sequence number 0xde. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7910 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30992. Deleted corrupt attribute list entry with type code 48 in file 101371. Unable to find child frs 0x7910 with sequence number 0x55. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7913 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30995. Deleted corrupt attribute list entry with type code 48 in file 101372. Unable to find child frs 0x7913 with sequence number 0x14e. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x65, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7916 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 30998. Deleted corrupt attribute list entry with type code 48 in file 101373. Unable to find child frs 0x7916 with sequence number 0x78. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7930 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31024. Deleted corrupt attribute list entry with type code 48 in file 101401. Unable to find child frs 0x7930 with sequence number 0x1b7. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The USA check value, 0x67, at block 0x1 is incorrect. The expected value is 0x3. The multi-sector header signature in file 0x7933 is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31027. Deleted corrupt attribute list entry with type code 48 in file 101402. Unable to find child frs 0x7933 with sequence number 0xec. The USA check value, 0x8001, at block 0x1 is incorrect. The expected value is 0x14a. The USA check value, 0x8001, at block 0x1 is incorrect. The expected value is 0x14a. The multi-sector header signature in file 0x795c is incorrect. 42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ?? BAAD0........... Deleting corrupt file record segment 31068. Deleted corrupt attribute list entry with type code 48 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. Deleted corrupt attribute list entry with type code 48 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. Deleted corrupt attribute list entry with type code 128 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. Deleted corrupt attribute list entry with type code 208 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. Deleted corrupt attribute list entry with type code 224 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. Deleted corrupt attribute list entry with type code 256 in file 336238. Unable to find child frs 0x795c with sequence number 0x19f. 336896 file records processed. File verification completed. Deleting orphan file record segment 30977. Deleting orphan file record segment 30992. Deleting orphan file record segment 30995. Deleting orphan file record segment 30998. Deleting orphan file record segment 31024. Deleting orphan file record segment 31027. Deleting orphan file record segment 31068. Deleting orphan file record segment 31130. Deleting orphan file record segment 31196. Deleting orphan file record segment 31197. Deleting orphan file record segment 31198. Deleting orphan file record segment 31199. 10329 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x60. The USA check value, 0x6e, at block 0x1 is incorrect. The expected value is 0x82. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xd. The USA check value, 0x4, at block 0x1 is incorrect. The expected value is 0x2. The USA check value, 0x312d, at block 0x1 is incorrect. The expected value is 0x177. The USA check value, 0x32, at block 0x1 is incorrect. The expected value is 0xa0. The USA check value, 0x32, at block 0x1 is incorrect. The expected value is 0x150. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0xfa. The USA check value, 0x34, at block 0x1 is incorrect. The expected value is 0x2a. The USA check value, 0x0, at block 0x1 is incorrect. The expected value is 0x9. The USA check value, 0x2e, at block 0x1 is incorrect. The expected value is 0x2a. Index entry FfuProvider.dll of index $I30 in file 0x137e points to unused file 0x7900. Deleting index entry FfuProvider.dll in index $I30 of file 4990. Index entry FFUPRO~1.DLL of index $I30 in file 0x137e points to unused file 0x7900. Deleting index entry FFUPRO~1.DLL in index $I30 of file 4990. Index entry f_000b37 of index $I30 in file 0x1761 points to unused file 0x795f. Deleting index entry f_000b37 in index $I30 of file 5985. The multi-sector header signature for VCN 0x2 of index $I30 in file 0x21d7 is incorrect. ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................ Correcting error in index $I30 for file 8663. The index bitmap $I30 in file 0x21d7 is incorrect. CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 8663. The down pointer of current index entry with length 0x88 is invalid. 42 57 00 00 00 00 80 00 88 00 70 00 01 00 00 00 BW........p..... d7 21 00 00 00 00 be 01 b0 38 29 4c f9 52 d2 01 .!.......8)L.R.. db ad 29 4c f9 52 d2 01 db ad 29 4c f9 52 d2 01 ..)L.R....)L.R.. b0 38 29 4c f9 52 d2 01 00 20 00 00 00 00 00 00 .8)L.R... ...... 00 11 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ ....... 17 01 70 00 6b 00 67 00 31 00 36 00 31 00 32 00 ..p.k.g.1.6.1.2. 31 00 30 00 30 00 30 00 30 00 30 00 30 00 30 00 1.0.0.0.0.0.0.0. 30 00 30 00 32 00 35 00 2e 00 62 00 69 00 6e 00 0.0.2.5...b.i.n. ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................ Sorting index $I30 in file 8663. Index entry PK97C0~1.BIN of index $I30 in file 0x21d7 points to unused file 0x79a7. Deleting index entry PK97C0~1.BIN in index $I30 of file 8663. Index entry PKDB75~1.BIN of index $I30 in file 0x21d7 points to unused file 0x79dd. Deleting index entry PKDB75~1.BIN in index $I30 of file 8663. Index entry pkg1612100000000032.bin of index $I30 in file 0x21d7 points to unused file 0x79dd. Deleting index entry pkg1612100000000032.bin in index $I30 of file 8663. Index entry pkg161210000000006e.bin of index $I30 in file 0x21d7 points to unused file 0x79a7. Deleting index entry pkg161210000000006e.bin in index $I30 of file 8663. Index entry Cache of index $I30 in file 0x575a points to unused file 0x795e. Deleting index entry Cache in index $I30 of file 22362. Index entry AppxSignature.p7x of index $I30 in file 0x7522 points to unused file 0x7958. Deleting index entry AppxSignature.p7x in index $I30 of file 29986. Index entry APPXSI~1.P7X of index $I30 in file 0x7522 points to unused file 0x7958.[/quote]

Please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial

 

Thanks a lot for your continued assistance axe0. Before I go ahead and do DISM repair procedure as you suggest above, I just want to double-check something please. When I ran chkdsk, it was yesterday on the 13th of Dec. The most up to date datestamp found in the uploaded chkdisk log file is on the 11th, two days prior to this. I wonder if this is correct, and that the writing/updating to this log file is not always occurring?

 

Regarding either the install.wim or install.esd files, please can you tell me if either of them are located on a W10 OEM home edition DVD? The reason I ask is that if one (or perhaps both) file are on there, then I will go and look for it, and then plug in a DVD drive in to my PC. This will save me a presumably large download, as I am using a fairly slow internet connection. Thanks a lot!

 

I hold off to answering that for a few days, I'm a bit ill and can't focus long enough to answer.

You should be able to check it, the files are located in the 'sources' folder.