"setup is restarting"
in [Setup and Deployment]
|
From: wyocowboy on 22 Sep 2006 12:43 Ok, I need some advice from an MVP or similar that really knows his/her stuff. I fix computers for a living, so amateurs need not apply... I've done maybe 50-70 repair reinstalls of xp. Most everytime, it has gotten through the install process, if not fixing the problem at hand. A customer brought in a Dell 4400 with a dead cpu and motherboard, so we replaced it with an Intel motherboard that looks identical to the Dell m/b, which is NLA. My boss initiated the repair reinstall as per KB824125 while I was out of the office on a service call. Somewhere during the GUI setup phase, it blue-screened with a bugcheck, and unfortunately, the error was not recorded. By the time I inherited this, it was stuck in a "setup is restarting" loop. The loop pattern is that shortly after shortly after this message, the mouse pointer appears, and then a error message flashes on the screen for a half-second or so and then it resets. The first error message that was presented was referencing SAM and system security, and it looks like the stop code is 0xc00000189, and this is not in the MSDN bug check code database. Viewing the setuperr.log from RC or BartPE shows "setup encountered an error while trying to set system security. An extended error has ocurred." So, thinking that perhaps another attempt at a repair reinstall might save the day (and the customer's programs, data, etc) I booted from the customer's Dell OS CD and and started over. Setup informed me that it "had already attempted to upgrade" but would try again if I pressed enter, so I did and it got through the "blue screen" phase of setup, restarted and again aborted at the same point, but this time it complains about Not enough virtual memory or paging file quota is available to complete the required operation" - but for some reason, this error does not get written to setuperr.log, which shows the contents and date/time stamp corresponding to the previous error. I did boot into BartPE and had a look at the registry setting for the pagefile, and it shows the path as c:\pagefile.sys, and the file does exist. Note that this issue does not appear to be SLP or hardware related. I was able do a fresh install from the Dell CD onto a spare hard drive and it completed without errors. I was also able to a parallel install onto the customer's hard drive, and this also worked. One bit of news that may or not be a factor: when the boss initiated the repair reinstall, he used a generic OEM CD w/sp2. This machine shipped in 2002 (pre-sp2) but browsing the c:\windows directory shows that sp1 had been installed, but sp2 had not. I am guessing that a service or something to do with XPSP2 being used on a repair reinstall over XPSP1 has something to do with the problem. What I would really like to know at this point is if there is a way of causing xp to forget about the previous setup attempts. There has to be a file or setting or folder that can be deleted or modified to do so, but so far, I haven't found one. While I can get the system running by doing a fresh install or using the parallel install, doing so means that the customer would have to reinstall all programs, recreate all user IDs, email accounts and move the data where it needs to go - a lot of work. Anyone out there know how to break the "setup is restarting" loop? I don't know that it will save the day, but a fresh repair reinstall seems like the next thing to try.
From: Carey Frisch [MVP] on 22 Sep 2006 13:24 The Dell Reinstallation CD is only valid with a Dell motherboard. The CD is BIOS-locked to the Dell motherboard and if a non-Dell motherboard was installed, setup will not complete. You'll need to purchase a "Full Version" of Windows XP, then perform a "Repair Install" as the Dell license is no longer valid without a genuine Dell motherboard installed. Changing a Motherboard or Moving a Hard Drive with XP Installed http://www.michaelstevenstech.com/moving_xp.html How to Perform a Repair Install of Windows XP http://www.michaelstevenstech.com/XPrepairinstall.htm -- Carey Frisch Microsoft MVP Windows - Shell/User Enjoy all the benefits of genuine Microsoft software: http://www.microsoft.com/genuine/default.mspx ------------------------------------------------------------------------------------------------------------ "wyocowboy" wrote: | Ok, I need some advice from an MVP or similar that really knows his/her | stuff. I fix computers for a living, so amateurs need not apply... | | I've done maybe 50-70 repair reinstalls of xp. Most everytime, it has gotten | through the install process, if not fixing the problem at hand. A customer | brought in a Dell 4400 with a dead cpu and motherboard, so we replaced it | with an Intel motherboard that looks identical to the Dell m/b, which is NLA. | My boss initiated the repair reinstall as per KB824125 while I was out of the | office on a service call. Somewhere during the GUI setup phase, it | blue-screened with a bugcheck, and unfortunately, the error was not recorded. | | By the time I inherited this, it was stuck in a "setup is restarting" loop. | The loop pattern is that shortly after shortly after this message, the mouse | pointer appears, and then a error message flashes on the screen for a | half-second or so and then it resets. The first error message that was | presented was referencing SAM and system security, and it looks like the stop | code is 0xc00000189, and this is not in the MSDN bug check code database. | Viewing the setuperr.log from RC or BartPE shows "setup encountered an error | while trying to set system security. An extended error has ocurred." | | So, thinking that perhaps another attempt at a repair reinstall might save | the day (and the customer's programs, data, etc) I booted from the customer's | Dell OS CD and and started over. Setup informed me that it "had already | attempted to upgrade" but would try again if I pressed enter, so I did and it | got through the "blue screen" phase of setup, restarted and again aborted at | the same point, but this time it complains about Not enough virtual memory or | paging file quota is available to complete the required operation" - but for | some reason, this error does not get written to setuperr.log, which shows the | contents and date/time stamp corresponding to the previous error. | | I did boot into BartPE and had a look at the registry setting for the | pagefile, and it shows the path as c:\pagefile.sys, and the file does exist. | | Note that this issue does not appear to be SLP or hardware related. I was | able do a fresh install from the Dell CD onto a spare hard drive and it | completed without errors. I was also able to a parallel install onto the | customer's hard drive, and this also worked. | | One bit of news that may or not be a factor: when the boss initiated the | repair reinstall, he used a generic OEM CD w/sp2. This machine shipped in | 2002 (pre-sp2) but browsing the c:\windows directory shows that sp1 had been | installed, but sp2 had not. I am guessing that a service or something to do | with XPSP2 being used on a repair reinstall over XPSP1 has something to do | with the problem. | | What I would really like to know at this point is if there is a way of | causing xp to forget about the previous setup attempts. There has to be a | file or setting or folder that can be deleted or modified to do so, but so | far, I haven't found one. | | While I can get the system running by doing a fresh install or using the | parallel install, doing so means that the customer would have to reinstall | all programs, recreate all user IDs, email accounts and move the data where | it needs to go - a lot of work. | | Anyone out there know how to break the "setup is restarting" loop? I don't | know that it will save the day, but a fresh repair reinstall seems like the | next thing to try.
From: wyocowboy on 22 Sep 2006 13:57 "Carey Frisch [MVP]" wrote: > The Dell Reinstallation CD is only valid with a Dell motherboard. The CD is BIOS-locked to the Dell motherboard and if a non-Dell > motherboard was installed, setup will not complete. You'll need to purchase a "Full Version" of Windows XP, then perform a "Repair > Install" as the Dell license is no longer valid without a genuine Dell motherboard installed. You need to go back and re-read what I wrote. This is not an SLP issue. Setup from the Dell CD did complete when I did a fresh install onto the spare hard drive. It is true that Dell has in the past locked their OS CD to the BIOS, but what happens in that case is that setup aborts early on, informing you that you don't have a Dell motherboard, so setup cannot continue. At least that is what happened when I tried it with a Win2kProfsp2/3 vintage. Assume for the moment that I know what I am talking about and back to my question: Do you know of a way to break the setup loop? > Changing a Motherboard or Moving a Hard Drive with XP Installed > http://www.michaelstevenstech.com/moving_xp.html > > How to Perform a Repair Install of Windows XP > http://www.michaelstevenstech.com/XPrepairinstall.htm > > -- > Carey Frisch > Microsoft MVP > Windows - Shell/User > > Enjoy all the benefits of genuine Microsoft software: > http://www.microsoft.com/genuine/default.mspx > > ------------------------------------------------------------------------------------------------------------ > > "wyocowboy" wrote: > > | Ok, I need some advice from an MVP or similar that really knows his/her > | stuff. I fix computers for a living, so amateurs need not apply... > | > | I've done maybe 50-70 repair reinstalls of xp. Most everytime, it has gotten > | through the install process, if not fixing the problem at hand. A customer > | brought in a Dell 4400 with a dead cpu and motherboard, so we replaced it > | with an Intel motherboard that looks identical to the Dell m/b, which is NLA. > | My boss initiated the repair reinstall as per KB824125 while I was out of the > | office on a service call. Somewhere during the GUI setup phase, it > | blue-screened with a bugcheck, and unfortunately, the error was not recorded. > | > | By the time I inherited this, it was stuck in a "setup is restarting" loop. > | The loop pattern is that shortly after shortly after this message, the mouse > | pointer appears, and then a error message flashes on the screen for a > | half-second or so and then it resets. The first error message that was > | presented was referencing SAM and system security, and it looks like the stop > | code is 0xc00000189, and this is not in the MSDN bug check code database. > | Viewing the setuperr.log from RC or BartPE shows "setup encountered an error > | while trying to set system security. An extended error has ocurred." > | > | So, thinking that perhaps another attempt at a repair reinstall might save > | the day (and the customer's programs, data, etc) I booted from the customer's > | Dell OS CD and and started over. Setup informed me that it "had already > | attempted to upgrade" but would try again if I pressed enter, so I did and it > | got through the "blue screen" phase of setup, restarted and again aborted at > | the same point, but this time it complains about Not enough virtual memory or > | paging file quota is available to complete the required operation" - but for > | some reason, this error does not get written to setuperr.log, which shows the > | contents and date/time stamp corresponding to the previous error. > | > | I did boot into BartPE and had a look at the registry setting for the > | pagefile, and it shows the path as c:\pagefile.sys, and the file does exist. > | > | Note that this issue does not appear to be SLP or hardware related. I was > | able do a fresh install from the Dell CD onto a spare hard drive and it > | completed without errors. I was also able to a parallel install onto the > | customer's hard drive, and this also worked. > | > | One bit of news that may or not be a factor: when the boss initiated the > | repair reinstall, he used a generic OEM CD w/sp2. This machine shipped in > | 2002 (pre-sp2) but browsing the c:\windows directory shows that sp1 had been > | installed, but sp2 had not. I am guessing that a service or something to do > | with XPSP2 being used on a repair reinstall over XPSP1 has something to do > | with the problem. > | > | What I would really like to know at this point is if there is a way of > | causing xp to forget about the previous setup attempts. There has to be a > | file or setting or folder that can be deleted or modified to do so, but so > | far, I haven't found one. > | > | While I can get the system running by doing a fresh install or using the > | parallel install, doing so means that the customer would have to reinstall > | all programs, recreate all user IDs, email accounts and move the data where > | it needs to go - a lot of work. > | > | Anyone out there know how to break the "setup is restarting" loop? I don't > | know that it will save the day, but a fresh repair reinstall seems like the > | next thing to try. > >
From: Kamal on 29 Sep 2006 13:31 Sorry mate no one will help you here. "wyocowboy" <wyocowboy(a)discussions.microsoft.com> wrote in message news:D0F8D5EF-3D65-4F11-938F-F8CE6EA26947(a)microsoft.com... > > > "Carey Frisch [MVP]" wrote: > >> The Dell Reinstallation CD is only valid with a Dell motherboard. The CD >> is BIOS-locked to the Dell motherboard and if a non-Dell >> motherboard was installed, setup will not complete. You'll need to >> purchase a "Full Version" of Windows XP, then perform a "Repair >> Install" as the Dell license is no longer valid without a genuine Dell >> motherboard installed. > > You need to go back and re-read what I wrote. This is not an SLP issue. > Setup from the Dell CD did complete when I did a fresh install onto the > spare > hard drive. > > It is true that Dell has in the past locked their OS CD to the BIOS, but > what happens in that case is that setup aborts early on, informing you > that > you don't have a Dell motherboard, so setup cannot continue. At least that > is > what happened when I tried it with a Win2kProfsp2/3 vintage. > > Assume for the moment that I know what I am talking about and back to my > question: Do you know of a way to break the setup loop? > > >> Changing a Motherboard or Moving a Hard Drive with XP Installed >> http://www.michaelstevenstech.com/moving_xp.html >> >> How to Perform a Repair Install of Windows XP >> http://www.michaelstevenstech.com/XPrepairinstall.htm >> >> -- >> Carey Frisch >> Microsoft MVP >> Windows - Shell/User >> >> Enjoy all the benefits of genuine Microsoft software: >> http://www.microsoft.com/genuine/default.mspx >> >> ---------------------------------------------------------------------------?--------------------------------- >> >> "wyocowboy" wrote: >> >> | Ok, I need some advice from an MVP or similar that really knows his/her >> | stuff. I fix computers for a living, so amateurs need not apply... >> | >> | I've done maybe 50-70 repair reinstalls of xp. Most everytime, it has >> gotten >> | through the install process, if not fixing the problem at hand. A >> customer >> | brought in a Dell 4400 with a dead cpu and motherboard, so we replaced >> it >> | with an Intel motherboard that looks identical to the Dell m/b, which >> is NLA. >> | My boss initiated the repair reinstall as per KB824125 while I was out >> of the >> | office on a service call. Somewhere during the GUI setup phase, it >> | blue-screened with a bugcheck, and unfortunately, the error was not >> recorded. >> | >> | By the time I inherited this, it was stuck in a "setup is restarting" >> loop. >> | The loop pattern is that shortly after shortly after this message, the >> mouse >> | pointer appears, and then a error message flashes on the screen for a >> | half-second or so and then it resets. The first error message that was >> | presented was referencing SAM and system security, and it looks like >> the stop >> | code is 0xc00000189, and this is not in the MSDN bug check code >> database. >> | Viewing the setuperr.log from RC or BartPE shows "setup encountered an >> error >> | while trying to set system security. An extended error has ocurred." >> | >> | So, thinking that perhaps another attempt at a repair reinstall might >> save >> | the day (and the customer's programs, data, etc) I booted from the >> customer's >> | Dell OS CD and and started over. Setup informed me that it "had already >> | attempted to upgrade" but would try again if I pressed enter, so I did >> and it >> | got through the "blue screen" phase of setup, restarted and again >> aborted at >> | the same point, but this time it complains about Not enough virtual >> memory or >> | paging file quota is available to complete the required operation" - >> but for >> | some reason, this error does not get written to setuperr.log, which >> shows the >> | contents and date/time stamp corresponding to the previous error. >> | >> | I did boot into BartPE and had a look at the registry setting for the >> | pagefile, and it shows the path as c:\pagefile.sys, and the file does >> exist. >> | >> | Note that this issue does not appear to be SLP or hardware related. I >> was >> | able do a fresh install from the Dell CD onto a spare hard drive and it >> | completed without errors. I was also able to a parallel install onto >> the >> | customer's hard drive, and this also worked. >> | >> | One bit of news that may or not be a factor: when the boss initiated >> the >> | repair reinstall, he used a generic OEM CD w/sp2. This machine shipped >> in >> | 2002 (pre-sp2) but browsing the c:\windows directory shows that sp1 had >> been >> | installed, but sp2 had not. I am guessing that a service or something >> to do >> | with XPSP2 being used on a repair reinstall over XPSP1 has something to >> do >> | with the problem. >> | >> | What I would really like to know at this point is if there is a way of >> | causing xp to forget about the previous setup attempts. There has to be >> a >> | file or setting or folder that can be deleted or modified to do so, but >> so >> | far, I haven't found one. >> | >> | While I can get the system running by doing a fresh install or using >> the >> | parallel install, doing so means that the customer would have to >> reinstall >> | all programs, recreate all user IDs, email accounts and move the data >> where >> | it needs to go - a lot of work. >> | >> | Anyone out there know how to break the "setup is restarting" loop? I >> don't >> | know that it will save the day, but a fresh repair reinstall seems like >> the >> | next thing to try. >> >>
|
Pages: 1 Prev: 0x0000019 Next: Adding Drivers to a Windows XP Installation |