Windows 10 bug corrupts my hard drive

f23948 · 16 Jan 2021

Please I would like to know do i need to reinstall Windows 10 or repair the hard drive or change the hard drive?
Source: Bleeping Computer

- - - Updated - - -

After i restarted my computer, my computer automatically checks the hard drive for errors but i think my hard drive has no errors then my computer restarted automatically then my computer boots normally and i think my hard drive has no errors can i use it?

- - - Updated - - -

I think my hard drive looks ok?

Windows 10 bug corrupts my hard drive-untitled.png

Samuria · 16 Jan 2021

You need to understand windows scans the drive and if it finds bad sectors it writes the as bad so next time you test it shows NO errors as it doesnt scan the bad block again.

The best test is to goto the makers website and get their disk test specif to your drive and see wha that says From the test it look like the drive is on its way out and you need to get a new drive and do a clean install. On no account try cloning the drive to a new one as it will write the bad block to the new drive and cant be reveresed

f23948 · 16 Jan 2021

Samuria said:

You need to understand windows scans the drive and if it finds bad sectors it writes the as bad so next time you test it shows NO errors as it doesnt scan the bad block again.

The best test is to goto the makers website and get their disk test specif to your drive and see wha that says From the test it look like the drive is on its way out and you need to get a new drive and do a clean install. On no account try cloning the drive to a new one as it will write the bad block to the new drive and cant be reveresed

I think I am going to wait until the MIcrosoft fix the bugs

zbook · 16 Jan 2021

In the video the first portion was blurry.

In the link end users had variable results.

There was a warning not to run the command.

Do you make free backup images?

How come you're pausing upgrades and remaining with Windows 1809?

Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

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

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

f23948 · 16 Jan 2021

zbook said:

In the video the first portion was blurry.

In the link end users had variable results.

There was a warning not to run the command.

Do you make free backup images?

How come you're pausing upgrades and remaining with Windows 1809?

Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

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

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

no thank you i want to wait until the microsoft fix the bugs

zbook · 16 Jan 2021

If there is a specific problem that you want Microsoft to be aware of and potentially fix you can use the feedback hub:
https://support.microsoft.com/en-us/...3-f66612949332

f23948 · 16 Jan 2021

zbook said:

If there is a specific problem that you want Microsoft to be aware of and potentially fix you can use the feedback hub:
https://support.microsoft.com/en-us/...3-f66612949332

i think the MIcrosoft is already aware of it

- - - Updated - - -

i run the command prompt as administrator, i did type chkdsk c: and my hard drive has no errors, can i use it?

zbook · 16 Jan 2021

Please run:
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Bree · 16 Jan 2021

zbook said:

If there is a specific problem that you want Microsoft to be aware of and potentially fix you can use the feedback hub...

The specific problem is the one @Brink reported here...

Brink said:

Microsoft to fix critical NTFS vulnerability on Windows 10 PCs >> OnMSFT.com

Known and Resolved issues for Windows 10 version 20H2 - post #297

f23948 said:

i think the MIcrosoft is already aware of it
- - - Updated - - -
i run the command prompt as administrator, i did type chkdsk c: and my hard drive has no errors, can i use it?

Like you, I read the article Brink gave a link for, followed its link to Bleeping Computer and read the instructions for triggering the bug that's supposed to corrupt the hard drive. It's just too tempting not to test it

Unlike you I took Bleeping Computer's warning to heart...

...this vulnerability can be triggered by a single-line command to instantly corrupt an NTFS-formatted hard drive, with Windows prompting the user to restart their computer to repair the corrupted disk records....

*WARNING* Executing the below command on a live system will corrupt the drive and possibly make it inaccessible. ONLY test this command in a virtual machine that you can restore to an earlier snapshot if the drive becomes corrupted.*WARNING*

...ran the test in a virtual machine and.....

....nothing happened.

If it had done the damage that Bleeping Computer said it would, then Windows would have immediately reported a disk corruption and scheduled a Chkdsk at boot. You'd have see this notification...

The fact that I didn't see this means I didn't corrupt the file system by testing that supposedly 'fatal' command.

Even if it had corrupted your drive, it's the NTFS file system that's supposed to suffer corruption, not the physical had drive. Nothing that, in the worst case, a format and reinstalling Windows wouldn't fix.

No, you haven't damaged the drive and can continue to use it.

EDIT: I see from your video that you did get the notification....

Windows 10 bug corrupts my hard drive-image.png

Check the System log in your Event log for Event 55 (Ntfs) as described by Bleeping Computer. If you don't find it then you haven't corrupted your system.

After the drives become corrupted, Windows 10 will generate errors in the Event Log stating that the Master File Table (MFT) for the particular drive contains a corrupted record.

Windows 10 bug corrupts your hard drive on seeing this file's icon

The corruption (if any) is only in the NTFS file system, the drive itself cannot be harmed. Restoring a system image from before your 'experiment' or reformatting and a clean install of Windows would fix it.

f23948 · 16 Jan 2021

zbook said:

Please run:
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

i disabled UAC

and here is my file attached