MDT Upgrade - Blank Wizard.HTA Window

Daren Slick 1 Reputation point

I just build a MDT upgrade task sequence for Windows 1909. This is being run against 1903 machines and I am using MDT 6.3.8345.1000.

Regardless how I initiate the sequence (manual or cmd) I always end up with a successful upgrade but a blank Wizard.HTA stops it right after the computer reboots and reaches 100% on the blue Windows is updating screen.

If I exit out of the Window the computer immediately goes to the Windows logon screen for 1909 and everything works. This issue is exacerbated by the fact the cursor isn't visible.

I have tried updating drivers and running the sequence on a Citrix desktop to avoid any potential hangs with Always-On VPN.

Any help would be greatly appreciated.

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
827 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Rick Someone 411 Reputation points

    From one convo I saw you need to make sure drivers are not getting upgraded.

    I have that in place in our GPO. However, you can add lines in MDT to prevent this:

    1. Run Command Line - Load Registry HKLM

    reg.exe load HKLM\MountedHive %OSDisk%\Windows\System32\config\SOFTWARE

    1. Run Command Line - Disable Driver Download

    regedit /s %ScriptRoot%\disabledriverdownload.reg

    disabledriverdownload.reg contents:

    Windows Registry Editor Version 5.00



    1. Run Command Line - Unload Registry HKLM

    reg.exe unload HKLM\MountedHive

    Additionally, you should ensure you have the correct NIC driver installed and WinPE drivers because Windows is set to search for newer drivers and will replace the correct one with one it thinks is correct.

    0 comments No comments

  2. Slick, Daren 1 Reputation point

    44438-wizard.log44487-bdd.log44439-litetouch.logThanks for the response.

    I did try adding the latest driver into MDT and adding that registry key to a computer prior to running the upgrade.


    0 comments No comments