Azure VM won't boot after sysprep; integration tools installed

Posted by Mark Williams on Server Fault See other posts from Server Fault or by Mark Williams
Published on 2012-09-10T17:13:46Z Indexed on 2012/10/02 21:41 UTC
Read the original article Hit count: 184

I have installed the Azure Integration Components and used sysprep on a Windows 2012 VM.

Now the machine won't start up. I uploaded the VHD to Azure - it failed there too.

When I start up the VM I get a PowerShell window that hangs out for a bit; eventually I get the following error, after which the machine restarts.


New-Object: The dependency service or group failed to start. (Exception from HRESULT: 0x8007042C)

At line1: char:1

  • New-Object -comobject WaAgent.WindowsSetupComponent | % { $_.HandleSetupError() ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +CategoryInfo : ResourceUnavailable (:) [New-Object], COMException +FullyQualifiedErrorId: NoCOMClassIdentified,Microsoft.PowerShell.Commands.NewObjectCommand

I have tried renaming unattended.xml and turning on bootlogging. Neither of those yielded much help.

Is there a way I can disable the Azure components that run during OOBE? That seems to be the source of the problem. Mounting the VHD is easy.

0x8007042C looks like a firewall issue, based on my googling. Unfortunately I can't get the machine to boot so I can figure that issue out.

Also, I can't get around this problem by booting into safe mode.

Thanks for your help, guys.

© Server Fault or respective owner

Related posts about Azure

Related posts about sysprep