none
Installation hangs at "Starting windows" after loading disk.sys

    Question

  • I have not been able to figure out this issue in RC and now trying again with RTM. I am doing an upgrade from vista ultimate, the installation will not go further that disk.sys at the "starting windows" screen. This is with windows 7 RTM (same issue with RC)

    HP x4000 :
    - 2 processor Intel Xeon CPU 2.40ghz
    - 2gb RAM
    - NVIDIA 7800GS AGP
    - LSI logic Ultra 160 PCI SCSI adapter

    I had no issue with Vista.....

    ANYBODY FROM MICROSOFT IS READING THIS??????????
    Sunday, August 23, 2009 5:18 PM

Answers

  • I finally found the solution.  The issue was not with the onboard SCSI controller (although I have disabled the onboard SCSI controller and added an Adaptec 39320A which is compatible with windows 7. 

    The issue was to have hyperthreading turned off for the Xeon processors in the bios of the HP x4000 workstation. 
    Once hyperthreading was turned on windows 7 installation continued with no issues.
    • Marked as answer by jeanfor Sunday, November 08, 2009 4:30 AM
    Sunday, November 08, 2009 4:30 AM

All replies

  • No the hard drive is not active.  I have left this installation alone for hours with no success.....
    Monday, August 24, 2009 3:04 AM
  • Hi,

    You can run Windows 7 Upgrade Advisor, it will tells you about any known compatibility issues.

    The black screen problem is caused by the incompatible device drivers or applications. If the advisor find no compatibility issue with the computer, I suggest you first check the display card.

    If you have another display card, I highly recommend you replace the original display card for test.


    Thomas Lin
    Tuesday, August 25, 2009 9:01 AM
  • I did run the upgrade advisor and it says that my system is fine.  The installation check runs before as well with no issue...

    Jean
    Wednesday, August 26, 2009 11:37 AM
  • Could the LSI Logic Ultra160 PCI SCSI controler be the problem. It is not complaining about it and access the drive with no issue.

    At this point when disk.sys, is there any way to find out which driver fails?
    Wednesday, August 26, 2009 12:48 PM
  • Can you specify how far setup progreses before the crash? What programs do yo have installed?

    Incidentally, this is the driver that loads after disk.sys on my machine:

    Classpnp.sys
    {
     BLOCK "000004B0"
     {
      VALUE "CompanyName", "Microsoft Corporation"
      VALUE "FileDescription", "SCSI Class System Dll"
      VALUE "FileVersion", "6.1.7100.0 (winmain_win7rc.090421-1700)"
      VALUE "InternalName", "Classpnp.sys"
      VALUE "LegalCopyright", "© Microsoft Corporation. All rights reserved."
      VALUE "OriginalFilename", "Classpnp.sys"
      VALUE "ProductName", "Microsoft® Windows® Operating System"
      VALUE "ProductVersion", "6.1.7100.0"
     }
    }

    BLOCK "VarFileInfo"
    {
     VALUE "Translation", 0x0000 0x04B0

    Wednesday, August 26, 2009 1:39 PM
  • It loads the files then gather all the files  and settings and then expand files up to 22%, then reboot. I get the "Starting windows" screen that stops after disk.sys. It does not crash, does not return any message anything just is stuck after disk.sys
    Thursday, August 27, 2009 2:27 AM
  • Did you check the setup log files in your windows folder?  setupact.log; setuperr.log

    http://support.microsoft.com/kb/927521
    Thursday, August 27, 2009 3:32 AM
  • This is whatI am getting for setuperr.log

    2009-08-26 01:35:03, Error                        Number of Enumerated Devices = 14[gle=0x00000103]
    2009-08-26 01:35:04, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:04, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:04, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:04, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:05, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:05, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:05, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:05, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:05, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:06, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:06, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:06, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:07, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:07, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:07, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:17, Error                        Number of Enumerated Devices = 14[gle=0x00000103]
    2009-08-26 01:35:17, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:17, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:17, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:17, Error                        Failed to find driver file path. Error=00000002x
    2009-08-26 01:35:18, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:18, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:18, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:18, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:18, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:35:19, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-08-26 01:44:35, Error      [0x0803db] MIG    IndirectKeyMapper: Cannot find the currently loaded location for hive C:\Users\mforichon\AppData\Local\Microsoft\Windows\UsrClass.dat; giving up (2).
    2009-08-26 01:56:51, Error      [0x0803db] MIG    IndirectKeyMapper: Cannot find the currently loaded location for hive C:\Users\mforichon\AppData\Local\Microsoft\Windows\UsrClass.dat; giving up (2).
    2009-08-26 01:57:28, Error      [0x0803db] MIG    IndirectKeyMapper: Cannot find the currently loaded location for hive C:\Users\mforichon\AppData\Local\Microsoft\Windows\UsrClass.dat; giving up (2).
    2009-08-26 01:58:05, Error      [0x0803db] MIG    IndirectKeyMapper: Cannot find the currently loaded location for hive C:\Users\mforichon\AppData\Local\Microsoft\Windows\UsrClass.dat; giving up (2).
    2009-08-26 02:07:50, Error      [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys, bailing out
    2009-08-26 02:07:50, Error      [0x080389] MIG    Failure while calling IDiscovery->Gather for Plugin={ServerPath="%SystemRoot%\System32\Setup\msdtcstp.dll", CLSID={342992B2-913C-4C36-9DB7-6C68ABD1F079}, ThreadingModel=Apartment}. Error: 0x80100101
    


    And for the other log file:

    2009-08-26 08:31:47, Info       [0x0e00cf] TOOL   Starting OS Rollback... (launched with command line [/noui /FinalCleanup /lang:en-US])
    2009-08-26 08:31:47, Info       [0x0e00d1] TOOL   OS Rollback: NoUI switch.
    2009-08-26 08:31:47, Info                  TOOL   OS Rollback: No rollback operations (left) to perform.
    2009-08-26 08:31:47, Info       [0x0e00d2] TOOL   PERFORMANCE: OS Rollback took 0 seconds.
    2009-08-26 08:31:53, Info                  DIAG   Module path is [D:\$WINDOWS.~BT\Sources\rollback.exe]
    2009-08-26 08:31:53, Info                  DIAG   Module version is [6.1.7600.16385 (win7_rtm.090713-1255)]
    2009-08-26 08:31:53, Info                  DIAG   Module path is [D:\$WINDOWS.~BT\Sources\rollback.exe]
    2009-08-26 08:31:53, Info                  DIAG   Failed install count for build [6.1.7600.16385 (win7_rtm.090713-1255)] is [7]
    2009-08-26 08:31:54, Info                  TOOL   RespawnSelfFromTemp: Copying [D:\$WINDOWS.~BT\Sources\rollback.exe] to [C:\Users\ADMINI~1.000\AppData\Local\Temp\rollback_{680FDFF1-F77D-4BB7-A67F-2DDF986F44EF}\rollback.exe] succeeded (0)
    2009-08-26 08:31:54, Info                  TOOL   RespawnSelfFromTemp: Copying [D:\$WINDOWS.~BT\Sources\en-US\rollback.exe.mui] to [C:\Users\ADMINI~1.000\AppData\Local\Temp\rollback_{680FDFF1-F77D-4BB7-A67F-2DDF986F44EF}\rollback.exe.mui] succeeded (0)
    2009-08-26 08:31:54, Info                  TOOL   RespawnSelfFromTemp: Copying [D:\$WINDOWS.~BT\Sources\unbcl.dll] to [C:\Users\ADMINI~1.000\AppData\Local\Temp\rollback_{680FDFF1-F77D-4BB7-A67F-2DDF986F44EF}\unbcl.dll] succeeded (0)
    2009-08-26 08:31:54, Info                  TOOL   RespawnSelfFromTemp: Copying [D:\$WINDOWS.~BT\Sources\wdscore.dll] to [C:\Users\ADMINI~1.000\AppData\Local\Temp\rollback_{680FDFF1-F77D-4BB7-A67F-2DDF986F44EF}\wdscore.dll] succeeded (0)
    2009-08-26 08:31:54, Info                  TOOL   RespawnSelfFromTemp: Copying [D:\$WINDOWS.~BT\Sources\migisol.dll] to [C:\Users\ADMINI~1.000\AppData\Local\Temp\rollback_{680FDFF1-F77D-4BB7-A67F-2DDF986F44EF}\migisol.dll] succeeded (0)
    2009-08-26 08:31:54, Info       [0x0e00d5] TOOL   End OS Rollback.
    
    Friday, August 28, 2009 1:45 AM
  • Hello Jeanfor,
    Can you send me all the logs from the panther folder.  There is a 6 hour difference in the error mentioned above from the setuperr.log and what is in the setupact.logs.
    Also can you run msinfo32 while in vista and save the output as an NFO file.
    Zip each of the logs up and send to me if you would.
    Darrellg@online.microsoft.com without the online in the email address.

    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, September 01, 2009 11:48 PM
  • I finally found the solution.  The issue was not with the onboard SCSI controller (although I have disabled the onboard SCSI controller and added an Adaptec 39320A which is compatible with windows 7. 

    The issue was to have hyperthreading turned off for the Xeon processors in the bios of the HP x4000 workstation. 
    Once hyperthreading was turned on windows 7 installation continued with no issues.
    • Marked as answer by jeanfor Sunday, November 08, 2009 4:30 AM
    Sunday, November 08, 2009 4:30 AM
  • Yeah I've got an Asus PE-D8 WS and I wanted to install Windows 7 Professional to disks that are attached to it I've got two SSD's in a RAID Stripe, the install was freezing and then I found this answer and I went to the BIOS to Hypertheading and the information in the BIOS said to 'Disable Hyperthreading' in all other OSes other than Windows XP and Linux so yeah turn on hyperthreading for those it says and yeah I just 'Disabled' hyperthreading and now the install it not freezing there anymore.
    Thursday, August 16, 2012 3:31 AM