Windows 10: Windows 7 x86 upgrade hangs on FIRST BOOT with spinning icon

I have an older Windows 7 Professional x86 install (on a multiboot) that I am trying to upgrade to Windows 10. Hardware is an AAEON thin mini-ITX with i3 3225, 4000 HD graphics and 500gb SSD.

The installation halts on the first boot, after the files have been copied, with the blue screen and spinning icon.

The error log is not of much use, but here are the last few lines.

MOUPG MoSetupPlatform: SetupPlatform::SetSqmDatapoint(DWORD) returned: [0x80004005]
MOUPG MoSetupPlatform: SetupPlatform::SetSqmEndTime returned: [0x80004005]
CDiagnosticsHelper::SetDeferredSQMStartTime: Attempting to set a deferred SQM datapoint start time in an invalid SQM session[gle=0x000000b7]
CDiagnosticsHelper::SetDeferredSQMEndTime: Attempting to set a deferred SQM datapoint end time in an invalid SQM session

This is definitely a software issue, because one of the partitions has been successfully upgraded. I could take the easy path with a clean install, but I am intensely curious as to why this won't upgrade, and was hoping someone could suggest what I might look for.

Suggestions?

:)

 

Windows 10 hangs on spinning dots

same issue - spinning dots, blue screen takes hours to boot and get to the login screen. just hangs at the spinning dots just prior to the login screen. I tried EVERYTHING and eventually had to load everything from scratch new build.

safe mode worked fine - clean boot with nothing in startup didn't work. Something about passport error messages in event log though not sure if that is related.

PC was running for 5 months no problem prior. Was an upgrade from windows 7.

What could cause this?

 

Windows 10 Upgrade on Old Hp Touchsmart

I wasn't able to upgrade my HP Touchsmart 600 (1040ch) to Windows 10. It just hangs on first boot and reverts back to windows 7...Trying for days now, haven't found a solution yet.

 

Hello Katanga Welcome to the Ten Forums!

You could actually see a nice fresh install of 10 go simply by following a rather unique option of seeing the 7 activation status passed along to the fresh copy of 10. Clean Install Windows 10 Directly without having to Upgrade First - Windows 10 Forums

One thing learned over the years here was that for every newer version a clean install was always the preferred route to take right from the start. But MS pulled a fast one with 10 trying to force the upgrade type install that too often can turn out buggy!

For not being able to see 10 go at all however that brings us to what I saw here intentionally walking into 10 blindly last summer having first seen a clone of the 7 Ultimate drive over to the second OS drive now the default 10 drive since and later when 10 simply wouldn't go on a fresh install of 7 still wouldn't take until the two storage drives were unplugged! That I found out when then turning to the other clean install guide and reading the notations! Windows 10 - Clean Install - Windows 10 Forums

What happened then and likely is what you are now running into is the "10 Installer Gets Confused" problem where the temp install folders created are place in one place while the boot files end up elsewhere! Those would be on drives without any OS at all! I found the "$Windows~BT" and "~WS" folders on the first of the pair of storage drives while the boot loader ended up on the second!

If you have any non OS drives plugged including flash drives, an external hard drive, or drive in a usb enclosure those would need to be unplugged. For any internal drive simply pulling out the 7pin data cable after first shutting everything down as a precaution should then be able to see 10 go on without fuss. But even for an upgrade install review the guide for that as well as the others! Windows 10 - Upgrade Installation - Windows 10 Forums

 

Thanks, but checking the logs, this would not seem to be the case, as the folders are where they should have been.

The paucity of information in the logs is frustrating, and I can't find any clues as to what is blocking completion of the upgrade.

There are no other devices attached, and I encountered this same issue during another upgrade attempt, also on an aged XP install that had been upgraded to Vista and then 7. In that case, there was only one partition and one storage device.

 

Try running the Windows 8.1 upgrade assistant and let us know the results:
Upgrading to Windows 8.1 from Windows 7 - Windows Help

Windows update may be failing due to some Windows 7 update that is trying to reinstall. Try to reset windows update:

Windows Update - Reset in Windows 10 - Windows 10 Forums

Reset is identical in windows 7, I think

Don't elect to update during setup, and disconnect from any network/internet during setup -you can do the updates after installation

 

An isolated type upgrade install is what Fafhrd is referring to there to prevent any inferences from updates getting in the way of the OS upgrade itself. As for the WU reset method for 7 it would best to look over the guide for that over at SF. The steps for 7 will be outlined there as well as seeing Option One a download for repair. Windows Update - Reset - Windows 7 Help Forums

 

I am trying the Windows Update reset suggested.

The Windows 8.1 Upgrade Advisor complained about Visio 2000 (which lingered on in Add/Remove Programs after being uninstalled), but little else.

I will confess that this particular Seven install began life as Windows 95 back in 1996 or so, and was subsequently upgraded to Windows 98, Windows 2000, XP, Vista and finally Seven. Might there be some holdover from one of these outdated OSs that is blocking the upgrade?

 

I read that BCD.corruption may be involved in this sort of problem and that rebuilding the BCD may help. Open an admin command prompt and run bootrec /rebuildBCD before retrying setup:
http://answers.microsoft.com/en-us/w...3aee7fb?page=2

