My problem lies in both the desktop upgrade AND the clean install by booting from disc. Whatever way I try I cannot get past the windows logo with the spinning dots. I've tried the bios settings with no luck, Ive tried with USB key doesn't work either
I created my bootable DVD/USB from my PC which has windows 7 installed on it. Whichever way i try to install windows 8 I cannot get past the blue/teal windows logo (which IMO doesn't look very modern looks more like a pre-2000 style logo). I have never seen the language selection before (unless I choose to upgrade from desktop which seems to successfully install windows 8 I've tried both upgrade and custom instal from desktop too) and when the computer needs to reboot i get stuck at the logo AGAIN.
I have no idea what is causing this, I've tried to use event manger and can't find a reason why this is happening and I'm not too sure I even know where to look on the event manager. Also when I approach this widows logo through trying to boot from DVD, when the spinning dots come up I have ejected the DVD to see if setup even notices the DVD was ejected... Which by the way it didn't. It just carries on spinning like it wants to do something but doesn't.
Getting fed up xD
Over 1500 views and no solutions !?!? someone please drop a helpful comment?
Hi Jay29. Welcome to EightForums.
The disk you made must not have burned correctly is what comes to mind. I see you burned in 7,but how?
Hi Hippsie, thanks for your response
I have burnt once with imgburn, one with magicISO, and once with windows 7 DVD/USB tool and I have also made a bootable USB out of it.
I am doubtful that there is any corruption or missing data. This is due to the fact I can run the setup through desktop and the upgrade successfully installs without any errors, however upon rebooting I can never get past the windows logo screen!
I had a problem after upgrading win 8 it would get to the logo then reboot. I don't know if its the same situation but i started the install again but kept my internet on and ran a download when prompted. And all works good. Also if the kernal that wind 8 is using may not recignise some firmware unless it can be updated if posible
From reading other forums, mainly Technet (there's a thread on there with a few hundred replies from people like us having this issue since August) it seems they have reached the conclusion that the actual windows boot loader has an issue on microsoft's end. Nothing they have tried has fixed our issue. At this point I am a firm believer that the issue is with the boot loader in the install files and it is up to Microsoft to patch/fix it.
The aforementioned people on Technet had no problems using the Developer Preview, nor the Consumer Preview, but once they tried to install the RTM edition, they were slapped with the issue we all face. It is likely Microsoft made some last minute changes and didn't thoroughly test the changes on a wide range of machines. They spent several months testing the DP and CP versions, if they spent several months testing the RTM version, the release of Windows 8 would of been pushed back into early 2013.
What gives me confidence that its on Microsoft's end and not ours, is the fact that on that thread, a user was able to uncompile the boot loader files in the RTM version, and swap some files out with the CP version, and that these actions resolved the issue (but with some minor bugs). Its definitely not something we would want to try, but I think it goes to show that this issue is originating in the actual windows installation files and not from us. Maybe the new boot loader is searching for something on our machines that we don't have because of our hardware, who knows what it is, but whatever its searching for, it's obvious its not finding and its hanging up. Reminds me of a If/Then conditional statement with no fallback.
I have read that entire forum post my self Aswell. A few people solved the problem by using DISM GUI to integrate drivers into the boot.wim file and others have fixed it by replacing the install.wim and boot.wim and few other boot files with those from the developer preview edition of windows 8.
I myself have tried to integrate drivers and this did not solve my problem. I think I might try just once to replace the boot files with those of developer edition and if that fails I wil wait for Microsoft to fix there mess!!
Ok good. You're up and running. Sorry, but I got busy today.
I noticed a lot of people are having problems with upgrades. I think MS needs to address this. Most of the savvier here recommend fresh install.
I doubt any firmware needed updating unless you mean drivers.
Just for grins, did you use the upgrade advisor?
Hi hippsie that's fine no problem
Yes I have tried with upgrade advisor and I have tried with downloaded unmodified ISO's from other sources. All my firmware and drivers where uptodate prior. It's definitely a problem with boot loader not picking up something or being stuck in an unsolveable loop.
This is what happens when a company rush-releases something.