Problems updating to Win 10 10049

Discussion in 'Windows 10' started by stephr1, Apr 1, 2015.

  1. stephr1

    stephr1 MDL Novice

    Jun 2, 2012
    44
    1
    0
    Anyone else having problems upgrading to 10049?

    I am running it on VMWare Workstation (on top of Win 7). I had 10041 doing just fine. When I went to update to 10049, it was a very slow process to do the actual update. However, when it went for a reboot, it got all the way to 23% total/79% setting up and just hung there (went down stairs for an hour or 2 and came back to find it was still at 23/79% :( When I rebooted at that point, it came back and said it was restoring my previous version of windows (just tried again this morning with same results).

    Anyone else experienced this? Am I missing something?

    Thanks and cheers......
     
  2. sof006

    sof006 MDL Novice

    Dec 16, 2010
    4
    0
    0
    The update takes a long time to install.

    It took me a few hours to update from 41 to 49.
     
  3. pisthai

    pisthai Imperfect Human

    Jul 29, 2009
    6,812
    1,996
    210
    My update from 10041 to 10049 was more than 7 hour while the clean install 20min!

    The Update needs a long time and as more Apps etc. are installed as longer it needs.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. stephr1

    stephr1 MDL Novice

    Jun 2, 2012
    44
    1
    0
    #4 stephr1, Apr 1, 2015
    Last edited: Apr 1, 2015
    (OP)
    I appreciate all the feedback. I thought surely I had some kind of problem or was doing something wrong.

    10 hrs??? OMG. Either I'll start the upgrade early in the day or just wait for the "slow" ring .iso version and hope it doesn't take anywhere near as long :(

    Thanks again.....Cheers.....
     
  5. SpeedDream

    SpeedDream MDL Addicted

    Feb 20, 2012
    620
    121
    30
    this is the kind of thing why I always do a fresh install, it's a vm anyhow without anything mine there and avoid many problems
    the build with spartan worked right away this way. No blue screen freeze in login or that kind of problems
     
  6. ibeqa

    ibeqa MDL Member

    Sep 14, 2009
    156
    7
    10
    I did upgrade from 10041 to 10049 and it took around 4 hours.
     
  7. gabrielmorrow

    gabrielmorrow MDL Member

    Jul 5, 2013
    193
    15
    10
    took an hour here to upgrade from 10041 to 10049
     
  8. shawnmos

    shawnmos MDL Member

    Oct 27, 2007
    178
    6
    10
    Took about 1.5-2h on my laptop with Core i5 and SSD drive.
     
  9. joe2013

    joe2013 MDL Novice

    Oct 12, 2013
    8
    0
    0
    Upgrade from Enterprise 10041 to 10049, it took exactly 24 hours "Asus mobo core i7" after windows restart said " windows needs activate", i had to manual put key in, display driver and some components device drivers didn't install, had to run DrivePackSolution ......:worthy:
     
  10. gigel2007

    gigel2007 MDL Novice

    Apr 9, 2010
    7
    1
    0
    10049.png
    running the upgrade under 2012R2 hyper-v.

    I suspect they disabled hdd write cache. Came here after four hours of patience. Discovered that I even had an account already. 9926 -> 10041 performed under the same conditions was much faster.

    taskmanager/resource monitor/process hacker on the HOST shows no more than 4Mb/s writes. plus inside the vm dismhost.exe is wasting cpu resources (most of the time goes 48% and does few kb/s writes)

    I'll go to sleep then tomorrow I'll cleanup old crap on this build[1][2] (not clickable hyperlinks, the forum does not let me) then attempt to upgrade again

    [1] blogs DOT technet DOT com /b/askpfeplat/archive/2014/05/13/how-to-clean-up-the-winsxs-directory-and-free-up-disk-space-on-windows-server-2008-r2-with-new-update.aspx
    [2] howtogeek DOT com/174705/how-to-reduce-the-size-of-your-winsxs-folder-on-windows-7-or-8/
     
  11. mowerman

    mowerman MDL Novice

    Mar 9, 2010
    25
    0
    0
    My upgrade took about 2 hrs. Thought it would never be over. I blamed it on the fact that I have W10 installed on an old drive I had laying around. It's dual booted with my W8.1 that's on an SSD which is really fast.
     
  12. moritaka

    moritaka MDL Novice

    Apr 1, 2015
    43
    9
    0
    my upgrade about 9hrs OMG :p
     
  13. naseap

    naseap MDL Senior Member

    Jul 25, 2009
    489
    123
    10
    Upgrade took a little over an hour on an SSD drive but I did not have a lot of programs installed.
     
  14. webodan

    webodan MDL Novice

    Dec 15, 2014
    9
    1
    0
    it was really slow for me too on real hardware. not only slow, it also didn't install properly and reverted to 10041. i'm afraid i just can't update regardless of using ISO or WU.:(
     
  15. stephr1

    stephr1 MDL Novice

    Jun 2, 2012
    44
    1
    0
    I tried once more and even after leaving it for ~7 hrs. it still didn't upgrade. Once again, when I restarted Win 10 (under VMWare Workstation) it restored to 10041.

    I'm giving up until I can get the .iso version. This is just crazy :(
     
  16. chukwe

    chukwe MDL Novice

    Aug 1, 2009
    17
    0
    0
    Since my Lenovo W520 Upgraded to 10049, most of the drivers has been buggy. Every time I boot up my laptop, it goes into safe mode. I've to reboot it to get it back to normal.

    So the sequence is Boot Up -> Restart immediately to be ok. Does anyone knows what's causing this problem\solution?
     
  17. gigel2007

    gigel2007 MDL Novice

    Apr 9, 2010
    7
    1
    0
    ok this is the worst update.
    I paused the vm, went to sleep. the next day i woke up, i reset the vm, booted bare metal.

    it upgraded after a long two hours new black screen update logo, rebooted, all went nice, ending up with 10049 login screen.

    entered password, started music program, my jpegsaver screensaver started showing pictures, I left it unattended for a while.

    came back when music stopped, everything was frozen, no response to ctrl-alt-del. hard resetted.

    failed to boot, started automatic repair, automatic repairs failed.
    booted again in vm, now it wants to restore.

    currently in the process of restoring to 10041.

    conclusion: AVOID 10049!
     
  18. endbase

    endbase MDL Guru

    Aug 12, 2012
    3,789
    1,100
    120
    For people who have problems with VMachines install set the processer core's to 2 and preferable install on ssd ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. tinybutstrong

    tinybutstrong MDL Junior Member

    Sep 11, 2010
    82
    6
    0
    Took ~8 hours here. Now in Windows task manager it report 100% of disk usage all the time, something is wrong with this build for sure.
     
  20. gigel2007

    gigel2007 MDL Novice

    Apr 9, 2010
    7
    1
    0
    guess what! I am already on SSD, and the vm already has two logical processors allocated! :)
    now I'm just copying my user profile from vhd and reinstall using 10041 iso.