Windows 10 1903 Black Screen

Question

I have created new images using the new Windows 10 1903 update on Hyper-V. After creating the image and deploying it to machines, they tend to give a black screen where the lock screen should be (sometimes with a mouse, other times not). The monitor is getting signal as displayed by the indicator, but I cannot do anything. This typically happens right after Windows set up and occasionally when the screen locks or the system is restarted. I have updated the family driver packs that couple with the image during deployment as well. Has anyone else run into this issue? I'm at a loss.

gwwells · Answer

Yes.  I have the same issue and have not found a good work around other than rebooting. Highly annoying!!!

tkoscielniak · Answer

The 1903 version was released then pulled back several times for issues. After final release, the OEMs have 3 months to get drivers prepared for the version. Driver packs for 1903 are not complete as of yet. I'm told they should be posted in a few weeks. Until then, there might be some issues with how 1903 behaves on some systems. When we release the driver packs on the ImageAssist site, you still have issues, please contact the ImageAssist Support desk and open a trouble ticket.

MarkDubois · Answer

August 1st (19-08), 5 months after release and this is still an issue. Testing on VM and the image works perfect. Test on Optiplex 3060 and it boots to black screen. Just checked for updated driver, tool says their aren't any. Do we have to rebuild our Image to 1809 or do you have an updated driver we can use?

tkoscielniak · Answer

For the OptiPlex 3060, please use the 'OptiPlex D9 Rev A08' driver pack. The site still says it is for 1809, but the driver pack is correct. If this does not work, please contact the ImageAssist support desk and log an issue. thx....TK

Santos13 · Answer

There is a possibility that the image got corrupted on the capturing process.

Was the image created to "automatically joint the domain" on the unattended XML form? If yes, try capturing set up as workgroup.

The best practice is to build a new virtual machine on Hyper V applying the following settings.

Note: If using Windows 10 Pro or Education, download a free ISO from Windows Media Creation tool. Do not update the OS via automatic updates.

https://www.microsoft.com/en-us/software-download/windows10

Do not update the OS via automatic updates to avoid Sysprep issues.

Launch Hyper-V Manager and on the top Main Menu>New>Virtual Machine>Next
Name your VM and save in a specific folder
Specify Generation: Generation 2
Assign Memory: Depends on the computer’s memory capacity but the minimum is 2 gigabytes Note: On 8 gigabytes memory: Best performance setting is 3 gigabytes (3072 kb). If 10 Gig or higher computer memory, on VM, enter memory size avoiding VM freeze/crash or slowing down of your host computer.
Dynamic Memory: Uncheck
Configure Networking: Not connected (do not enable) You can turn on after the virtual machine is created and Windows 10 automatic updates are disabled-stop.
Connect Virtual Hard Disk: Create a Virtual Hard Disk (For small size Images try 80 Gig HD size or as needed)
Install an Operating System from a bootable Image File: Browse to your OS media.
Finish

-----------------------------------------------------------------------------------------------------------------------------------------------------

Additional configuration after VM creation and before Operating system Installation

Click to highlight the Virtual Machine’s name. Under the bottom right pane>Your “Virtual machine name”>Click settings> (New windows will open)
On the left upper pane-Hardware>
Security: Disable Secure Boot (uncheck)
Processors: 2 cores
On the left bottom pane-Management> click, Integrations Service> place a checkmark on Guest Services> Ok.
Follow the provided Power Pont presentation for additional configurations for How to make the host computer’s HD visible in your Hyper-V.
Install the operating system. Note: Once the Operating System is installed, immediately disable Windows 10 Automatic updates to avoid the OS update via the internet.
Install ImageAssist, capture and deploy for testing purposes. Note: Capture an image without adding additional applications and deploy to verify functionality and compatibility.

To avoid image corruption:

Do not remote control into the Hyper via other sources like a server connection, or desktop remote. Control the virtual machine It directly from the host computer
If Windows 10 was updated via automatic windows updates, or a windows upgrade mas made, SysPrep may fail or freeze the capturing process by packages or applications.
In the capturing process, make sure there is no local network connection. The VM needs to be isolated from external resources.

MarkDubois · Answer

Thanks Santos. Yes it's set to join the domain. We need all the machines to join the domain automatically. When tested, the image does join the domain successfully, but it just sits at a black screen. When deploying the image on a VM, it works flawlessly which leads me to believe it's something with the driver/hardware. Yes, we are using win10_optiplex d9_a08 driver pack.

T_Raun · Answer

We have the same issue with latitude 7490 and 7300. with the dell driver pack, i get the issue.

if i deploy the image with no drivers, so windows installs what it can, i dont get the error.

on the 7490, i installed it and the ran the dell command update, and the grapped the drivers, then i could use the drivers for deployment, but it is not the case for the 7300.

techaanderson · Answer

Having the same issue on Latitude 5400 and Latitude 5500. Found https://social.technet.microsoft.com/Forums/azure/en-US/4bc1dc59-8309-444e-9041-e0fdba282e11/mdt-8456-windows-10-1903-windows-updates-deployment-pauses-for-almost-an-hour-help?forum=mdt while researching and was unable to resolve after performing rollback procedure here (https://support.microsoft.com/en-us/help/4052623/update-for-windows-defender-antimalware-platform) and re-capturing.

ED_The_Dog · Answer

After a lot of trial and error I found that removing both Intel Corporation SCSIAdapter iaStorAC.inf 17.0.0.1072 and Intel Corporation SCSIAdapter iaStorAC.inf 17.2.4.1011 from the driver pack eliminated the black screen issue on a Dell 7300

Mark_OSI · Answer

Thanks ED_The_Dog.

Was able to test this with some models I have here and same issues on the following:

Intel Corporation SCSIAdapter iaStorAC.inf 17.2.6.1027

Intel Corporation SCSIAdapter iaStorAC.inf 17.0.2.1076

The following driver WORKS:

Intel Corporation SCSIAdapter iaStorAC.inf 17.2.7.1028

Image Assist

Was this post helpful?