If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
8.1 update stuck
My Store - based upgrade to 8.1 starts "checking compatibility" and
sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? |
Ads |
#2
|
|||
|
|||
8.1 update stuck
Hi, Peter.
Please define "indefinitely" and "Eventually", in your case. Did you wait 20 minutes? 2 hours? How long? Some of these update/upgrade processes do take MUCH longer than most of us expect. But these newsgroups - and my own experience - include several cases that eventually did succeed after several hours or even overnight. But you've given us no clue as to how long you actually let the 8.1 upgrade run. RC -- R. C. White, CPA San Marcos, TX Microsoft Windows MVP (2002-2010) Windows Live Mail 2012 (Build 16.4.3508.0205) in Win8.1 Pro "Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? |
#3
|
|||
|
|||
8.1 update stuck
On 25/11/2013 13:49, R. C. White wrote:
Hi, Peter. Please define "indefinitely" and "Eventually", in your case. Did you wait 20 minutes? 2 hours? How long? Some of these update/upgrade processes do take MUCH longer than most of us expect. But these newsgroups - and my own experience - include several cases that eventually did succeed after several hours or even overnight. But you've given us no clue as to how long you actually let the 8.1 upgrade run. RC -- R. C. White, CPA San Marcos, TX Microsoft Windows MVP (2002-2010) Windows Live Mail 2012 (Build 16.4.3508.0205) in Win8.1 Pro "Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? I left it about three hours. It went up to 58% on the compatibility check within the first twenty minutes or so, and then stuck for the remainder of the three hours. I understand the upgrade can take a long time - but surely not stuck at 58%... |
#4
|
|||
|
|||
8.1 update stuck
On Mon, 25 Nov 2013 14:08:16 +0000, Peter wrote:
On 25/11/2013 13:49, R. C. White wrote: Hi, Peter. Please define "indefinitely" and "Eventually", in your case. Did you wait 20 minutes? 2 hours? How long? Some of these update/upgrade processes do take MUCH longer than most of us expect. But these newsgroups - and my own experience - include several cases that eventually did succeed after several hours or even overnight. But you've given us no clue as to how long you actually let the 8.1 upgrade run. RC -- R. C. White, CPA San Marcos, TX Microsoft Windows MVP (2002-2010) Windows Live Mail 2012 (Build 16.4.3508.0205) in Win8.1 Pro "Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? I left it about three hours. It went up to 58% on the compatibility check within the first twenty minutes or so, and then stuck for the remainder of the three hours. I understand the upgrade can take a long time - but surely not stuck at 58%... I fully understand that 58% is unacceptable. What percentage would have been OK with you? |
#5
|
|||
|
|||
8.1 update stuck
On 25/11/2013 14:29, Char Jackson wrote:
On Mon, 25 Nov 2013 14:08:16 +0000, Peter wrote: On 25/11/2013 13:49, R. C. White wrote: Hi, Peter. Please define "indefinitely" and "Eventually", in your case. Did you wait 20 minutes? 2 hours? How long? Some of these update/upgrade processes do take MUCH longer than most of us expect. But these newsgroups - and my own experience - include several cases that eventually did succeed after several hours or even overnight. But you've given us no clue as to how long you actually let the 8.1 upgrade run. RC -- R. C. White, CPA San Marcos, TX Microsoft Windows MVP (2002-2010) Windows Live Mail 2012 (Build 16.4.3508.0205) in Win8.1 Pro "Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? I left it about three hours. It went up to 58% on the compatibility check within the first twenty minutes or so, and then stuck for the remainder of the three hours. I understand the upgrade can take a long time - but surely not stuck at 58%... I fully understand that 58% is unacceptable. What percentage would have been OK with you? Gosh that's witty. |
#6
|
|||
|
|||
8.1 update stuck
Peter wrote:
On 25/11/2013 14:29, Char Jackson wrote: On Mon, 25 Nov 2013 14:08:16 +0000, Peter wrote: On 25/11/2013 13:49, R. C. White wrote: Hi, Peter. Please define "indefinitely" and "Eventually", in your case. Did you wait 20 minutes? 2 hours? How long? Some of these update/upgrade processes do take MUCH longer than most of us expect. But these newsgroups - and my own experience - include several cases that eventually did succeed after several hours or even overnight. But you've given us no clue as to how long you actually let the 8.1 upgrade run. RC -- R. C. White, CPA San Marcos, TX Microsoft Windows MVP (2002-2010) Windows Live Mail 2012 (Build 16.4.3508.0205) in Win8.1 Pro "Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? I left it about three hours. It went up to 58% on the compatibility check within the first twenty minutes or so, and then stuck for the remainder of the three hours. I understand the upgrade can take a long time - but surely not stuck at 58%... I fully understand that 58% is unacceptable. What percentage would have been OK with you? Gosh that's witty. I was expecting some revelations in here, because usually these tutorials handle all sorts of exception cases. http://www.eightforums.com/tutorials...1-preview.html So no help there. ******* Before doing the update, you should have a backup of Windows 8.0 in hand. That covers off situations where you need to hit the power button, because the update didn't work out the way you planned. You can use System Image for that, a copy of Macrium Reflect Free, and so on. ******* Before the other OSes did updates, you had the option of doing CheckSUR. Which stands for System Update Readiness. http://support.microsoft.com/kb/947821 Notice that the information there, shows no separate CheckSUR download for Windows 8. As far as I know, DISM is part of WAIK deployment kit. I don't know if it's present by default in a user copy of Windows 8. But apparently this is the equivalent of doing CheckSUR. DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth I can find a reference to the topic here. Since Shawn doesn't mention downloading WAIK, that means there must be a DISM.exe in Windows already. Which would be good news. http://www.eightforums.com/tutorials...ndows-8-a.html ******* Any time an update runs, it leaves multiple log files. You'd want to search for .log on C:, look for things with recent date stamps, and look for perhaps things with cbs in the name. CBS stands for Component Based Store, and the store contains more files than your OS needs, and the precise files needed by your version of OS, are then hard-linked into the actual working system folders. C:\Windows\Logs\CBS\CBS.log What usually happens with these log files, is when an update fails, a whole bunch of lines about "backing out..." fill the file. Meaning the root cause event is buried half way up the file. And requires the user to get out a magnifying glass, to see what is actually broken. In other words, the error message is not contained in the very last line of the file. That would be too convenient. So if the update stops in an overnight run, you'd have a look for available logs. And then if you absolutely had no other choice, try the DISM thing. Or even, revert to a backup, if it looks like something got damaged (system no longer boots, DVD won't repair it, etc). ******* I bought Windows8 Upgrade for $39.95. There is an electronic download of 3GB or so in size for that. There is a trick you can use, where you go back to the download site, with your Windows key in hand, and you can trick the downloader into giving you a copy of Windows 8.1 3GB DVD image instead. Now I have both here. When it comes time to install the update, I won't be doing it via Windows Update, and will be using the DVD instead. The image I have, uses install.esd, with only one version of OS inside the DVD, versus the MSDN image which contains multiple versions of OS. The MSDN ISO9660 should be several hundred megabytes bigger than my "inferior" image. But my DVD will suffice to update my installation, as it is exactly the right version, with no extra files. I only really need to do that update, within the next year or so. There is no rush at the moment. I keep automatic updates turned off, so it won't "sneak in" while I'm sleeping or something :-) The reason for waiting, is to learn all the installation tricks before doing it. Downloading that image is one of the tricks. The other trick, is avoiding the creation of a Microsoft Account. http://windowssecrets.com/top-story/...an-ms-account/ So I'm just about ready to do the update here, as time allows. Good luck, Paul |
#7
|
|||
|
|||
8.1 update stuck
On 11/25/2013 9:08 AM, Peter wrote:
went up to 58% on the compatibility check within the first twenty minutes or so, and then stuck for the remainder of the three hours. I understand the upgrade can take a long time - but surely not stuck at Have you disabled you virus checking and your firewall? I had to make several tries to get 8.1 to update, and then only after I disabled the Firewall and virus checker. |
#8
|
|||
|
|||
8.1 update stuck
Paul wrote:
I bought Windows8 Upgrade for $39.95. There is an electronic download of 3GB or so in size for that. There is a trick you can use, where you go back to the download site, with your Windows key in hand, and you can trick the downloader into giving you a copy of Windows 8.1 3GB DVD image instead. Now I have both here. When it comes time to install the update, I won't be doing it via Windows Update, and will be using the DVD instead. The image I have, uses install.esd, with only one version of OS inside the DVD, versus the MSDN image which contains multiple versions of OS. The MSDN ISO9660 should be several hundred megabytes bigger than my "inferior" image. But my DVD will suffice to update my installation, as it is exactly the right version, with no extra files. I only really need to do that update, within the next year or so. There is no rush at the moment. I keep automatic updates turned off, so it won't "sneak in" while I'm sleeping or something :-) The reason for waiting, is to learn all the installation tricks before doing it. Downloading that image is one of the tricks. The other trick, is avoiding the creation of a Microsoft Account. http://windowssecrets.com/top-story/...an-ms-account/ So I'm just about ready to do the update here, as time allows. Good luck, Paul A good plan. The MSDN 8.1 iso contains Core and Pro or optionally on a separate iso - Enterprise. It won't sneak in via AU - by design the Store or retail are the only deployment routes. The possibility does exist to deploy a notification for 8.1 on 8.0 systems via Windows Updates...but iirc that bit has not been flipped (yet). Imo, if you wish to continue to use Windows 'Future X.x', a MSFT account is inevitable for consumers...the relief (i.e. option) for Local only will be soley in Enterprise domain based. There is no compelling reason for MSFT to continue creation of Local Accounts unless a MSFT is first created and to provide future support for Windows when the o/s and activation are not tied to MSFT account. i.e. Enjoy it while it lasts. -- ...winston msft mvp consumer apps |
#9
|
|||
|
|||
8.1 update stuck
On 25/11/2013 18:13, Paul wrote:
C:\Windows\Logs\CBS\CBS.log Thanks Paul - I have to admit, the CBS file is beyond me. There are no signs of the "backing out" you mention, though there are a few failures due to missing files, none of which seem to have terminated the process. In fact the log ends "CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2013-11-25 16:58:48, Info CBS TiWorker signaled for shutdown, going to exit. 2013-11-25 16:58:48, Info CBS Ending the TiWorker main loop. 2013-11-25 16:58:48, Info CBS Starting TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending the TrustedInstaller main loop. 2013-11-25 16:58:48, Info CBS Starting TrustedInstaller finalization. 2013-11-25 16:58:48, Info CBS Ending TrustedInstaller finalization. Which doesn't seem like a Panic. I guess I'll try shutting off firewall and AVG as suggested elsewhere in this thread and see what happens... |
#10
|
|||
|
|||
8.1 update stuck
On 11/26/2013 3:46 AM, Peter wrote:
On 25/11/2013 18:13, Paul wrote: C:\Windows\Logs\CBS\CBS.log Thanks Paul - I have to admit, the CBS file is beyond me. There are no signs of the "backing out" you mention, though there are a few failures due to missing files, none of which seem to have terminated the process. In fact the log ends "CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2013-11-25 16:58:48, Info CBS TiWorker signaled for shutdown, going to exit. 2013-11-25 16:58:48, Info CBS Ending the TiWorker main loop. 2013-11-25 16:58:48, Info CBS Starting TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending the TrustedInstaller main loop. 2013-11-25 16:58:48, Info CBS Starting TrustedInstaller finalization. 2013-11-25 16:58:48, Info CBS Ending TrustedInstaller finalization. Which doesn't seem like a Panic. I guess I'll try shutting off firewall and AVG as suggested elsewhere in this thread and see what happens... Sounds like a plan to me. I started a couple of my upgrades and went to bed, when I got up (after 8 hours of me not watching the monitors) they were either finished or had reported a problem like a incompatible driver or interface card. Either way, if they had not finished or reported a problem in 8 hours I figured they were never going to finish and reverted them back to another OS version but so far out of 7 upgrades only one actually refused to take the 8.1 transplant. Just lucky I guess or is it cursed since so many of them actually took to the transplant... |
#11
|
|||
|
|||
8.1 update stuck
Peter wrote:
On 25/11/2013 18:13, Paul wrote: C:\Windows\Logs\CBS\CBS.log Thanks Paul - I have to admit, the CBS file is beyond me. There are no signs of the "backing out" you mention, though there are a few failures due to missing files, none of which seem to have terminated the process. In fact the log ends "CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2013-11-25 16:58:48, Info CBS TiWorker signaled for shutdown, going to exit. 2013-11-25 16:58:48, Info CBS Ending the TiWorker main loop. 2013-11-25 16:58:48, Info CBS Starting TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending TiWorker finalization. 2013-11-25 16:58:48, Info CBS Ending the TrustedInstaller main loop. 2013-11-25 16:58:48, Info CBS Starting TrustedInstaller finalization. 2013-11-25 16:58:48, Info CBS Ending TrustedInstaller finalization. Which doesn't seem like a Panic. I guess I'll try shutting off firewall and AVG as suggested elsewhere in this thread and see what happens... One of the generic reasons listed here, is "processor doesn't meet requirements". Windows 8.1 has a few instruction types it requires, which is different than the 8.0 requirement. That requirement rules out a pretty small percentage of computers (but that should have been detected before the installation attempt even starts). http://windows.microsoft.com/en-US/w...-windows-store I can see an example of a cbs.log here, and like you're saying, there isn't evidence of "backing out". But some other installers or Service Packs do that, and then you have to go way back in the log file, until you find the event causing the failure. http://answers.microsoft.com/en-us/w...1-2fe93eff36d6 I like your "disable Firewall and AVG" idea. Sounds like a good place to start. Don't forget to have a backup copy of your Windows hard drive in hand before your next run... Just in case. Back when Windows 7 SP1 update showed up, the installer was pretty good about not damaging anything. But at least one user got "bricked", when the installer thought it had finished, when it had not, and the OS would no longer boot. That's why you do backups, for those "one-in-a-million" failures. Paul |
#12
|
|||
|
|||
8.1 update stuck
R. C. White [asked for details...]:
"Peter" wrote in message o.uk... My Store - based upgrade to 8.1 starts "checking compatibility" and sticks at 58 per cent. No info, no warnings; just sits there indefinitely. Eventually I cancelled the upgrade. Before I try again - anybody else had the problem? I understood you could leave it running in the background while you went on working - yes? Or am I disturbing it by using the PC? You kicked off the apparently stuck routine? Good for you!!! I hate it when the Microsoft denizons tell me an app is free, then it's crippled, runs online, and nags me to pay for an upgrade to a fluffier model! Who came up with that business model anyway? This time make sure if you have a 3rd party software firewall to go ahead and disable it temporarily. Also, make sure you don't have other software running (such as silent updating a-la Windows 8 cuteness) before slap teh "Git 'Er Done" button... Clean your caches with CCleaner. Then navigate back via the Windows Store interface thangy routine - and go again. Be sure to check every now and again in case it throws up one of those interrogative dialogs on its alleged "unassisted" upgrade/update routine[s]. It's a little bumpy, but likely as not, you'll get through it unscathed. -- I NEVER thought this could happen, but my heart just got broken last week : http://www.winamp.com/media-player/en How will I ever be able to listen to Shoutcast Radio again? So many hours; so many songs; so many girlfriends; so many smiles; so many "our songs"; so many good times... I believe I'll be going into mourning now... I understand that it is a "process" - and right now I am realizing an overwhelming sense of "Shock and Disbelief"! |
#13
|
|||
|
|||
8.1 update stuck
On Tue, 26 Nov 2013 01:52:14 -0500, "...winston"
wrote: Imo, if you wish to continue to use Windows 'Future X.x', a MSFT account is inevitable for consumers...the relief (i.e. option) for Local only will be soley in Enterprise domain based. There is no compelling reason for MSFT to continue creation of Local Accounts unless a MSFT is first created and to provide future support for Windows when the o/s and activation are not tied to MSFT account. i.e. Enjoy it while it lasts. I'm glad you added that last line because I read the paragraph above it three times without understanding it. |
#14
|
|||
|
|||
8.1 update stuck
Char Jackson wrote:
On Tue, 26 Nov 2013 01:52:14 -0500, "...winston" wrote: Imo, if you wish to continue to use Windows 'Future X.x', a MSFT account is inevitable for consumers...the relief (i.e. option) for Local only will be soley in Enterprise domain based. There is no compelling reason for MSFT to continue creation of Local Accounts unless a MSFT is first created and to provide future support for Windows when the o/s and activation are not tied to MSFT account. i.e. Enjoy it while it lasts. I'm glad you added that last line because I read the paragraph above it three times without understanding it. Hastily composed and could have been clearer. Microsoft needs to reduce variation, balance and standardize support for all devices capable of using the 8x and later o/s. Common support across all devices trumps user's preference and flexibility. Thus to avoid variation, in the long run the more likely (and obvious) path for future versions of Windows - in a non-Enterprise based (i.e. consumer based) environment that tying the installation, initial setup/upgrade, Windows Updates and Mainstream/Extended Support to a MSFT account, imo, will become mandatory. A Local Account creation (with Standard or Admin privilege) will only be an option after creation of that MSFT account. XP upcoming removal will precipitate an entire restructuring of the Support organization. In 2 more years Win 8.0 drops off the same table. Enjoy it while it lasts and get ready for future - one o/s across multiple devices - all necessitating use of a MSFT account as a condition for use for consumers. -- ...winston msft mvp consumer apps |
#15
|
|||
|
|||
8.1 update stuck
On 2013-11-27, ...winston wrote:
Char Jackson wrote: On Tue, 26 Nov 2013 01:52:14 -0500, "...winston" wrote: Imo, if you wish to continue to use Windows 'Future X.x', a MSFT account is inevitable for consumers...the relief (i.e. option) for Local only will be soley in Enterprise domain based. There is no compelling reason for MSFT to continue creation of Local Accounts unless a MSFT is first created and to provide future support for Windows when the o/s and activation are not tied to MSFT account. i.e. Enjoy it while it lasts. I'm glad you added that last line because I read the paragraph above it three times without understanding it. Hastily composed and could have been clearer. Microsoft needs to reduce variation, balance and standardize support for all devices capable of using the 8x and later o/s. Common support across all devices trumps user's preference and flexibility. Thus to avoid variation, in the long run the more likely (and obvious) path for future versions of Windows - in a non-Enterprise based (i.e. consumer based) environment that tying the installation, initial setup/upgrade, Windows Updates and Mainstream/Extended Support to a MSFT account, imo, will become mandatory. A Local Account creation (with Standard or Admin privilege) will only be an option after creation of that MSFT account. XP upcoming removal will precipitate an entire restructuring of the Support organization. In 2 more years Win 8.0 drops off the same table. Enjoy it while it lasts and get ready for future - one o/s across multiple devices - all necessitating use of a MSFT account as a condition for use for consumers. May also require 24/7 connection on the internet to msft? like that of the xbox originally? Oh well, the "Personal Computer" is getting to become a NON "PC" but just a terminal to a mainframe. Well, I do have a Mac Mini where I use fink but will/can certainly reinstall linux which will do for my needs. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|