Hi, go to start, search and type cmd right click on the returned cmd.exe and select "run as administrator", A command prompt will open.(this is called an elevated cmd prompt and is usually required, (regardless of your log on status) also known as a cmd as admin)
I wrote the fix mentioned by cleaverx in post #2 it is however taken out of context, happens a lot.
The fsutil cmd (file system util) will not cause you any harm it is simply a way of reading a flagged (ntfs) disk problem.
the command must be run from an elevated cmd prompt ie:- as admin (as shown)
fsutil dirty query c: (press enter) it will return:-
volume c: is NOT dirty OR is dirty, this simply means the drive is flagged for a chkdsk to be run at boot, this happens, the dirty bit is cleaned and all is well....this does not always happen.
We need you to open a cmd prompt as admin (as shown) and at the command prompt copy paste all the following in red:-
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" > 0 & notepad 0
Press enter, please post the notepad outcome here.
I wrote the fix mentioned by cleaverx in post #2 it is however taken out of context, happens a lot.
The fsutil cmd (file system util) will not cause you any harm it is simply a way of reading a flagged (ntfs) disk problem.
the command must be run from an elevated cmd prompt ie:- as admin (as shown)
fsutil dirty query c: (press enter) it will return:-
volume c: is NOT dirty OR is dirty, this simply means the drive is flagged for a chkdsk to be run at boot, this happens, the dirty bit is cleaned and all is well....this does not always happen.
We need you to open a cmd prompt as admin (as shown) and at the command prompt copy paste all the following in red:-
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" > 0 & notepad 0
Press enter, please post the notepad outcome here.