locked
Installation process stuck RRS feed

  • Question

  • I'm installing WHS on a dell 8200, 1.8G Pentium, 768MB RAM with an 80M and 500M hard drive(s).  The installation works without an errors whatsoever, then stops at the same point each time.  With 28 minutes to go in "installing windows" the system just stops there.  I've run it several times and left it on overnight twice.  I also just booted up the system without the DVD in and it immediately starts the setup process again.  There are no error messages at all during or after the process.  I'm out of ideas here.
    Sunday, February 14, 2010 10:10 PM

Answers

  • Ok, I'm declaring a partial victory, and closing this as solved.

    I pulled out my NIC, USB and Firewire PCI cards, didn't validate, and got a successful installation.  Victory in that now I have a working OS that I can plow thru updates, drivers etc.  I'll open another Q if something else unsurmountable comes up.

    The first time I ran it 'bare' it failed, so I tried it again successfully.

    Took almost three weeks on and off to get this far.  Jeeez.

    My suggestion to anyone who gets into this mess is to minimalize your hardware to absolute basics - 1 hard disk, dvd drive, graphics card, and build it up from there.  The underlying problem is there were no / few messages or warnings to tell me something was going wrong.  My wild guess is there's some timing sensitivity in some of the processes and my extra hardware was causing a halt. 

    Thanks for the suggestions.
    • Marked as answer by jca2 Sunday, February 21, 2010 9:31 PM
    Sunday, February 21, 2010 9:31 PM