The i3 3225 is not an old enough processor, (launched in Q3 2012), surely, to have had that upgrade history?

It sounds like the old joke about the guy who had been using the same broom for 40 years with six replacement heads and 4 replacement handles over that time!

I seriously doubt that the upgrade history is very relevant - the NTFS from Windows 2000 et seq. will have wiped all traces of the FAT32 for Windows 9X, and The Windows 7 BCD will have replaced the legacy NT bootmanager.

 

I'm running with the belief that the minimum system requirements are not being met for 10. You are now looking at a 20yr. system trying to upgrade into 10 when having started with how large of a drive? It takes a good 88gb for 10 Pro and likely over 75gb for the Home edition with the addition of the Windows.old and other folders during an upgrade. 7 Ultimate will fit on a 60gb primary in contrast still having been a single not dual platform OS now being seen with 10. Lack of drive space anyone?

Back in 1996 you wouldn't have even been seeing a 13gb hard drive. Here I upgraded out of an old IBM 386 with a 200mb into an AST 486 where I swapped out the 500mb for a 1.2gb WD at the time first seeing 95 and later 98SE. Finally when drive capacities started climbing XP was able to first see 120gb drives when dual booted with 98 and a pair of 250s while 98SE couldn't realize the full capacities of those drives.

 

I think Katanga has described the software upgrade history, but the hardware has been upgraded too, over time, NightHawk. It was stated that the 8.1 upgrade assistant only complained about Visio2000, and that there was a 500GB SSD installed.

The Mini-Thin ITX board can only be 3 years old, and the processor about the same, and the SSD has replaced a chain of older hard disks. It's amazing what can be done on custom hardware with full retail products.

I run Windows 10 usefully, (but not necessarily as main systems) on drive volumes as small as 35GB, with 5 GB of free space - you need nowhere near 88GB unless you have a large hiberfil.sys and oversized pagefiles due to lots of RAM, loads of programs and lots of pictures videos etc., and don't do your maintenance often enough.

 

That was on VM not a physical install I ran into the default 60gb vhd simply not being enough. And you would normally expect there would have been hardware as well as OS upgrades over that amount of time as well. The second build here with only 8gb of memory and the original 500gb drive I saved out of an old Vista case last having seen the 7 beta, RC builds saw 7 Pro at first upgraded to 10 and since wiped clean and now running strictly Insider builds there.

At first I tried creating a second primary for the initial clean install to follow as a dual boot to verify 10 would activate last summer and had to wipe the drive entirely for the final install which has seen numerous newer builds upgrade over the 10565 I later saw go on fresh when you could still grab that from the Tech bench site. The drive is still in good working order to allow all that and one item that could be checked there.

The 500gb here was new for the Vista build back in 2007 when bought in a pair with the other now in another 7 Pro case. I told the friend I passed that along to that he could try out 10 on a second drive that could be added in to get a look at the new version but so far he has simply been occupied with an 8.1 laptop where he wants to see that drive swapped out.

The other thing I noticed was Katanga's reference to the other partition.

That would suggest trying to set up a dual 10 dual boot with two upgrades not one being seen.

 

I noticed that reference to another partition that had successfully upgraded too.

I try out VMs occasionally, but invariably give up on them when I need more real space on the disk - they do seem to eat up disk space.

 

Agreed! I tend to keep only a few per machine to avoid that problem! Even with 1tb OS drives space tends to get chewed up real fast when you are not watching it!

The two primary one already upgraded should already be what was needed for simply giving 10 a look. Here on both desktops I run with two separate OS drives one having been a former storage drive on the main now in used for 7 Pro and a backup partition the second case used primarily for testing only. That along with the matching other WD Black edition 1tb drive stuffed into an enclosure were replaced by a pair of 2tb Server class WD "Heavy Duty" drives.

 

There are two of these old installs I have tried to upgrade. Both were originally Windows 95 OSR2, upgraded to 98, 2000, XP, Vista and finally 7. Over the years, they were used on many different hardware combinations, but now one has been migrated to a B85 1150 with i3 4170 CPU and 750gb hard drive, while the other is on a Q77 1155 with i3 3225 CPU and 500gb hard drive with several partitions.

I had no trouble upgrading installs that were originally XP to 32-bit 10. Thus, I am thinking that there may be some residual from Windows 2000 or earlier that is keeping the FIRST BOOT from happening.

[QUOTEBack in 1996 you wouldn't have even been seeing a 13gb hard drive. Here I upgraded out of an old IBM 386 with a 200mb into an AST 486 where I swapped out the 500mb for a 1.2gb WD at the time first seeing 95 and later 98SE. Finally when drive capacities started climbing XP was able to first see 120gb drives when dual booted with 98 and a pair of 250s while 98SE couldn't realize the full capacities of those drives.[/QUOTE]I upgraded a circa-2004 XP install to 32-bit Windows 10, with no trouble. It had originally been installed on a 120gb PATA drive, for a circa-2001 ALI Alladin AMD board. It had been migrated many times over the years, first to AMD and later to Intel architectures, before its current home of a B85 1150.

Yup. One old XP install I created back in 2004 has been migrated several times, and with Intel dropping support for XP on its latest chipsets, I finally broke down and upgraded it to 32-bit 10, via Vista and 7.