The dreaded 33% freeze while upgrading Windows 10.

Discussion in 'Windows 10' started by nosirrahx, Mar 24, 2018.

  1. nosirrahx

    nosirrahx MDL Member

    Nov 7, 2017
    200
    116
    10
    Is there an actual known cause of this?

    I maintain 6 PCs at a local school, all of them have identical hardware and software.

    I attempted to upgrade all of them from RS2 to RS3 today with an RS3 image containing the latest CU and SSU.

    4 of the 6 went off without a hitch and 2 of them stopped at 33% after the 2nd reboot.

    I don't actually need to fix these (will just pave over them) but I would love to know what actually causes this.

    Reports seem to indicate that at 33% drivers are being installed and some people have reported that removing a wireless card fixed the lockup but in my case all 6 systems are identical so hardware seems unlikely.
     
  2. coleoptere2007

    coleoptere2007 MDL Guru

    Apr 8, 2008
    2,290
    1,176
    90
    event viewer could help in this case
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    2,698
    419
    90
    install does two with out any drivers.
     
  4. TigTex

    TigTex MDL Member

    Oct 5, 2009
    108
    79
    10
    Most of the cases that I have seen are caused by an HDD that it's failing or are solved with a clean install instead of an upgrade.
    Is the bios version the same on all computers?
     
  5. nosirrahx

    nosirrahx MDL Member

    Nov 7, 2017
    200
    116
    10
    Everything is up to date and the computers are all identical. I know a clean install fixes this, not what I am asking.

    Searching around turns up this problem quite frequently but in most cases there is no resolution, at least nothing consistent.

    More or less I am just trying to see if anyone here knows more about this screamingly random glitch in an upgrade install.

    I left one of the 2 problem systems on 33%, will see if letting it sit long enough sorts this. Reading what others have said seems to imply that this wont work.
     
  6. andrews

    andrews MDL Novice

    Jul 31, 2009
    44
    17
    0
    I think I remember this happening to me when I tried to upgrade using a multi-ISO with both home and pro on it. Try using the ISO that matches exactly and has only what you're trying to upgrade - x86 or x64 and home or pro.
     
  7. nosirrahx

    nosirrahx MDL Member

    Nov 7, 2017
    200
    116
    10

    Interesting, that has literally never been mentioned in the support threads but yes, the image I use for upgrades does indeed have both Home and Pro.

    Using DISM to extract just Home (what these systems all use) is a single enough task.
     
  8. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    3,392
    3,663
    120
    fresh install=no issues trust me :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. andrews

    andrews MDL Novice

    Jul 31, 2009
    44
    17
    0
    This happened enough to me in the past that I only use multi-ISO for clean installs and use specific ISO for updates.