COMMAND PROMPT APPEARS AND DISAPPEARS UPDATE
COMMAND PROMPT APPEARS AND DISAPPEARS VERIFICATION

Phase duration (Free space recovery): 0.00 milliseconds. Stage 5: Looking for bad, free clusters вЂ¦ Phase duration (User file recovery): 2.82 hours. Stage 4: Looking for bad clusters in user file data вЂ¦ Phase duration (USN journal verification): 2.25 seconds. Phase duration (Data attribute verification): 0.95 milliseconds. Phase duration (Security descriptor verification): 323.02 milliseconds.

COMMAND PROMPT APPEARS AND DISAPPEARS VERIFICATION

Security descriptor verification completed. Stage 3: Examining security descriptors вЂ¦Д¬leaning up 1449 unused index entries from index $SII of file 0x9.Д¬leaning up 1449 unused index entries from index $SDH of file 0x9.Д¬leaning up 1449 unused security descriptors. Phase duration (Reparse point and Object ID verification): 64.93 milliseconds. Phase duration (Orphan recovery to lost and found): 1.77 minutes. Phase duration (Orphan reconnection): 7.33 seconds.Д unindexed files recovered to lost and found. Phase duration (Index verification): 4.77 minutes. Phase duration (Bad file record checking): 0.83 milliseconds. Phase duration (Orphan file record recovery): 0.00 milliseconds.

Phase duration (File record verification): 1.54 minutes. Stage 1: Examining basic file system structure вЂ¦ My next step will be the dism when I have some spare time to see if that will fix the problem. From what IвЂ™ve heard, new disks at manufacture have bad sectors that are mapped around, and sectors will go bad as the disk ages. Based on the bad sector count, IвЂ™m not too nervous about the disk at this time. Depending on where the CRC is checked, the errors could be in the disk, the disk read logic, the cable and / or the PC disk interface hardware. IвЂ™ll also run a boot time hardware diagnostic to see what it finds when I have the opportunity. I will try a less aggressive chkdsk first to see whatвЂ™s detected and keep going forward.

COMMAND PROMPT APPEARS AND DISAPPEARS UPDATE

Since things worked fine, Windows update, things donвЂ™t work fine but do in SAFE MODE (and for installers), IвЂ™m suspecting the update and looking for instances of commonality. I run a number of pieces of software (e.g., amateur radio) that must be installed outside the вЂProgram FilesвЂ¦вЂ™ directories to get around permission issues. This still вЂfeelsвЂ™ like a permission mismatch. After it ran, I again ran HDTune and the CRC values were the same as before. I ran the Dell Support assist Hardware analysis which includes Hard Disk analysis. The CRC number was consistent and stable. It appears it reads the disk statistics, correct? The only line that showed attention (blue/green) was CRC errors. I ran HDTune and looked at the Health tab. The other profile command prompt / powershell didnвЂ™t work either.

Command prompt appears and disappears