Windows 10 April Update, Version 1803 - Failed Installation

RobertM40 said:
I haven't been able to complete the 1803 update install either. After running Windows update and installing, the VM restarts and counts up the percentage installed as normal. Then it reboots again and shows the update progress again, but it stays at 0%, and the spinner doesn't move. There is hard drive and CPU activity for awhile, but after about a half hour, the both drop off and the VM is completely inactive. I've left it overnight twice now, and it never goes further.
After a reset, it gives me the option to roll back, but that just leads to a black screen. Fortunately I made a snapshot before rebooting to start the install, so I can at least get back into the system. But the snapshot was made after the update was downloaded, so it will try again on the next restart. Hopefully there's a solution to this issue soon, as I can't just keep rolling back to the old snapshot.
Click to expand...

I have exactly the same issue - has someone an idea how to fix this?
 
Luckily I had a snapshot from the day before after installing the faulty april update. :)
I've cloned my vm and did some tests - it seems that I have a resolution at least for my problem.

In the preferences of my vm I limited the CPU to one and the memory to 2GB and removed the USB- and Buetooth-entry from hardware tab.
--> I think the last setting did the trick.
With this settings I was able to install the windows april update (1803) from a mounted ISO-file.

Currently I'm trying to do this again but with online update and only with removed USB- and Bluetooth devices.

If this works I'll try to update my original vm...
 
Last edited:
Also after a clean install windows freezes shortly after start.
--> It seems that it freezes (at least) as soon as a message is display (black message box in lower right corner) e.g. when you insert a dvd or iso.
 
After several attempts, 1803 installed for me by doing the following (as posted above):

1. deactivated Media Player
2. turned off fast startup (although, this was turned back on during update)
3. disabled anti-virus
 
After multiple attempts to update, I did the one described in the previous messages. Thank you to the people who took the time to find the solution.
Disable "USB and Bluetooth" and reset the profile of the VM.
When restarting, the installation goes up to 30%, then black screen. But after a few seconds, the VM restarts, and the installation resumes at 30% and continues. Then idem at 75%.
The installation of the update, ended up being total. And everything is working properly.
 
AlBundy33 said:
I have exactly the same issue - has someone an idea how to fix this?
Click to expand...
This above is also exactly what has happened to me.
After reading the forums here, if I do the following, will I be able to update successfully?
Follow these steps to update my vm to 1803:
disable usb and bluetooth in hardware tab and reset the profile settings of the vm.
 
These steps below worked for me, THANKS to those who found and posted this problem solver!

Feature Update to Windows 10, version 1803:
+ started Mac and Win 10 vm as usual
+ created new snapshot of vm (just to be safe)
+ shut down vm
+ disabled access to USB & Bluetooth in vm Config hardware tab
+ reset profile from Dev to Productivity (and back to Dev) in vm Config general tab
+ started update to 1803
+ after about four auto restarts during update plus auto Parallels Tools reinstall, vm opened normally
+ checked vm Config for usual settings, all ok now
+ reset display resolution and text size percent in display settings for Win 10 vm (for unknown reason, the update caused a change), all ok now
Glad this is complete; however, since the issues I had (as others did as well) were related to Parallels, doesn't it seem like the Parallels people could have indicated these steps to assist us before we wasted so many hours?

Again, THANKS to you on this forum!
 
I had to do a lot of updates and clean installations until I have found out the problem.
First Updates (online and from dvd) and clean installs failed.
After that I've tried a clean install in a new vm - as this was working as expected I was sure that this must be an issue with the settings.

I'm glad that my steps are working by others too.

Maybe it's time for parallels to add this to their knowledgebase.
 
Thank you very much for this posting!

It helped me to get the update installed. But there are two minor inconsistencies I found:

- Parallels now does not show the developer setting any more.
- Windows now occupies about 7 GB more than before.

Regarding the last point my VM is now about 52 GB with nothing really big installed. Is there a way to get it smaller?
 
Hi all,
My problem of black screen (during system shutdown) after update to Win April 2018, I solved it by deleting the VM and Parallels, and doing clean installation of Parallels and Windows 10 Pro (via .ISO), now seems to work all correctly and the VM it seems a lot more performing!
Ciao ciao
 
You must log in or register to reply here.
Back
Top