I didn't know about v1809 being blocked by Microsoft. I knew they removed it because of a bug (thanks God I didn't had upgraded my PC when I downloaded it). I occasionally use it for new installations (or clean installations), I hope it will not harm these PCs.
1) Run the BETA log collector and post a zip into this thread:
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)
2) Open administrative command prompt and type or copy and paste:
chkdsk /x /r /v C:
This may take many hours so plan to run overnight.
C:\WINDOWS\system32>chkdsk /x /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
3) Use the txt and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread using one drive, drop box, or google drive
zbook - >> 1) Run the BETA log collector and post a zip into this thread<<<
The logs displayed problems with corruption on the drive file system and windows defender failure.
There were multiple chkdsk performed.
None were without any findings.
Open administrative command prompt and type or copy and paste:
chkdsk /r /v E:
This may take many hours.
C:\WINDOWS\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
Run HD Tune ( free edition )
Post images of test results for these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan (This may take several hours to run)
Windows defender needs to be troubleshooted.
Do you see an error message or code?
Code:The MFT mirror is different from the MFT. Correcting errors in the Master File Table (MFT) mirror.Code:The shadow copy provider had an unexpected error while trying to process the specified operation. A snapshot error occured while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.Code:Stage 3: Examining security descriptors ... Cleaning up 448 unused index entries from index $SII of file 0x9. Cleaning up 448 unused index entries from index $SDH of file 0x9. Cleaning up 448 unused security descriptors. Security descriptor verification completed. 44492 data files processed.
Code:Event[122]: Log Name: System Source: Ntfs Date: 2018-11-05T15:55:57.543 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-1T59FCE Description: A corruption was discovered in the file system structure on volume E:. A corruption was found in a file system index structure. The file reference number is 0x5000000000005. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".Code:Event[3276]: Log Name: System Source: Service Control Manager Date: 2018-11-08T09:49:41.650 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-1T59FCE Description: The Windows Defender Antivirus Service service failed to start due to the following error: The system cannot find the file specified.
In that case, if the disk is in Warranty, contact the shop for return
zbook - >>> Open administrative command prompt and type or copy and paste:
chkdsk /r /v E:
This may take many hours. <<<
I did see mention of problems with the E drive in the code you posted, however my system drive is the C drive, it has the OS and all my data. I fitted a second SSD in this machine a couple of weeks ago to use as a back-up which the computer labelled as drive E. At present E has a clone of the C drive, made just after it was installed. When I did the clone (in safe mode) Casper Back-Up did say that there were certain files it could not copy - is that what's being picked up here?
Does the E referred to in the chkdsk /r /v E: command refer to the E drive? If so do I need to change this to C ? Or maybe should I physically disconnect the second SSD drive (E) until this is sorted ?
Incidentally you did mention problems with Defender: its operation is very flaky, basically it doesn't work and at least one of its screens denies me access saying that I should consult my IT Dept ! SO, I have Malwarebytes installed and do regular on line Eset virus scans.
zbook - thank you for your perseverance...
1) Download the MCT to the desktop: Download Windows 10
2) Place the computer in clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts | Windows 10 Tutorials
3) Remove any hardware that is attached to the computer so that the only attached hardware are mouse, keyboard, and monitor
4) Make sure that there is only one drive attached to the computer. Other drives can be removed or the cables detached.
5) Open file explorer > identify the iso on the desktop > click on setup or setup.exe > perform an in place upgrade repair while in clean boot > if there are any error messages or codes > make an image > post into the thread
Repair Install Windows 10 with an In-place Upgrade | Windows 10 Tutorials
6) After the in place upgrade repair > open windows defender > perform updates > run a scan > post an image of any error messages or codes.
If by clean boot you mean to boot from DVD, it won't work. To do an inplace upgrade you must run Setup from inside Windows you want to upgrade/repair. I agree about disconnecting all other disks and hardware though. I would also disable in BIOS any non-critical device (audio, ethernet etc) to avoid any driver issue. Once Windows upgrade is complete you can enable them again and connect the rest hardware.
Well I took the bull by the horns yesterday and did a Repair Install Windows 10 with an In Place Upgrade having downloaded the 1803 ISO and burnt it to DVD.
The Repair Install took ~40 minutes, all my files and settings are as before BUT it appears that, as if by magic, all my previous problems have disappeared and Windows 10 is behaving itself again. I eventually had so many issues that it may take a couple more days to confirm all is well but it’s certainly looking good. Everything appears to work though there are some errors appearing in the Event Viewer, predominantly error 55...
A corruption was discovered in the file system structure on volume ??. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>".
However I have in the past worried too much about things appearing in the Event Viewer so for now I’m just going to enjoy things working again…
Thanks to zbook and everyone who offered help and advice, its greatly appreciated. I also need to apologise to Dalchina for not doing the Repair Install earlier when he suggested it was the way to go. I never really felt at home with W10 and it seemed such a terminal step to take but it eventually worked out. I feel better now knowing that I have the disc here if things go pear shaped again – though I’d obviously need to check I was using the latest version…
Thanks again guys, I couldn’t have done it without you…
Glad to see the progress.
You are welcome.
The most recent entries in the event viewer were not available.
If the entries were after prior chkdsk then rerun the chkdsk commands.
If they were before the chkdsk commands then please post the recent reports.
For the file system corruption message please run chkdsk /r /v on all drives using the syntax:
chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
The command may take many hours to run so plan to run overnight.
Use the text and images in this link to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive.
Quote