Windows 10: Macrium Reflect claims bad sector(s), Windows 10 says no bad sectors

(For background, I ran a Macrium Reflect image backup on December 22, 2019 and it worked)

So I ran a new Macrium Reflect (free home version) image backup a short while ago, and it failed at the end; I got the "Macrium backup aborted unable to read from disk error code 23" thing, which Macrium says indicates bad sectors: Techie Tuesday: Imaging disks with bad sectors - Macrium Software

However, I ran an in-OS disk check using the method here, and it reported zero bad sectors: Disk Error Checking: How to run CHKDSK in Windows 10

[Note: the page is updated for Win 10, not just 8]

Here's the log from the Event Viewer using the method at thewindowsclub:

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:

Stage 1: Examining basic file system structure ...
506368 file records processed. File verification completed.
12917 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
23038 reparse records processed. 681972 index entries processed. Index verification completed.


23038 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
87803 data files processed. CHKDSK is verifying Usn Journal...
39008992 USN bytes processed. Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1952935422 KB total disk space.
147775520 KB in 366179 files.
245848 KB in 87804 indexes.
678614 KB in use by the system.
65536 KB occupied by the log file.
1804235336 KB available on disk.

4096 bytes in each allocation unit.
488233855 total allocation units on disk.
451058834 allocation units available on disk.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...




So I'm confused. Does anybody have any suggestions? If it helps, I have a Win 7 Pro install on a 2nd drive (not the destination drive of the Win 10 Enterprise image, which would be a third drive; this drive has plenty of room). Haven't tried backing up the 7 drive yet.

Also, I hope you'll bear with me--I injured my arm recently and have been under a lot of stress and re-learning to do things.

Thank you in advance.

Win 10 Enterprise v 1909

- - - Updated - - -

Interestingly, I'm looking at the Event Viewer > Windows Logs > System and I'm seeing a lot of Event ID 7s (all saying The device, \Device\Harddisk0\DR0, has a bad block.) That seems to contradict the in-OS disk check, though it probably can't check all the blocks while the OS is running.

Also received something like 10 or more instances of Event ID 10016:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-QD3JOTC\BrianM SID (S-1-5-21-1447188902-895408778-2406305107-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


I don't quite know what this means, though I did have to create an offline account (though I'm running the online account) in order to try to get the Microsoft Store back (it disappeared, and that was one of the solutions to attempt).

- - - Updated - - -

(Errors were stated as being found when I ran the in-OS check on the 7 disk, so I'm gonna run a repair on that.)

:)

 

Macrium Reflect claims bad sector(s), Windows 10 says no bad sectors

Ah, that occurred to me about 30 seconds before I saw this post. So I'm checking all disks now for errors. Thank you.

- - - Updated - - -

Didn't occur to me to go to the disk maker's website for a potential tool. I'm trying to avoid fully reinstalling 10, but I may have to. Thank you.

- - - Updated - - -

I will revisit this thread to update. I need to rest my arm and my brain.

- - - Updated - - -

Ok, I repaired the 7 install and the large data HDD, and did a segregated backup of the 10 drive with Macrium--it created a system image but I set it so that it would "move" (or notify me that it wouldn't be backed up?) the 1 bad sector it found:

"Read Error: bad sector found in cluster 45219732
Bad Sectors: WARNIG [sic]: 1 Clusters located in bad sectors. Data may be lost."

I'm going to attempt repairing this at a different time. There's too much gaming to be done right now .

Since the reason for this post has been resolved, I'll mark it as such. Thank you folks.

 

Macrium Reflect claims bad sector(s), Windows 10 says no bad sectors

(For background, I ran a Macrium Reflect image backup on December 22, 2019 and it worked)

So I ran a new Macrium Reflect (free home version) image backup a short while ago, and it failed at the end; I got the "Macrium backup aborted unable to read from disk error code 23" thing, which Macrium says indicates bad sectors: Techie Tuesday: Imaging disks with bad sectors - Macrium Software

However, I ran an in-OS disk check using the method here, and it reported zero bad sectors: Disk Error Checking: How to run CHKDSK in Windows 10

[Note: the page is updated for Win 10, not just 8]

Here's the log from the Event Viewer using the method at thewindowsclub:

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:

Stage 1: Examining basic file system structure ...
506368 file records processed. File verification completed.
12917 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
23038 reparse records processed. 681972 index entries processed. Index verification completed.


23038 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
87803 data files processed. CHKDSK is verifying Usn Journal...
39008992 USN bytes processed. Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1952935422 KB total disk space.
147775520 KB in 366179 files.
245848 KB in 87804 indexes.
678614 KB in use by the system.
65536 KB occupied by the log file.
1804235336 KB available on disk.

4096 bytes in each allocation unit.
488233855 total allocation units on disk.
451058834 allocation units available on disk.

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...




So I'm confused. Does anybody have any suggestions? If it helps, I have a Win 7 Pro install on a 2nd drive (not the destination drive of the Win 10 Enterprise image, which would be a third drive; this drive has plenty of room). Haven't tried backing up the 7 drive yet.

Also, I hope you'll bear with me--I injured my arm recently and have been under a lot of stress and re-learning to do things.

Thank you in advance.

Win 10 Enterprise v 1909

- - - Updated - - -

Interestingly, I'm looking at the Event Viewer > Windows Logs > System and I'm seeing a lot of Event ID 7s (all saying The device, \Device\Harddisk0\DR0, has a bad block.) That seems to contradict the in-OS disk check, though it probably can't check all the blocks while the OS is running.

Also received something like 10 or more instances of Event ID 10016:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-QD3JOTC\BrianM SID (S-1-5-21-1447188902-895408778-2406305107-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


I don't quite know what this means, though I did have to create an offline account (though I'm running the online account) in order to try to get the Microsoft Store back (it disappeared, and that was one of the solutions to attempt).

- - - Updated - - -

(Errors were stated as being found when I ran the in-OS check on the 7 disk, so I'm gonna run a repair on that.)

 

Bad sectors

ok so ive used those commands but it says it couldnt run because the volume is in use by another process and it will be checked when it restarts but when it does, nothing happens

so ive got a new ssd, im planning on migrating my current c drive onto the new one but thats the one with bad sectors. if i moved it onto the new one not sure if i would still have windows 10 or the bad sectors