2017 MacBook Pro -vs- Windows 10 April Update (version 1803)...

Discussion in 'Windows, Linux & Others on the Mac' started by smckenna, May 5, 2018.

  1. smckenna macrumors newbie

    May 5, 2018
    I've been running BootCamp Windows 10 version 1709 for months now, very stable with the latest BootCamp drivers.
    Windows is trying to update to the new "April Update" version 1803, and it bombs out at 43% with BSOD. I even downloaded the ISO and started a brand new Windows installation from scratch and that bombs out as well. Once with CLOCK_WATCHDOG_TIMEOUT, and once with WHEA_UNRECOVERABLE_ERROR.
    Has anyone successfully gotten Win10 version 1803 to install on their 2017 MacBook Pro yet?
  2. slimwallet, May 5, 2018
    Last edited: May 7, 2018

    slimwallet macrumors newbie

    Oct 9, 2015
    i just tried and got the same issue. CLOCK_WATCHDOG_TIMEOUT at around 43%
    Edit: 2017 15" MBP with 560 GPU.
  3. KUKitch macrumors 6502


    Jan 10, 2008
    I just did a new boot camp install this past week, and just got the spring creator update installed as well - 2017 15"... seems to have gone fine
  4. Husky29 macrumors newbie


    Dec 29, 2017
    Western Cape, South Africa
    I have a 2017 15" 2.9GHz with Radeon Pro 560. I had Windows 10 1703 installed initially with Boot Camp 1 year ago. Then upgraded to 1709 when that came out, no problems. Upgraded to 1803 when that came out, also no problems, went very smoothly. I am not sure what could be causing the problems other people have been having.
  5. saynax macrumors newbie

    Jul 8, 2016

    This may be anecdotal but I previously had the same issue - I was stuck in an infinite loop of Win 10 forcing the update upon me every other day and it failing and rolling back automatically.

    Until it worked one day without me changing anything, except for: When the update gets installed your Mac will restart several times. Usually, I was away from the computer during the restarts and it would default into MacOS throughout, and I would then catch it, restart into Windows 10 again to continue the update until it failed.

    Now I don't know if this was sheer luck and just random, but the one time I managed to successfully install the update I stayed by my computer and ensured that during each restart I was present and ensured to boot directly into Windows 10. Could just be an odd coincidence, but this worked for me (once).

Share This Page