New
#41
I thought that BETA to RC upgrades werent recommended.
I thought that BETA to RC upgrades werent recommended.
This is Vista to RC1 and Microsoft wants us to do this as it reflects what most people will do when its at RTM.
Exactly, how would we actually report that we couldn't install it in the first place?
Well, I took a look at the official MS forums and it seems Win7 produces log files during the installation? If someone wants to try it now then it might be cool otherwise i'll do it tonight. Here's what the post said:
A likely cause of this is a device installation that is failing to return. You can provide a bit more detail to help pinpoint the issue:
1) What percentage is the "completing installation" at?
2) Analyze and/or post relavent sections of setup log files. Try the following:
If you're not getting anywhere with looking at the log files, post some of the suspicious/relevant information and it might shed more light on the issue.
- Press SHIFT-F10 during the "completing installation" screen, a command prompt opens
- Navigate and review the following log files (start at the end):
- \windows\inf\setupapi.dev.log (shows current device installations)
- \windows\panther\unattendgc\setupact.log (shows the current state of Setup)
Stephen Lodwick [MSFT]
Great! Guessing you mean 4 GBs? Try it with 8 GBs, i doubt RAM is the problem and if it is, i'm sure it'll show it in the logs! Let me know how it goes!
Thanks!
no no, you dont understand, I had 8 GB before and it didnt work, got the 62% problem all the time.
now.. I removed 2 of my sticks.. (got back to 4 GB or 2 x 2 Gb )
and seems it partially worked...
heres what I did.
1.- RESTORE ALL WINDOWS SERVICES TO ITS DEFAULT ( im a gamer, so I dont need a lot of these really dumb services lingering, so I usually have them disabled, so all the disabled were set to manual or automatic depending on their default setting)
2.- REMOVE 2 STICKS OF RAM ( total ram lowered to 4 GB )
3.- and now the interesting part... prior to today, there was no update for the RC installation program, today it downloaded something, I wonder if its something it let me get past this bug.
so I got past the 62%, went to 100%
unfortunately, after the first reboot, I got greeted by the dreaded BSOD.
the error was something like:
PAGE FAULT IN NON PAGED AREA
the file was like : LH1.sys or something similar, it was a 5 key word, unfortunately my computer is .. fast... and dumped the memory really fast.
it was a loop cycle, sometimes it dumps faster and sometimes slower (managed to get a glimpse of the error .. )
interestingly, going into SAFE MODE seems to run correctly until it detects that the installation hasnt been fully completed, and thus wants you to restart and try again the installation.
the attemp "fix your installation" also now appears inthe boot menu, unfortunately, it does the rollback and now fixing actually anything.
so Im pretty sure its either 1.- the mix betwen the 8GB of ram and the 3870 ( some users reported problems with some drivers of ATI and more than 4 GB of ram.. ) 2.- The Services set to default (I seriously dont think so ) 3.- or the extrange patch the setup downloaded before starting the installation.
in short words, yes, I Finally got past the 62% hang bug but got a BSOD after first restart.
I will try more in the weekend since I have to finish some university proyects for Friday.
*addenum*
after reviewing the setupapi.dev.log of my dir c:\windows
it says :
<<< Section end 2009/05/06 13:34:59.227
<<< [Exit status: SUCCESS]
I suppose this means everything went correctly this time on the dev point. (last hardware in the list was the sound device inside my Sapphire 3870 )
the last lines of the other Log files is:
2008-08-03 14:33:55, Info [oobeldr.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_COMPLETE]
2008-08-03 14:33:55, Info [oobeldr.exe] OOBELdr.exe exiting with code [0x0]...
2008-08-03 14:33:55, Info [windeploy.exe] Process exited with exit code [0x0]
2008-08-03 14:33:55, Info [windeploy.exe] RunUserProvidedScript: Found script at [C:\Windows\Setup\Scripts\SetupComplete.cmd]; executing with UI hidden...
2008-08-03 14:34:19, Info [windeploy.exe] RunUserProvidedScript: Successfully executed script; (returned with exit code 0x0)
2008-08-03 14:34:19, Info [windeploy.exe] WinDeploy.exe exiting with code [0x0]
After this, I noticed that there are 2 residual directories that seems to not be removed or cleaned
1.- $Windows.~BT ( wich I suppose is the "upgrade 7 path"
2.-$UPGRADE.~OS ( the backup? )
the first weighing around 3 GB, and the second just 1 GB
I wonder if I should send the files or error logs to microsoft or something.
and before I forget. I wonder if theres more error.logs or something that could tell what file got the bsod.