New Windows Installation and Macrium

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 582
    win10
    Thread Starter
       #21

    Hi Denis - it is R. No, I have not used fsutil dirty query - that's in the command window...looks like.

    I also have figured another solution to this bsod issue. My Dell is a favorite of mine - it carries a few things that I cannot do elsewhere. So to keep everything happy i.e., the Dell, I am going to use it ONLY for those goodies.

    I have the Chromebook which has sufficed in plenty of my recent troubles and a Kindle 10 - both of these do a lot for me. I used to just leave the Dell running all day - now after I do what I need on it, I'm shutting down. I will use the other two devices as necessary.

    Thanks again for all help. Patrice
      My Computer


  2. Posts : 16,577
    Windows 10 Home x64 Version 22H2 Build 19045.3930
       #22

    I suggest you run these commands in an elevated command prompt window.
    fsutil dirty query C:
    ChkDsk C: /F /V /R /X
    [if the first one said it was dirty then run it again after the ChkDsk]


    Denis
      My Computer


  3. Posts : 582
    win10
    Thread Starter
       #23

    To clarify Denis -- fsutil dirty query C: ChkDsk C: /F /V /R /X

    This is how I enter it in the command window? Thanks.
      My Computer


  4. Posts : 16,577
    Windows 10 Home x64 Version 22H2 Build 19045.3930
       #24

    No, they are two separate commands.
    Do this one in an elevated command prompt window
    fsutil dirty query C:
    then do this one in an elevated command prompt window
    ChkDsk C: /F /V /R /X


    Denis
      My Computer


  5. Posts : 582
    win10
    Thread Starter
       #25

    ok - will try it. Thanks.
    Just ran the first command - says C is not dirty. Good, right??

    - - - Updated - - -

    I ran it and it said not dirty - then I had a bsod - which only happens when it is idle btw - never when I'm doing anything. So, ran both entries in command window - after the bsod -- sure hope it helps. Thanks.
    Last edited by patriceltic; 04 May 2023 at 13:33.
      My Computer


  6. Posts : 16,577
    Windows 10 Home x64 Version 22H2 Build 19045.3930
       #26

    Not dirty. Yes, very good.

    Denis
      My Computer


  7. Posts : 582
    win10
    Thread Starter
       #27

    What exactly does not dirty mean. I went on to have a bsod after that ND entry. So I ran it again with the second line. It hopefully fixed the "not-dirty" OS.
    Thanks Denis...
      My Computer


  8. Posts : 16,577
    Windows 10 Home x64 Version 22H2 Build 19045.3930
       #28

    Dirty means that Windows has detected a file system error & will run ChkDsk on its next reboot. Some file system errors cause a Dirty result, others don't.
    Not dirty means it has not detected such an error.


    Denis
      My Computer


  9. Posts : 582
    win10
    Thread Starter
       #29

    OK - thanks.
      My Computer


  10. Posts : 582
    win10
    Thread Starter
       #30

    System wiped out this morning. Will not boot. Says cannot repair - I can't seem to get to the macrium usb. System keeps going to menu of options - I hit f8 repeatedly but doesn't want to go there. Should I go to UEFI settings? I can get there. Thanks.

    Can someone tell me why I can't get to f8. It keeps going to the repair page that does not repair. If I can get to f8, I can run the Macrium backup. and restore the system.

    I wouldn't care but all the commands I have been running as in dirty file - all say no problem. So why does this pc keep failing?

    I still have my clean install usb. Do I have to go back to that? If I do the clean install, then I do the Macrium backup from there as I recall. My system as I have it formatted. Not just windows -- if I could get to the Macrium usb I could do the restore but I can't get there...
    Last edited by patriceltic; 08 May 2023 at 12:11.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:46.
Find Us




Windows 10 Forums