All replies

  • I'm installing WHS on a dell 8200, 1.8G Pentium, 768MB RAM with an 80M and 500M hard drive(s).  The installation works without an errors whatsoever, then stops at the same point each time.  With 28 minutes to go in "installing windows" the system just stops there.  I've run it several times and left it on overnight twice.  I also just booted up the system without the DVD in and it immediately starts the setup process again.  There are no error messages at all during or after the process.  I'm out of ideas here.
    Have you tried runining chkdsk /r on the drive you're installing on?
    Monday, February 15, 2010 12:01 AM
    Moderator
  • Since the installation is in a loop, I can't get to the command line.  The 80G disk was working fine on xp prior to the conversion, and the 500G is brand new.

    Monday, February 15, 2010 12:07 AM
  • Since the installation is in a loop, I can't get to the command line.  The 80G disk was working fine on xp prior to the conversion, and the 500G is brand new.
    You can try removing that drive from the server and running chkdsk /r from a client.
    Monday, February 15, 2010 3:03 AM
    Moderator
  • Also even if the 80GB isn't faulty now, is it worth using a much older drive for your server?
    --
    Tuesday, February 16, 2010 2:54 PM
  • Kariya21,

    It's not clear to me which drive you are referring to here.  I have the 80G as Master and 500G as slave in this configuration.  The installation finds both drives and formats them as best I can tell.

    More info here on the process steps: 

    "collecting information" completes successfully
    "dynamic update" completes successfully
    "preparing install" completes successfully
    "installing windows"  -
                      "installing devices" completes successfully
                      "performing configuration" completes successfully
                      "copying files" completes successfully
                      "completing installation"  sticks at exactly 28 minutes remaining

    I would have to tear down another working system (or create an xp boot CD???) to do a chkdsk here.

    I also attempted connect from a WHSclient and it can't connect / find the new WHS.
    Wednesday, February 17, 2010 1:11 AM
  • Kariya21,

    It's not clear to me which drive you are referring to here.

    Both.  :)

    I have the 80G as Master and 500G as slave in this configuration.  The installation finds both drives and formats them as best I can tell.

    More info here on the process steps: 

    "collecting information" completes successfully
    "dynamic update" completes successfully
    "preparing install" completes successfully
    "installing windows"  -
                      "installing devices" completes successfully
                      "performing configuration" completes successfully
                      "copying files" completes successfully
                      "completing installation"  sticks at exactly 28 minutes remaining

    I would have to tear down another working system (or create an xp boot CD???) to do a chkdsk here.

    No, you just connect them to a working client (either through an extra port on the mobo or using a USB enclosure), then run chkdsk /r from within that OS.

    I also attempted connect from a WHSclient and it can't connect / find the new WHS.

    Wednesday, February 17, 2010 3:24 AM
    Moderator
  • An update as of 2/16 PM.

    1) I pulled the 500G drive and ran the process over from scratch on the 80G drive.  Hangs/stops at 25 minutes to go. (ed. I typo'd this earlier it's 25 minutes, not 28.)

    2) I then pulled the 80G drive and replaced it with the 500G exactly as the 80G drive had been installed.  Again, the exact same result.  (ed. i did have an initial problem here getting the 500G recognized until I figured out the 80 had been strapped CS, not MS as I assumed).  Hangs / stops at 25 minutes. 

    That should eliminate a disk failure or driver problem(?).  Again, the 80G worked flawlessly prior and the 500G is brand new, both have been reformated several times throughout this process.  

    Other observations: the marketing messages and the activity lights on screen are still active, so my machine is not completely locked up.  There's no activity on the DVD drive where the installation disk is located.   I've also run this process from scratch with the ethernet cable disconnected just to try something.

    The software I purchased is powerpack 1, so i'm assuming i'll have to download a bunch of updates when this thing finally completes its install.

    I still don't understand how I can use my WHS server with an unbreakable installation loop and get to a command line.  I don't own a spare usb enclosure, and not anxious to put more cash into this until I know I can get WHS working.

    All of my hardware, NICs, USB, graphics etc worked perfectly w/XP before I started this process.

    Thanks for the ideas, keep 'em coming.
    Wednesday, February 17, 2010 4:12 AM
  • An update as of 2/16 PM.

    1) I pulled the 500G drive and ran the process over from scratch on the 80G drive.  Hangs/stops at 25 minutes to go. (ed. I typo'd this earlier it's 25 minutes, not 28.)

    2) I then pulled the 80G drive and replaced it with the 500G exactly as the 80G drive had been installed.  Again, the exact same result.  (ed. i did have an initial problem here getting the 500G recognized until I figured out the 80 had been strapped CS, not MS as I assumed).  Hangs / stops at 25 minutes. 

    That should eliminate a disk failure or driver problem(?).

    Although unlikely, it could be both hard drives.  Having said that, did you try a different port on the motherboard?  How about a different data cable?

    Again, the 80G worked flawlessly prior and the 500G is brand new, both have been reformated several times throughout this process.  

    Other observations: the marketing messages and the activity lights on screen are still active, so my machine is not completely locked up.  There's no activity on the DVD drive where the installation disk is located.   I've also run this process from scratch with the ethernet cable disconnected just to try something.

    The software I purchased is powerpack 1, so i'm assuming i'll have to download a bunch of updates when this thing finally completes its install.

    I still don't understand how I can use my WHS server with an unbreakable installation loop and get to a command line.  I don't own a spare usb enclosure, and not anxious to put more cash into this until I know I can get WHS working.

    All of my hardware, NICs, USB, graphics etc worked perfectly w/XP before I started this process.

    Thanks for the ideas, keep 'em coming.

    Wednesday, February 17, 2010 4:33 AM
    Moderator
  • This could be due to many different reasons, so I guess we'll have to check eveything we can.
    To check the drives, the best way is to install them on a different system as kariya21 already suggested. If you have a desktop computer working, you should be able to install the drives and run chkdsk.
    To check the RAM sticks, use http://www.memtest.org/#downiso
    It is also possible that your installation media is damaged. Try to create a new installation dvd.

    Wednesday, February 17, 2010 6:46 AM
  • I guess i'll have to buy a eide/usb enclosure to test the drives.  Another alternative is to reload XP (ugh).  Maybe I can use the eide enclosure as a door stop after i'm done.

    Again, i've run this hardware for a few years, and had no BSOGs, hardware glitches or failures the entire time.  I lost a NIC card years ago and replaced it. 

    I purchased this DVD directly so that eliminates download errors.  I considered loading a trial version, then validating it with my code, but the documentation says its a complete reload to do so?
    Wednesday, February 17, 2010 1:22 PM
  • Hi,

    I suggest you try an installation from USB Memory stick.  You will either need to make a copy of your DVD to ISO image and then use the following tool to create a bootable USB stick:
    http://store.microsoft.com/Help/ISO-Tool

    Or use the following guide - but you will need a Vista, W7, 2008 Server machine to do it on:
    http://usingwindowshomeserver.com/2009/05/29/how-to-use-a-usb-stick-to-install-windows-home-server-%E2%80%93-or-anything-else-for-that-matter/

    This will test if either your DVD Drive or the Disc is at fault.

    Let us know how you get on.

    Cheers,
    Al

    --
    Wednesday, February 17, 2010 1:41 PM
  • one other question.  So if i run chkdsk on the drives; do i just reinstall them afterwards and try again?  or is there something in the results of chkdsk that would eliminate a drive as usable?

    thanks for the suggestions!
    Wednesday, February 17, 2010 1:43 PM
  • jca2, first of all, you don't need to buy an external enclosure if you have available ports on a desktop computer. Just turn off that computer, install the drive and boot it up again and run chkdsk.
    If you can't find any errors, you probably don't have any hardware issues with the drives. However, if you have say bad clusters on the drive, the new drive should be under warranty. If the old drive is bad, just use the new one for now and add more drives later for file duplication.
    Wednesday, February 17, 2010 1:49 PM
  • Bjurran,

    The problem with that approach is the system is in a setup loop as I cannot get to a command line to run any commands.  It just keeps restarting setup regardless of if there's a WHS install DVD or not.  Unfortunately, I do not have any ports available on desktops at hand.  I bought the enclosure (a hybrid IDE/SATA so it's got some legs in it) for $30 and i'll run the chkdsk later this evening.

    thanks.

    Wednesday, February 17, 2010 10:51 PM
  • kariya21, et al,

    I ran chkdsk /r on both disks.  There don't appear to be any problems.  Only curious part is both only show 20G, but I guess the rest of the disk is allocated for the NTFS volume of backups.

    please note the stage here: 1) used the 80G only and did an install which failed.  2) used the 500G only and did an install which failed at the same point. 

    Please read thoughts at bottom.

    chkdsk for the 80G:
    K:\>chkdsk /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process.  Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted.  All opened handles to this volume are now invalid.
    Volume label is SYS.

    CHKDSK is verifying files (stage 1 of 5)...
      8864 file records processed.
    File verification completed.
      3 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
      9546 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      8864 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
      8848 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      4843053 free clusters processed.
    Free space verification is complete.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522784 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75477 KB in use by the system.
         65536 KB occupied by the log file.
      19372216 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843054 allocation units available on disk.

    K:\>

    ________________________

    chkdsk for the 500G:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\>k:

    K:\>chkdsk
    The type of the file system is NTFS.
    The volume is in use by another process. Chkdsk
    might report errors when no corruption is present.
    Volume label is SYS.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
      8880 file records processed.
    File verification completed.
      4 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
      9562 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      8880 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522780 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75497 KB in use by the system.
         65536 KB occupied by the log file.
      19372200 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843050 allocation units available on disk.

    K:\>chkdsk /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process.  Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted.  All opened handles to this volume are now invalid.
    Volume label is SYS.

    CHKDSK is verifying files (stage 1 of 5)...
      8880 file records processed.
    File verification completed.
      4 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
      9562 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      8880 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
      8864 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      4843050 free clusters processed.
    Free space verification is complete.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522780 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75493 KB in use by the system.
         65536 KB occupied by the log file.
      19372204 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843051 allocation units available on disk.

    K:\>
    _____________

    At a glance, the directories on the disks appear the same and the chkdsk show only a few files difference between them.

    Is there a log or progress file I can pull off to see where this failed??

    Al - I don't believe my computer will support a USB boot up; this is an older pc and the USB ports aren't in the boot order of the bios.

    Other thoughts?

    Thanks for the help all.

    Thursday, February 18, 2010 2:26 AM
  • kariya21, et al,

    I ran chkdsk /r on both disks.  There don't appear to be any problems.  Only curious part is both only show 20G, but I guess the rest of the disk is allocated for the NTFS volume of backups.

    please note the stage here: 1) used the 80G only and did an install which failed.  2) used the 500G only and did an install which failed at the same point. 

    Please read thoughts at bottom.

    chkdsk for the 80G:
    K:\>chkdsk /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process.  Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted.  All opened handles to this volume are now invalid.
    Volume label is SYS.

    CHKDSK is verifying files (stage 1 of 5)...
      8864 file records processed.
    File verification completed.
      3 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
      9546 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      8864 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
      8848 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      4843053 free clusters processed.
    Free space verification is complete.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522784 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75477 KB in use by the system.
         65536 KB occupied by the log file.
      19372216 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843054 allocation units available on disk.

    K:\>

    ________________________

    chkdsk for the 500G:

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\>k:

    K:\>chkdsk
    The type of the file system is NTFS.
    The volume is in use by another process. Chkdsk
    might report errors when no corruption is present.
    Volume label is SYS.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
      8880 file records processed.
    File verification completed.
      4 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
      9562 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      8880 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522780 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75497 KB in use by the system.
         65536 KB occupied by the log file.
      19372200 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843050 allocation units available on disk.

    K:\>chkdsk /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process.  Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted.  All opened handles to this volume are now invalid.
    Volume label is SYS.

    CHKDSK is verifying files (stage 1 of 5)...
      8880 file records processed.
    File verification completed.
      4 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      0 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 5)...
      9562 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      8880 file SDs/SIDs processed.
    Security descriptor verification completed.
      341 data files processed.
    CHKDSK is verifying file data (stage 4 of 5)...
      8864 files processed.
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      4843050 free clusters processed.
    Free space verification is complete.
    Windows has checked the file system and found no problems.

      20972825 KB total disk space.
       1522780 KB in 8497 files.
          2348 KB in 343 indexes.
             0 KB in bad sectors.
         75493 KB in use by the system.
         65536 KB occupied by the log file.
      19372204 KB available on disk.

          4096 bytes in each allocation unit.
       5243206 total allocation units on disk.
       4843051 allocation units available on disk.

    K:\>
    _____________

    At a glance, the directories on the disks appear the same and the chkdsk show only a few files difference between them.

    Is there a log or progress file I can pull off to see where this failed??

    I still have my install logs on my server (from 2 1/2 years ago) at C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs.

    Al - I don't believe my computer will support a USB boot up; this is an older pc and the USB ports aren't in the boot order of the bios.

    Other thoughts?

    Thanks for the help all.
    How about using a different data cable/different power cable/different port on the motherboard?
    Thursday, February 18, 2010 3:07 AM
    Moderator
  • I am confident the data cable, power cables and ports on the motherboard are physically working perfectly.  Again, all of this equipment was a very well behaved XP machine until I began this upgrade process.  I have a CD-ROM, DVD-ROM and two hard disks which have had no operating problems, ever.  Is there any reason the slave disk should be used as the primary boot disk?  Seems unlikely. 

    I check a few of the logs; located in the WINDOWS directory.  They are pages long.  Here's the end of a couple of them if it helps.

    SETUPLOG:

    02/16/2010 21:42:05,d:\nt\base\ntsetup\syssetup\log.c,316,,C:\$WIN_NT$.~LS\i386\iis6.cab was copied to C:\Inetpub\wwwroot\iisstart.htm.
    02/16/2010 21:42:05,d:\nt\base\ntsetup\syssetup\log.c,316,,C:\$WIN_NT$.~LS\i386\iis6.cab was copied to C:\Inetpub\wwwroot\pagerror.gif.
    02/16/2010 21:42:05,d:\nt\base\ntsetup\syssetup\log.c,316,,Setup has completed copying component files.
    02/16/2010 21:42:05,d:\nt\base\ntsetup\ocmanage\common\ocsetup.c,1822,END_SECTION,Performing configuration...
    02/16/2010 21:42:05,d:\nt\base\ntsetup\ocmanage\common\ocsetup.c,1837,BEGIN_SECTION,Completing installation...

    SETUPERR is empty

    SETUPAPI
    #-166 Device install function: DIF_INSTALLDEVICE.
    #I123 Doing full install of "ROOT\RDP_KBD\0000".
    #I121 Device install of "ROOT\RDP_KBD\0000" finished successfully.
    [2010/02/16 21:35:52 320.142]
    #-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
    #-290 Processing REGISTERDLLS section [WBEM.RegSvr]. Module: "%11%\licwmi.dll", flags: 0x0001, timeout: 60s.
    #E357 Registration of "C:\WINDOWS\system32\licwmi.dll" appears to have hung.
    #E291 Failed to register OLE server "C:\WINDOWS\system32\licwmi.dll". Error 258: The wait operation timed out. 

    SETUPACT
    C:\$WIN_NT$.~LS\i386\iis6.cab was copied to C:\Inetpub\wwwroot\iisstart.htm.
    C:\$WIN_NT$.~LS\i386\iis6.cab was copied to C:\Inetpub\wwwroot\pagerror.gif.
    Setup has completed copying component files.
    desk.cpl:  Using a VRefresh of 60 because VRefresh was 0 or missing in the unattended file
    desk.cpl:  OcManager: unattended BitsPerPel: 32
    desk.cpl:  OcManager: unattended XResolution: 1024
    desk.cpl:  OcManager: unattended YResolution: 768
    desk.cpl:  OcManager: unattended VRefresh: 60

    Note the beginning of SETUPACT seemed to find all my drives, drivres and hardware without any errors.

    ??????

    Thursday, February 18, 2010 4:33 AM
  • is the licwmi.dll a part of the activation process in whs? I remember that name from playing around with win xp.
    If so, what part of the activation happens during the installation? Could it be as simple as a bad NIC driver not allowing the installation to connect to the internet?

    jca2, regarding the slave disk... WHS will be installed on the first disk, which if I understand your setup correctly is whatever is connected to the Primary master IDE/PATA.
    Thursday, February 18, 2010 7:07 AM
  • The reason you only see 20 GB on each disk is because you're only scanning the system partition. This is the same on both disks as you've tried to install on both.
    As you have the installation media and don't have anything important on the disk, you could just format the drive and use the full size as one partition, and scan the disk again. This should tell you if you have any bad sectors outside the area allocated to hold the system partition.
    This will require a complete reinstallation again and you will not be able to resume the installation where it stopped last time.

    /Bjurran, Sweden
    Thursday, February 18, 2010 7:14 AM
  • Bjurran,

    A complete reformat is a good idea to try; nothing to lose and perhaps there's bad clusters out  on the disk somewhere.

    No idea what licwmi.dll is.

    About a month ago, I did upgrade my NIC card to a 1000/100/10, so I almost expected to be asked for a driver (which I have).  It hasn't.  What do you think of taking the NIC out, trying to finish the installation, then reinstalling the NIC if it works?  is the NIC a requirement to finish install?

    Thanks.

    Thursday, February 18, 2010 1:23 PM
  • Bjurran,

    A complete reformat is a good idea to try; nothing to lose and perhaps there's bad clusters out  on the disk somewhere.
    It's worth to try. At least you'll know if the disks are ok or not.

    No idea what licwmi.dll is.
    I guess someone else here would have to answer that. Don't know for sure either.

    About a month ago, I did upgrade my NIC card to a 1000/100/10, so I almost expected to be asked for a driver (which I have).  It hasn't.  What do you think of taking the NIC out, trying to finish the installation, then reinstalling the NIC if it works?  is the NIC a requirement to finish install?

    Thanks.


    I'm not sure if you need the NIC to install or not. I forgot to connect the cable to my server when I reinstalled it so there's no need to have it connected, but I'm not sure if the system requires a NIC or not. However, if connected to the internet during install, you will get most of the updates installed from the beginning.
    Thursday, February 18, 2010 2:47 PM
  • I did a search and licwmi.dll is a microsoft file that causes and error when trying to validate a copy of XP.  http://support.microsoft.com/kb/916247

    They have a fix prescribed for it, but again,  this system is stuck in an install loop that I have to get through to make any windows or command line solutions.

    Still reformatting disks from scratch, will update when finished.
    Saturday, February 20, 2010 11:34 PM
  • An update: still having the same problem with the installation hanging with 25 minutes remaining.

    Here's what's been tried.
    - removed both disks, ran chkdsk /r on both, no errors
    - complete reformat of both disks
    - ran chkdsk again, no errors.

    Reinstalled only the 500MB disk, reran WHS installation, same failure results
    Changed boot order to put hard disk on first.  Reran WHS, same result.
    Tried WHS installation without putting in the product key (this was mentioned elsewhere).  Same result.

    Some research on error 258 also suggest the root problem is the installation validation - i have the original DVD and did not download the software.

    Next:
    - try using a copy of the DVD burned as slow as possible to see if there's something in the disk read amiss.
    - pulling the NIC, USB and Firewire adapters out of the PCI slots to see if there's a driver failures.

    Mostly guessing / fishing here.  Suggestions welcome!
    Sunday, February 21, 2010 6:54 PM
  • Ok, I'm declaring a partial victory, and closing this as solved.

    I pulled out my NIC, USB and Firewire PCI cards, didn't validate, and got a successful installation.  Victory in that now I have a working OS that I can plow thru updates, drivers etc.  I'll open another Q if something else unsurmountable comes up.

    The first time I ran it 'bare' it failed, so I tried it again successfully.

    Took almost three weeks on and off to get this far.  Jeeez.

    My suggestion to anyone who gets into this mess is to minimalize your hardware to absolute basics - 1 hard disk, dvd drive, graphics card, and build it up from there.  The underlying problem is there were no / few messages or warnings to tell me something was going wrong.  My wild guess is there's some timing sensitivity in some of the processes and my extra hardware was causing a halt. 

    Thanks for the suggestions.
    • Marked as answer by jca2 Sunday, February 21, 2010 9:31 PM
    Sunday, February 21, 2010 9:31 PM