Beware of Fast Startup in multi-boot scenarios!

Page 2 of 2 FirstFirst 12

  1. Posts : 1,255
    Windows 10 Pro
       #11

    Pirx said:
    Huh? You would of course check the volumes during system initialization; all you need to do is check if the volume has seen any writes after the time of "shutdown". On an NTFS volume that's trivial to do and will only take microseconds, literally. All they need to do is do it...
    Details please. My statements came from experience as an amateur programmer.
      My Computer


  2. Posts : 913
    CP/M
       #12

    Well-known problem starting at Windows 8. "Fast Startup" is modified hibernation (without user session) so it leaves disk volumes/filesystems in Dirty Shutdown state (does not dismount them) after "shutdown". Much worse, FCU re-enables this "feature" without notifying users.
    Last edited by muchomurka; 11 Nov 2017 at 21:56.
      My Computer


  3. Posts : 63
    Windows
    Thread Starter
       #13

    LMiller7 said:
    Details please. My statements came from experience as an amateur programmer.
    You access the USN change journal using functionality analogous to fsutil's USN journal query functions.
    See here for a brief overview of the architecture of Change Journal records on NTFS volumes. More details on how to work with Change Journal records are here.

    Do you have experience with Windows systems-level programming if I may ask?
      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 16:42.
Find Us




Windows 10 Forums