none
Windows 7 NTFS vs. Windows XP NTFS

    Pergunta

  • Hi!

    I've created a WinXP & Win7 dual OS config on my computer.
    (It is not a dual-boot configuration since I have to choose which one I want to boot up in BIOS.)

    My problem is the different way the two OS handle NTFS partitions.

    If a check any of my NTFS drives from XP it "corrects" some errors in the filesystem and vice versa from 7. There are no problems if i'm useing just XP OR just 7, but by switching between them XP and 7 always does some "corrections".

    I guess it is because they handle NTFS volumes slightly different way, but it's really anoying, even while there are no appearant modifications made to my data.

    As far as I know XP uses NTFS v5.1, while Vista uses v6.0 (?) so 7 should use at least v6.

    Now if Win7 can see that my old partitions is in v5.1 format, why is it forces v6.x (or whatever it uses) checks and repairs?
    And vice versa:
    If XP can see, that my Win7 partition is in newer format, than 5.1, how come it tries to "repair" it?


    segunda-feira, 2 de março de 2009 09:53

Respostas

  • Although XP found the drive clean, Window 7 fails to recognize a SID (Security IDentifiers) from XP.  There is nothing wrong, per se, with your drive; Windows 7 just throws a fit with your XP SIDs.

    quarta-feira, 4 de março de 2009 04:49

Todas as Respostas

  • I have both XP and Windows 7 and change boot in the BIOS as you do, however I have no problem relating to any "corrections" when switching.
    segunda-feira, 2 de março de 2009 20:09
  • What “corrections” is chkdsk applying?  If it pertains to security descriptors, that is probably more related to the differing security accounts than to different versions of NTFS.

     

    segunda-feira, 2 de março de 2009 23:10
  • I will run a check from XP and from 7, to provide you exact information.

    Until that here are the typical lines from Win7 chkdsk logs after XP found them clean, regardless of which drive i've checked:

    eg1: (F:\)
    CHKDSK is verifying security descriptors (stage 3 of 3)...
    Deleting an index entry with Id 311 from index $SII of file 9.
    Deleting an index entry with Id 311 from index $SDH of file 9.
      120128 file SDs/SIDs processed.                                       

    Cleaning up 24 unused index entries from index $SII of file 9.
    Cleaning up 24 unused index entries from index $SDH of file 9.
    Cleaning up 24 unused security descriptors.
    Security descriptor verification completed.
    ------

    eg2: (F:\)
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      120128 file SDs/SIDs processed.                                       

    Cleaning up 17 unused index entries from index $SII of file 0x9.
    Cleaning up 17 unused index entries from index $SDH of file 0x9.
    Cleaning up 17 unused security descriptors.
    Security descriptor verification completed.
    ------

    eg3: (G:\)
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      123392 file SDs/SIDs processed.                                       

    Cleaning up 29 unused index entries from index $SII of file 0x9.
    Cleaning up 29 unused index entries from index $SDH of file 0x9.
    Cleaning up 29 unused security descriptors.
    Security descriptor verification completed.
    ------

    eg4: (D:\)
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      44032 file SDs/SIDs processed.                                       

    Cleaning up 1 unused index entries from index $SII of file 0x9.
    Cleaning up 1 unused index entries from index $SDH of file 0x9.
    Cleaning up 1 unused security descriptors.
    Security descriptor verification completed.


    terça-feira, 3 de março de 2009 13:21
  • Although XP found the drive clean, Window 7 fails to recognize a SID (Security IDentifiers) from XP.  There is nothing wrong, per se, with your drive; Windows 7 just throws a fit with your XP SIDs.

    quarta-feira, 4 de março de 2009 04:49
  • Are there any possible ways, to get rid of this?
    quarta-feira, 4 de março de 2009 18:40
  • Don't run CHKDSK from Windows 7 on a Windows XP BOOT volume?!
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    sexta-feira, 13 de março de 2009 00:13
  • All of my drives are affected...
    And usually it runs automatically during boot up.
    sexta-feira, 13 de março de 2009 11:10
  • Well, you can always just skip the disk check by "pressing any button" when it first boots up.

    Use the chkntfs command to disable a volume from auto check with the /x parameter.

    chkntfs [/x volume [...]]

    For example, to disable this on C drive, type:

    chkntfs /x c:


    You can also disable it via Registry.


    Here's a registry file to disable disk check upon boot, save it as a .reg file. Its for WINXP, not 7.

    Windows Registry Editor Version 5.00 
     
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager] 
    "AutoChkTimeOut"=dword:0000000 
     
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager] 
    "BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\ 
    00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00 
     
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] 
    "SFCScan"=dword:00000000 
     
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\cleanuppath] 
    @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 
    00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,63,00,6c,00,\ 
    65,00,61,00,6e,00,6d,00,67,00,72,00,2e,00,65,00,78,00,65,00,20,00,2f,00,44,\ 
    00,20,00,25,00,63,00,00,00 

    Added by Forum Moderator:

    Warning: While this solution solves the issue or problem, serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. For more information about modifying the registry, see Microsoft support article 256986.
    sexta-feira, 13 de março de 2009 11:27