Aaron@Shared Posted January 28, 2019 Report Share Posted January 28, 2019 I am building new GIs on my desktop and then importing it into SmartDeploy on the server. They import fine and I am able to create my deployment packs. Once I deploy it thru WDS and reboots, I am greeted by an immediate BSOD: Quote The operating system couldn't be loaded because of a critical system driver is missing or contains errors. File: \Windows\System32\drivers\wd\WdBoot.sys Error code: 0xc000000d HELP!!! I do this because I can build 2-3 GIs in a day on my PC compared to 1 on the server. Thoughts? Aaron Link to comment Share on other sites More sharing options...
Jeff Harris Posted January 28, 2019 Report Share Posted January 28, 2019 Aaron, So I understand this correctly; You're creating your virtual machines and then capturing them on your local workstation, and then copying/importing the WIM file to your SmartDeploy console on the server, yes? If you create USB media, boot to SmartDeploy and deploy your image, does it succeed? Are your clients that you're attempting to deploy to via WDS in UEFI mode? Link to comment Share on other sites More sharing options...
Aaron@Shared Posted January 28, 2019 Author Report Share Posted January 28, 2019 Correction: I built the VM on my workstation. Shut it down as stated in the userguide. Then I went into SDE on my Server and imported them from my local PC across the network. We are using PXE boot for network imaging. I will try creating an ISO from the image and deploying it via a VM. The PCs we use have UEFI but we turn SecureBoot off and at the boot menu, select the BIOS not UEFI Network card. Link to comment Share on other sites More sharing options...
Jeff Harris Posted January 28, 2019 Report Share Posted January 28, 2019 If your workstation is that much faster, I recommend leaving the VMs there, shutting them down and then capturing your images locally, and then copy the images to the Server host for deployment. You can have the console installed on more than one workstation without a license penalty. Then it could be a worthwhile test to use the Media wizard to create a SmartDeploy ISO and boot a new VM to that, and test-deploy your image, however I would still recommend using USB media to test it on one of the devices you're attempting to PXE boot, Lastly, if your devices are in UEFI mode, you will want to enable Secure Boot. If your system is in UEFI mode, but you temporarily boot to the Legacy BIOS mode network card, then SmartDeploy is going to detect that it's in Legacy BIOS, and then deploy the image in BIOS mode. Your system will then restart, back into it's normal UEFI mode and thus won't be able to boot. You should be able to manually enable the UEFI Network Stack in the System Settings, but keep in mind that there is additional configuration needed to PXE boot and deploy devices with WDS in UEFI mode. Link to comment Share on other sites More sharing options...
Aaron@Shared Posted January 29, 2019 Author Report Share Posted January 29, 2019 Jeff, thanks. I will try setting up SmartDeploy Ent on another computer, then importing the images and then transferring them to the server. Link to comment Share on other sites More sharing options...
dblameuser Posted September 23, 2019 Report Share Posted September 23, 2019 I am having the same issue, was there a resolution to this issue? Link to comment Share on other sites More sharing options...
Aaron@Shared Posted September 23, 2019 Author Report Share Posted September 23, 2019 16 minutes ago, dblameuser said: I am having the same issue, was there a resolution to this issue? I ended up switching from building the VMs and images on the server onto my workstation. I also use Virtualbox to create a master VM, then duplicate it and then make modifications from there. Link to comment Share on other sites More sharing options...
CAnderson Posted November 4, 2019 Report Share Posted November 4, 2019 I'm getting this exact same error, but only when trying to deploy Windows 10 Enterprise version 1903. I haven't tried an older version of Windows 10 Enterprise, but Windows 10 Pro (any version) is working fine. recapturing the image = same error even remaking the VM + image = same error. Smartdeploy version is 2.0.3050.10466 Link to comment Share on other sites More sharing options...
reilogix Posted January 3, 2020 Report Share Posted January 3, 2020 I have a very similar or same issue. After deployment (Windows 10 Pro 1909, fully Windows updated as of 12/31/2019,) it never will boot successfully. I am greeted with that pesky wdboot.sys error. If I instead load the older image (Windows 10 Pro 1903, fully Windows updated 11/1/2019,) it boots just fine. It makes no difference if I select LEGACY or UEFI Boot. Link to comment Share on other sites More sharing options...
mbuit Posted November 10, 2020 Report Share Posted November 10, 2020 I keep getting the same blue screen after I image any PC. I have tried deploying with WDS and USB and get the same result. I have tried turning off secure boot thinking that maybe that was the issue and it still doesn't work. I'm at a loss right now and I have a pile of laptops that need to be imaged. Link to comment Share on other sites More sharing options...
Aaron@Shared Posted November 16, 2020 Author Report Share Posted November 16, 2020 Add the following into your answer files: Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now