Win7 SP1 RC1 stuck at 9% for over three hours
-
31 Ekim 2010 Pazar 02:48
Win7 Professional 32-bit and SP1.
Uninstalled SP1 beta from my #2 system. Took about 45 minutes, reboot, after about 90 minutes the desktop never appeared and the reboot was cancelled. That partition was reformatted and Win7 Pro 32-bit reinstalled.
Using the DVD created with 7601.17105.100929-1730-3_Update_Sp_Wave1-RC1SP1.1_DVD.iso as an image an update was attempted. Failed with message: ERROR_INVALID_FUNCTION(0x80070001). Spent about an hour trying to determine cause of the error message. Based on comments I found in Microsoft forums about this problem I decided to copy the DVD to a hard drive partition and install the update from there. The copying of the file windows6.1-KB976932-x86.exe failed - tried three times. Had to go online and re-download the file as a separate item.
Tried the update again from the partition holding windows6.1-KB976932-x86.exe. It took about 2½ hours to complete and a reboot was required. Reboot selected and the blue screen appeared with the message: Configuring Service Pack, 9% complete, Do not turn off your computer. This message has not changed for 3+ hours and I doubt this action, whatever it is, would be stuck at 9% for that length of time.
At this time I appear to have no recourse but to ignore the message about not turning off the computer and to again reformat the Win7 drive/partition and install everything new and forget about updating using SP1 RC1.
This system is a dual-boot setup with XP Pro w/SP3. I can boot into XP and use Explorer to look at the Win7 folders/files installation. Is there anything I can check that may provide information or an answer of some kind to this problem?
Tüm Yanıtlar
-
31 Ekim 2010 Pazar 11:38
boot from the Windows 7 DVD or Windows Recovery Environment (F8) and run the command prompt and run this:
DISM /image:C:\ /cleanup-image /revertpendingactions
(replace C: with the drive where you installed Windows 7)
This reverts all pending operations. Now you should go back to Windows 7 RTM.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
01 Kasım 2010 Pazartesi 20:39
Did revert - Message: Installation was not successful - Error:0x800f0845; selecting Details - nothing - no Details provided.
"Go online to learn more about this issue" - selected: online - no help.Search on 0x800f0845 came up empty - nothing relevant listed using Google or Bing - any ideas?
-
01 Kasım 2010 Pazartesi 21:36Are you able to get the files from the CBS folder of your installed Windows 7?
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
02 Kasım 2010 Salı 21:21No folder labelled CBS found; what is/was its supposed location? Checked the root of all my drives/partitions.
-
02 Kasım 2010 Salı 23:22The files are stored here:
C:\Windows\Logs\CBS
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
03 Kasım 2010 Çarşamba 21:55
CBS.log file found - dated today - why today, is it updated daily? Size is 2,909Kb.
Appears CBS.log file was started on 11-01 at 14:26 with last entry appearing to be the time I looked at it: 11-03 at 14:28 - odd.
What am I supposed to be looking for? File is too big to input here.
-
03 Kasım 2010 Çarşamba 22:49
upload all CBS files to your SkyDrive:
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/- Düzenleyen Andre.ZieglerMicrosoft Community Contributor 09 Kasım 2010 Salı 11:59
-
04 Kasım 2010 Perşembe 03:52
For some reason I can no longer reply to this posting from my #1 system in XP Pro or XP Pro x64 - just get little spinning circle when I post - has happened before - no one has responded to why. That's why my name has changed. I'm assuming I'll lose the ability soon to post from my #2 also; if past is prologue.
Don't have SkyDrive - prefer not to; have no immediate/regular/long term use for one.
Looked through CBS.log file section dated 2010-11-01 and culled out items that indicated Failure of some kind. I did notice that in many places there was mention of the error: 0x800f0805 - same error number I mentioned above.
Unable to find any mention of why the system did not shut down and reboot.
Failures-CBS.log
2010-11-01 14:33:33, Info CBS Session: 30112268_1869112672 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:33, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 14:33:33, Info CBS Session: 30112268_1869425172 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:33, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 14:33:33, Info CBS Session: 30112268_1870362672 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:33, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 14:33:33, Info CBS Session: 30112268_1871456422 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:33, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 14:33:34, Info CBS Session: 30112268_1871612672 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:34, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 14:33:35, Info CBS Session: 30112268_1881925172 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:35, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 14:33:35, Info CBS Session: 30112268_1881925173 initialized by client WindowsUpdateAgent.
2010-11-01 14:33:35, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 19:58:30, Info CBS Session: 30112313_3561668336 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:30, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 19:58:30, Info CBS Session: 30112313_3562762086 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:30, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 19:58:30, Info CBS Session: 30112313_3564637086 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:30, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 19:58:30, Info CBS Session: 30112313_3566355836 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:30, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 19:58:30, Info CBS Session: 30112313_3566668336 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:30, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 19:58:32, Info CBS Session: 30112313_3579324586 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:32, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 19:58:32, Info CBS Session: 30112313_3579480836 initialized by client WindowsUpdateAgent.
2010-11-01 19:58:32, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:28:50, Info CBS Session: 30112318_287505684 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:50, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:28:50, Info CBS Session: 30112318_287505685 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:50, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:28:50, Info CBS Session: 30112318_292349434 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:50, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:28:51, Info CBS Session: 30112318_294380684 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:51, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:28:51, Info CBS Session: 30112318_294536934 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:51, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:28:53, Info CBS Session: 30112318_313443184 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:53, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:28:53, Info CBS Session: 30112318_313599434 initialized by client WindowsUpdateAgent.
2010-11-01 20:28:53, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:42:44, Info CBS Session: 30112320_41828905 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:44, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:42:44, Info CBS Session: 30112320_41985155 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:44, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:42:44, Info CBS Session: 30112320_42453905 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:44, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:42:45, Info CBS Session: 30112320_44641405 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:45, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:42:45, Info CBS Session: 30112320_46360155 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:45, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 20:42:48, Info CBS Session: 30112320_78449998 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:48, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2010-11-01 20:42:48, Info CBS Session: 30112320_78635545 initialized by client WindowsUpdateAgent.
2010-11-01 20:42:48, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]2010-11-01 21:38:17, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:38:17, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:38:17, Info CBS WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]2010-11-01 21:39:53, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:39:53, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:39:53, Info CBS WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]2010-11-01 21:40:50, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:40:50, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
2010-11-01 21:40:50, Info CBS WER: Failure is not worth reporting [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]Hope this helps.
-
04 Kasım 2010 Perşembe 04:06I had it stuck at 9 percent earlier today to when it wanted to shut down & setup the package.... I only let it sit at 9 percent for 10 minutes and then I hit the reset button, windows loaded up, said configuring and this time around didn't get stuck, configured and installed it.
-
04 Kasım 2010 Perşembe 06:58ModeratörPlease disable antivirus and firewall. If the issue still occurs, re-download the package.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
04 Kasım 2010 Perşembe 12:13
Every LiveID (the email you use to sign in here to the forums) has a SkyDrive: http://skydrive.live.com/Don't have SkyDrive
Sign in with your LiveID and you can upload 25GB of data and share them with your friends.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
04 Kasım 2010 Perşembe 22:18
I had it stuck at 9 percent earlier today to when it wanted to shut down & setup the package.... I only let it sit at 9 percent for 10 minutes and then I hit the reset button, windows loaded up, said configuring and this time around didn't get stuck, configured and installed it.
Tried that - did not work - reboot and ended up at same place; 9% and it stayed there for an hour before I opted to run 'revert' procedure as mentioned above. -
04 Kasım 2010 Perşembe 22:19
Please disable antivirus and firewall. If the issue still occurs, re-download the package.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
Firewall and antivirus had been disabled prior to initial attempt. -
08 Kasım 2010 Pazartesi 22:21
Decided to try again; evening of 06 Nov, with hardware changes required when Win7 SP1 beta was successfully installed.
Hard drives are SATA and are connected to a Promise SATA 150TX2 add-in controller card. Booted into BIOS and turned off items pertaining to PATA CD/DVD drives - had to do this to get SP1 beta to install.
Win7 SP1 RC was copied to a partition and windows6.1-kb976932-x86.exe selected and run from there. Took about 2½ hours for install and reboot message to appear. Reboot selected and the blue screen appeared with the message: Configuring Service Pack, 9% complete, Do not turn off your computer. Waited an hour and no change from 9%. Killed power - went to bed. Next morning, system started and Win7 selected from dual-boot menu; got blue screen and 9% message again. Waited two hours, no change. Killed power.
Used ****** for access to the creation of SkyDrive storage space - CBS.log file uploaded to folder Win7 SP1 folder I created and listed as public - I have no idea what to do next to allow public access to this file and folder; no hint at the Windows Live web page. I signed out of Skydrive - clueless as to how it functions or what information I am supposed to provide to allow someone access to this folder.
Again: From Microsoft Forums:
Boot > Win7 > F8 > Recovery Environment: DISM /image:H:\ /cleanup-image /revertpendingactions (Had to use floppy to install SATA controller drivers)Service Pack changes were reverted and I was back at Win7 RTM with error message: installation was not successful > Details> Error: 0x800f0845 - same as earlier.
NOTE: Had to boot into Win7 32-bit to reply to this message - reply fom within XP Pro failed to post; only got spinning circle.
- Düzenleyen ChiefZeke 09 Kasım 2010 Salı 23:39 remove e-mail address
-
09 Kasım 2010 Salı 12:00please remove your email and post a link to your public SkyDrive folder.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
09 Kasım 2010 Salı 23:43
please remove your email and post a link to your public SkyDrive folder.
E-Mail address removed.
Though I created a SkyDrive folder and uploaded the log file I have no idea as to where it is or how to get to it - when I created it I got no feedback on what I created or where it is located - it just said you did it. This fiasco with this SkyDrive thing is why I said above I had no use for it, did not want it, and would prefer not to have to mess with it.
The only time anyone has asked if I had one and would I post to it was in this forum, two times over the past year or so, and both concerning Win7 SP1 - one about beta and this one about RC.
I just went to Windows Live and Skydrive to see if I could determine what I did yesterday - still have no answer. Do not know where the log file is and/or how to tell anyone else were it is to get it. A total waste of time and useless for anything I am interested in doing online.
-
10 Kasım 2010 Çarşamba 00:20
zip all files into 1 ZIP and upload it to Mediafire:
http://www.mediafire.com
and post the link here.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
10 Kasım 2010 Çarşamba 01:02
Hi ChiefZeke,
I'd like to assist you with this problem. If you aren't comfortable with using SkyDrive. I've created a workspace where you can send me your files. Please go to:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=87b01d63-e06e-40bd-8585-3fdc315ac572
It will ask for a password, it is: UQy]1@]_jIzQ
Please share the following files:
- Everything in C:\Windows\Logs\CBS
- C:\Windows\inf\setupapi.dev.log
- C:\Windows\system32\winevt\logs\System.evtx
- C:\Windows\system32\winevt\logs\Application.evtx
Was the "blue donut" spinning while it was stuck at 9%?
Thanks,
Mark [MSFT]
-
12 Kasım 2010 Cuma 22:43
Mark,
Five files were uploaded to the location specified - thanks for the help and I hope you can determine an answer.
The 'blue donut' was spinning all of the time things were stuck at 9% - no indication the system was hung.
It's not that I'm not comfortable using SkyDrive, it's that, as I said, once I logged into SkyDrive, created the folder and uploaded the CBS.log file I had no idea as to 'where I was' in the sense of seeing the information that said: here is the URL that is the location of the folder you have made available to the public.
I'm guessing here that the https: *** you posted above is the same info I had expected to be readily available - my issue is I could not tell anyone even today, where that is or how to figure it out. If it is on the SkyDrive page somewhere/anywhere then I was totally unwaware of that fact then and am still unable to say where it is now.
Did I miss something somewhere in that process?
Also, for what it's worth - I still cannot reply to any mesage in this forum from within XP - I am sending this from Win7 64-bit.
-
02 Aralık 2010 Perşembe 06:09
Hi ChiefZeke,
I'd like to assist you with this problem. If you aren't comfortable with using SkyDrive. I've created a workspace where you can send me your files. Please go to:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=87b01d63-e06e-40bd-8585-3fdc315ac572
It will ask for a password, it is: UQy]1@]_jIzQ
Please share the following files:
- Everything in C:\Windows\Logs\CBS
- C:\Windows\inf\setupapi.dev.log
- C:\Windows\system32\winevt\logs\System.evtx
- C:\Windows\system32\winevt\logs\Application.evtx
Was the "blue donut" spinning while it was stuck at 9%?
Thanks,
Mark [MSFT]
Mark,It's been 19 days since I posted a reply - would be nice to know if the information helped solve the probkem.
-
03 Aralık 2010 Cuma 18:27
Hi ChiefZeke,
Apologize for the delayed response. I'm looking at this now.
Mark [MSFT]
-
03 Aralık 2010 Cuma 23:12
ChiefZeke,
Is there any chance I can get the files from you again? I wasn't able to receive them the first time. For some reason I didn't receive notifications from this thread or the file share mechanism.
Mark [MSFT]
-
04 Aralık 2010 Cumartesi 03:35Files re-uploaded at 1930 hours California time. Hope they get to you this time; also glad I saved them.
-
06 Aralık 2010 Pazartesi 22:47
ChiefZeke,
Is there any chance I can get the files from you again? I wasn't able to receive them the first time. For some reason I didn't receive notifications from this thread or the file share mechanism.
Mark [MSFT]
Mark,Files were re-uploaded two days ago - no notice to you again?
-
07 Aralık 2010 Salı 04:20
Hi ChiefZeke,
I got the notice this time. I'll have a look and let you know.
Mark [MSFT]
-
07 Aralık 2010 Salı 21:40
Hi ChiefZeke,
Unfortunately the logs don't tell me as much as I'd hoped. There is indeed a hang. It happens during the servicing of drivers but I cannot find any information on the nature of the problem. I found this error in the System event log which appears on every startup:
"Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware."
Are you using some special or uncommon hardware? It maybe your controller card. The only thing I can advise is check on the manufacturer websites for updated drivers. Also check for updates for your BIOS.
Are you still experiencing the hang? Have you been able to successfully install the SP?
Mark [MSFT]
-
07 Aralık 2010 Salı 22:01
Mark,
you should tell him to enable verbose logging:
system environment variable: WINDOWS_TRACING_FACILITY_POQ_FLAGS with a value of 10000 .
and install the Sp1 again and upload the new logs. Maybe this tells you more.
André
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
09 Aralık 2010 Perşembe 04:24
Hi ChiefZeke,
Unfortunately the logs don't tell me as much as I'd hoped. There is indeed a hang. It happens during the servicing of drivers but I cannot find any information on the nature of the problem. I found this error in the System event log which appears on every startup:
"Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware."
Are you using some special or uncommon hardware? It maybe your controller card. The only thing I can advise is check on the manufacturer websites for updated drivers. Also check for updates for your BIOS.
Are you still experiencing the hang? Have you been able to successfully install the SP?
Mark [MSFT]
The hardware in the system in question is:
Foxconn 661MXPlus motherboard
Promise SATA150TX2Plus/TX4 controller card
Intel Celeron 2.5Ghz cpu
Kingston KVR400X64C3AK2/2G memory
Western Digital 320Gb SATA drives (two each)
Creative PC-DVD Encore Dxr3 Decoder Card
Creative 5x and 6x DVD drives
ATI Radeon X1650 512Mb of memory, AGP video card
Creative SoundBlaster Audigy2 Platinum audio cardAs far as I know the motherboard and the Promise controller card are up-to-date as far as firmware is concerned. There are no SATA ports on the motherboard; the hard drives are connected to the Promise controller card.
The initial install of Win7 Pro 32-bit went fine with the inclusion of the drivers for the Promise controller card and all other hardware items listed.
When Win7 SP1 beta was tested a similar problem occured and was cured by my turning off all of the PATA devices in the BIOS so that the initial reboot, required after Win7 SP1 beta was installed, would not 'see' the two DVD drives before the harddrives connected to the SATA controller and, therefore, not start Win7 with SP1 beta. The BIOS was set to point to the Promise controller card as the initial boot device but, for some reason, this was not recognized as the mandated boot order by the SP1 beta reboot process.
When Win7 SP1 RC1 was released I assumed a similar problem might occur so I, again, copied the complete SP1 RC1 CD to a harddrive partition, turned off the PATA devices in the BIOS to ensure only the Promise controller card and the connected SATA harddrives were available as the boot devices and proceeded to install Win7 SP1 RC1. The initial install routine completed and a reboot was required and that's when everything 'hung' for the hours I mentioned above.
So, given that Win7 installed, then Win7 SP1 beta, I was not expecting RC1 to fail. I am awaiting any and all suggestions.
-
09 Aralık 2010 Perşembe 04:27
Hi ChiefZeke,
Unfortunately the logs don't tell me as much as I'd hoped. There is indeed a hang. It happens during the servicing of drivers but I cannot find any information on the nature of the problem. I found this error in the System event log which appears on every startup:
"Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware."
Are you using some special or uncommon hardware? It maybe your controller card. The only thing I can advise is check on the manufacturer websites for updated drivers. Also check for updates for your BIOS.
Are you still experiencing the hang? Have you been able to successfully install the SP?
Mark [MSFT]
The hardware in the system in question is:
Foxconn 661MXPlus motherboard
Promise SATA150TX2Plus/TX4 controller card
Intel Celeron 2.5Ghz cpu
Kingston KVR400X64C3AK2/2G memory
Western Digital 320Gb SATA drives (two each)
Creative PC-DVD Encore Dxr3 Decoder Card
Creative 5x and 6x DVD drives
ATI Radeon X1650 512Mb of memory, AGP video card
Creative SoundBlaster Audigy2 Platinum audio cardAs far as I know the motherboard and the Promise controller card are up-to-date as far as firmware is concerned. There are no SATA ports on the motherboard; the hard drives are connected to the Promise controller card.
The initial install of Win7 Pro 32-bit went fine with the inclusion of the drivers for the Promise controller card and all other hardware items listed.
When Win7 SP1 beta was tested a similar problem occured and was cured by my turning off all of the PATA devices in the BIOS so that the initial reboot, required after Win7 SP1 beta was installed, would not 'see' the two DVD drives before the harddrives connected to the SATA controller and, therefore, not start Win7 with SP1 beta. The BIOS was set to point to the Promise controller card as the initial boot device but, for some reason, this was not recognized as the mandated boot order by the SP1 beta reboot process.
When Win7 SP1 RC1 was released I assumed a similar problem might occur so I, again, copied the complete SP1 RC1 CD to a harddrive partition, turned off the PATA devices in the BIOS to ensure only the Promise controller card and the connected SATA harddrives were available as the boot devices and proceeded to install Win7 SP1 RC1. The initial install routine completed and a reboot was required and that's when everything 'hung' for the hours I mentioned above.
So, given that Win7 installed, then Win7 SP1 beta, I was not expecting RC1 to fail. I am awaiting any and all suggestions.
-
09 Aralık 2010 Perşembe 17:54add the Environment variable and run Sp1 installer again. Now give Mark the new logs.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
12 Aralık 2010 Pazar 05:10
add the Environment variable and run Sp1 installer again. Now give Mark the new logs.
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
11 DecEdit environmental variables to add: WINDOWS_TRACING_FACILITY_POQ_FLAGS with a value of 10000
Started SP1 RC1; updated proceeded ok until reboot - then, as earlier, reboot stayed at 9% for an hour. Hard reboot and opted to perform recovery option as shown above. Boot into Win7 Pro successful with same error message is earlier.
Copied the files mentioned earlier and uploaded to same location as earlier.
-
12 Aralık 2010 Pazar 05:10
Hi ChiefZeke,
Unfortunately the logs don't tell me as much as I'd hoped. There is indeed a hang. It happens during the servicing of drivers but I cannot find any information on the nature of the problem. I found this error in the System event log which appears on every startup:
"Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware."
Are you using some special or uncommon hardware? It maybe your controller card. The only thing I can advise is check on the manufacturer websites for updated drivers. Also check for updates for your BIOS.
Are you still experiencing the hang? Have you been able to successfully install the SP?
Mark [MSFT]
11 DecEdit environmental variables to add: WINDOWS_TRACING_FACILITY_POQ_FLAGS with a value of 10000
Started SP1 RC1; updated proceeded ok until reboot - then, as earlier, reboot stayed at 9% for an hour. Hard reboot and opted to perform recovery option as shown above. Boot into Win7 Pro successful with same error message is earlier.
Copied the files mentioned earlier and uploaded to same location as earlier.
-
13 Aralık 2010 Pazartesi 21:38
Hi ChiefZeke,
I received your new logs. I need to consult with some other colleagues to find out what the best course of action is.
Thanks,
Mark [MSFT]
-
14 Aralık 2010 Salı 00:46
Hi ChiefZeke,
Based on what we could get out of your logs, can you try the following:
- Remove your sound card
- Disable all sound devices in Device Manager
and try installing the SP again.
Mark [MSFT]
-
14 Aralık 2010 Salı 03:13Why would sound driver stop installation - where in the log did you find this?
-
14 Aralık 2010 Salı 03:22
Based on the order the drivers were being installed, it got stuck installing an audio driver. Because of an overall lack of available logging (probably due to the hang itself), this is our best guess on how to unblock installation.
Mark [MSFT]
-
15 Aralık 2010 Çarşamba 23:18
Hi ChiefZeke,
Based on what we could get out of your logs, can you try the following:
- Remove your sound card
- Disable all sound devices in Device Manager
and try installing the SP again.
Mark [MSFT]
Sound card, really? I find it hard to believe there is a big difference between the sound card drivers provided with SP1 beta versus SP1 RC1. I would think SP1 was designed to use the sound card drivers already installed for that device and did not actually have its own set of drivers.If SP1 RC1 installs successfully with the sound card removed can I then assume a re-installation of the sound card will prevent Win7 w/SP1 from booting?
-
16 Aralık 2010 Perşembe 18:38
It is possible that Windows is using the sound driver that comes "inbox" with Windows, unless you have the manufacturer or 3rd-party drivers installed. It may be an incompatibility with your particular sound card and its driver at the time of SP1 installation. We have no reason to believe re-installing the sound card would prevent Win7 from booting.
Can you let us know if this prevents the hang? Also, let us know what sound card you have and what driver version it is using (from Device Manager).
Thanks,
Mark [MSFT]
-
17 Aralık 2010 Cuma 23:11
It is possible that Windows is using the sound driver that comes "inbox" with Windows, unless you have the manufacturer or 3rd-party drivers installed. It may be an incompatibility with your particular sound card and its driver at the time of SP1 installation. We have no reason to believe re-installing the sound card would prevent Win7 from booting.
Can you let us know if this prevents the hang? Also, let us know what sound card you have and what driver version it is using (from Device Manager).
Thanks,
Mark [MSFT]
Creative SoundBlaster Audigy2 Platinum audio card
Microsoft Digital Sound System 80The Creative sound drivers originally installed were those that were on the CD that came with the sound card.
Win7 > Device Manager > Sound, video and game controllers > Creative SB Audigy 2 (WDM) > Properties > Driver > Creative, 18 Mar 10, 6.0.1.1377, Creative Labs Inc - this, to me , indicates the drivers have been updated as the ones on the Creative CD were dated years ago.
Different problem: Am having difficulties posting responses to this forum. Last night post from Win7 64-bit did not make it. Earlier today fro XP Pro a NO-GO, this from XP Pro x64 and different Live ID.
-
18 Aralık 2010 Cumartesi 13:29
Different problem: Am having difficulties posting responses to this forum. Last night post from Win7 64-bit did not make it. Earlier today fro XP Pro a NO-GO, this from XP Pro x64 and different Live ID.
ask this here:
http://social.microsoft.com/Forums/en-US/reportabug/threads/
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
19 Aralık 2010 Pazar 06:17
It is possible that Windows is using the sound driver that comes "inbox" with Windows, unless you have the manufacturer or 3rd-party drivers installed. It may be an incompatibility with your particular sound card and its driver at the time of SP1 installation. We have no reason to believe re-installing the sound card would prevent Win7 from booting.
Can you let us know if this prevents the hang? Also, let us know what sound card you have and what driver version it is using (from Device Manager).
Thanks,
Mark [MSFT]
18 DecRemoved Creative SoundBlaster Audigy2 Platinum audio card and booted into Win7 (did notice sound was still working when Win7 started, determined it was because the Microsoft Digital Sound System 80 was still USB connected and powered); started installation of SP1 RC1 - 90 minutes to get to 'Restart" - configuring service pack at 9% - after 30 minutes at 9% I pulled the USB connector for the Digital Sound System 80 to see if that would make a difference - waited 15 minutes - still at 9%. Disconnected USB Web Cam (Creative Video Blaster WebCam Go - which had no Win7 drivers) - progress; got to 30% and rebooted. Selected Win7 from menu - surprise - rebooted - selected Win7 then start normally - moving colored icons then blank screen, tried again - reboot. Why??? Killed Power - will reinstall sound card and USB Digital Sound 80.
Later same night.
Started system - boot into XP Pro fine. Reboot - Win7 either repair or start normally - normally did not work, twice, just reboots. Repair selected - could not repair. Time to revert - again. Failure: blank screen, keyboard inop, mouse light is on. Hard reboot. Tried revert process again - says successful. Restart. Win7 selected, color icon swirl, blank screen.
Looks like I cannot return to Win7 prior to SP1 RC1 attempted install. Will boot to XP and copy files listed previously and post to same location. Looks like I'll have to reformat the drive Win7 is on and reinstall - again. So far, SP1 RC1 is a bust.
Hope all this is helping someone somewhere.
-
19 Aralık 2010 Pazar 06:26
Different problem: Am having difficulties posting responses to this forum. Last night post from Win7 64-bit did not make it. Earlier today fro XP Pro a NO-GO, this from XP Pro x64 and different Live ID.
ask this here:
http://social.microsoft.com/Forums/en-US/reportabug/threads/
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
I asked at that forum 4-6 weeks ago, or more, and never received an answer, a question, or a suggestion on a possible fix. I gave up on seeking help from that location - that's why I posted the comment here. -
19 Aralık 2010 Pazar 08:39I definately recall diffeculty installing RC after removal of beta. I believe the problem is not installing RC but removing beta corrupted my system. I reinstalled 7 and installed RC with no diffeculty. I would focus on reinstalling 7 and then test the removall of RC and reinstall of RC. If all goes well with this then whatever was causing said diffeculty was eliminated with RC.
-
19 Aralık 2010 Pazar 13:58
I definately recall diffeculty installing RC after removal of beta. I believe the problem is not installing RC but removing beta corrupted my system. I reinstalled 7 and installed RC with no diffeculty. I would focus on reinstalling 7 and then test the removall of RC and reinstall of RC.
I had the Sp1 Beta on a Server 2008 R2, removed it and installed the RC and it works all fine. You can't generalize such issues. Start your own topic and test it again. After removing Sp1 beta, run sfc and look at the CBS.log is files where repaired. I had an issue with the IE9 corrupting files. A MSFT employee confirms that and told it it fixed in IE9 (RTM).
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
19 Aralık 2010 Pazar 19:49
Interesting response Mr. Ziegler. I believe I was on topic and furthermore was merely confirming DesertJerry's concern that it is quite possible there may be an issue with removing SP1 beta since I had a similar experiance with RC install after removal of beta. Using SFC as you suggested will confirm file corruption or missing files but wil not serve as a viable solution for any later releases of SP1. Furthermore yes, you are correct to say there was a snag removing IE9, specifically the location of temporary internety files lost and transfererd to the profile's working temp folder however reasigning from internet properties solved it. Please understand that this is prerelease software not yet perfected, furthermore I was in no way generalizing but sharing my own experiance to shed light on the subject and in doing so, validate DesertJerry's primary concern that indeed there may be something that should not be overlooked here. As was done for IE9 that you mentioned we can resolve any issues with removing future releases of SP1 be reporting any discrepancies here. Good day.I definately recall diffeculty installing RC after removal of beta. I believe the problem is not installing RC but removing beta corrupted my system. I reinstalled 7 and installed RC with no diffeculty. I would focus on reinstalling 7 and then test the removall of RC and reinstall of RC.
I had the Sp1 Beta on a Server 2008 R2, removed it and installed the RC and it works all fine. You can't generalize such issues. Start your own topic and test it again. After removing Sp1 beta, run sfc and look at the CBS.log is files where repaired. I had an issue with the IE9 corrupting files. A MSFT employee confirms that and told it it fixed in IE9 (RTM).
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
21 Aralık 2010 Salı 05:48
I definately recall diffeculty installing RC after removal of beta. I believe the problem is not installing RC but removing beta corrupted my system. I reinstalled 7 and installed RC with no diffeculty. I would focus on reinstalling 7 and then test the removall of RC and reinstall of RC. If all goes well with this then whatever was causing said diffeculty was eliminated with RC.
Somewhere above in one of my earlier postings I did mention that the removal of SP1 beta was unsuccessful and I had to reformat the drive/partition and reinstall Win7 32-bit Pro as a new install on my #2 system. Since then my postings have been about issues with the installation of SP1 RC1 on this same system.Since then, my comments have been about NOT successfully installing SP1 RC1 on my #2 system. Your comments about testing the removal of RC make sense - it is not installing.
- Yanıt Olarak Öneren hohoemiko 21 Aralık 2010 Salı 09:46
-
21 Aralık 2010 Salı 08:01
If it is of any help, I tried to install RC from an extracted folder. I extracted it with /x or /xp command. The install was unsuccessful at an early stage.
-
21 Aralık 2010 Salı 22:52
It is possible that Windows is using the sound driver that comes "inbox" with Windows, unless you have the manufacturer or 3rd-party drivers installed. It may be an incompatibility with your particular sound card and its driver at the time of SP1 installation. We have no reason to believe re-installing the sound card would prevent Win7 from booting.
Can you let us know if this prevents the hang? Also, let us know what sound card you have and what driver version it is using (from Device Manager).
Thanks,
Mark [MSFT]
Mark,Updated info posted and log files in same location as previously on 18 Dec - it appears you are not being notified, again.
-
21 Aralık 2010 Salı 22:58
Hi,
From one of your previous replies, it looks like removing Creative Video Blaster WebCam Go (which you said had no Win7 drivers, it's a very old device!) allowed the SP1 installation to get past the stuck at 9% point. Can you confirm if this is correct? If so, can you describe the nature of your current problem (if any)?
Mark [MSFT]
-
22 Aralık 2010 Çarşamba 06:07
Hi,
From one of your previous replies, it looks like removing Creative Video Blaster WebCam Go (which you said had no Win7 drivers, it's a very old device!) allowed the SP1 installation to get past the stuck at 9% point. Can you confirm if this is correct? If so, can you describe the nature of your current problem (if any)?
Mark [MSFT]
Mark,
Please go back and read the posting listed as: Sunday, December 19, 2010 6:17 AM - it has all of the steps I was able to accomplish and the results - actually got to 30% this time. As I mentioned - requested files uploaded to same locationas used previously. I have since had to reformat the Win7 partition on my $2 system as I was no longer able to access it. Next step is to reinstall Win7, again, and wait fro suggestions.
-
31 Aralık 2010 Cuma 21:28
31 Dec
Drive re-formatted 19 Dec. Win7 install attempt from DVD failed. First reboot got BSOD - could not read. Try again in a couple of days.
Drive re-formatted 20 Dec. Win7 attempt from DVD failed again. First reboot got BSOD - could not read. This is ridiculous. Reformat again.
30 Dec - Copied Win7 DVD to hard drive. Rebooted, went to BIOS to turn off all PATA devices. Found the IDE channels were corrupted; rather than showing AUTO - showed unreadable symbols/letters/numbers/etc. Probably caused by Win7 install routine 'reading' BIOS for information during reboot and corrupting same.
Booted into XP Pro to verify all PATA devices not listed in Device Manager or in Explorer. Started Win7 setup from hard drive. Installation was successful - about 60 minutes. Checked Desktop - looked OK; made minor changes to date/time/colors/etc. Started installation of SP1 RC1 - successful - took about 75 minutes. Then ran Microsoft Update - three Windows updates installed and three driver updates installed. Everything appears to be ok.
Copied the same four files as previously. Ready to upload them to same location as previously so you can compare the files from the unsuccessful attempts to the now successfull attempt and, maybe, determine the cause - though I am pretty sure it is caused by the Win7 SP1 RC1 install routine not reading the BIOS correctly and; therfore, not seeing the SATA addin card as the location for the hard drives. YOUR problem - not mine.
Please advise on upload as I'm not sure you got the previous files.
- Yanıt Olarak Öneren Dog4591 01 Ocak 2011 Cumartesi 03:37
-
20 Şubat 2011 Pazar 17:56
I instaled win7 sp1 in safe mode, and it went smoothly. As I had the same problem configuration being stuck at 9% after installation. I do hope this works for you after all you have been through. some time the simplest soulution is the best. took me two days to finally try safe mode
Good luck
.png)
