Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

Keep in Mind........
ImageX is not required.........
You CAN do ImageX....That is more Native Windows Imaging and works with Shares.

You can also do "zac img" and that works over TFTP as always.

If you open an SR, I'm sure you can get someone to talk you through it....though if the person you are talking to does not seem to grasp the issue, may want to get it escalated....
Not all FL engineers have a ton of WinPE Imaging support YET.....
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
ex Trusted Contributor.
Trusted Contributor.

Re: Deploying Windows 10 1803 BCD error

This seemed to lose traffic ....anything new on this issue at all? Seems it would gain a lot more attention, seeing as we are all at the same impasse. Our campus has been imaging Win10 since v1511, then at 1709, it started to get shaky. Every machine had to have chkdsk /f run on it to get ZCM / NAL functional working. Now with v.1803+, we are dead in the water, just spinning dots w/out anything meaningful to troubleshoot on.

We are still running ZCM 11.2 and with the downtime required, we are not able to update Zen2017. Either way, it is still the same issue on 2017.

Does this end here and the only resolution to use something else, don't use ZCM and it's Microsoft's fault?

I don't see where any WinPE option is built into ZCM. We are Linux on everything but 4000 end-users and this is to remain. Is WinPE the 3rd party product made by "ENGL"

Regards .... Eric
0 Likes
tpicrum Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

ex;2498211 wrote:
This seemed to lose traffic ....anything new on this issue at all? Seems it would gain a lot more attention, seeing as we are all at the same impasse. Our campus has been imaging Win10 since v1511, then at 1709, it started to get shaky. Every machine had to have chkdsk /f run on it to get ZCM / NAL functional working. Now with v.1803+, we are dead in the water, just spinning dots w/out anything meaningful to troubleshoot on.

We are still running ZCM 11.2 and with the downtime required, we are not able to update Zen2017. Either way, it is still the same issue on 2017.

Does this end here and the only resolution to use something else, don't use ZCM and it's Microsoft's fault?

I don't see where any WinPE option is built into ZCM. We are Linux on everything but 4000 end-users and this is to remain. Is WinPE the 3rd party product made by "ENGL"

Regards .... Eric


I found the fix- that will work on Windows taking forever to load *if you get to that point- windows Store update needed to be stopped. This was causing the issues along with extremely log mini setup times. I hope this helps anyone with this issue. Microsoft was not able to find the fix after working with their premier support.
WinPE is just a preboot environment for imaging. ZCM should work without an issue - considering you are just making an image file, once it's packaged, you shouldn't have any issues.

# Disable Windows Store Automatic Updates

Write-Host -Message "Adding Registry key to Disable Windows Store Automatic Updates"

$registryPath = "HKLM:\SOFTWARE\Policies\Microsoft\WindowsStore"

If (!(Test-Path $registryPath)) {

Mkdir $registryPath -ErrorAction SilentlyContinue

New-ItemProperty $registryPath -Name AutoDownload -Value 2

}

Else {

Set-ItemProperty $registryPath -Name AutoDownload -Value 2

}

#Stop WindowsStore Installer Service and set to Disabled

Write-Host -Message ('Stopping InstallService')

Stop-Service InstallService

Write-Host -Message ('Setting InstallService Startup to Disabled')

& Set-Service -Name InstallService -StartupType Disabled

}
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

ZCM 11.2 does not support Windows 10 in any way manner.
Windows 10 Support was added in 11.4.1.
If I were to guess, you are actually running 11.4.2, which CAN support Windows 10, though ZCM 11.4.x has been out of support for quite a while now.

I will assume you are running ZCM 11.4.2 in may answer and not 11.2.

The Simplest and most Error Free way to Image Windows 10 is to image the base install before applying Any Update or Any Patches or Any Software adds.
Say no to apply patches during the install. Perhaps keep the device off the network during install to ensure this.
(Note: If you want to install the ZCM agent at this point that is fine, but most folks prefer adding that after the fact.)

The Internet Traffic about Windows Updates causing Imaging Issues in Pure MS Environments probably runs a close 2nd to Netflix for total internet traffic. (Yes, I'm exaggerating...but its ALOT)
The issues you are experiencing have nothing to do with ZCM code.

There are sites that have pages of scripts and tips on how to make Windows imaging still work after patched, but it gets deep and very complex and its all heavy Core Window OS understanding stuff.....
The Prior tip may help....but.....

#1 - Make sure you are not patching Windows before imaging....even during the Windows install.



ex;2498211 wrote:
This seemed to lose traffic ....anything new on this issue at all? Seems it would gain a lot more attention, seeing as we are all at the same impasse. Our campus has been imaging Win10 since v1511, then at 1709, it started to get shaky. Every machine had to have chkdsk /f run on it to get ZCM / NAL functional working. Now with v.1803+, we are dead in the water, just spinning dots w/out anything meaningful to troubleshoot on.

We are still running ZCM 11.2 and with the downtime required, we are not able to update Zen2017. Either way, it is still the same issue on 2017.

Does this end here and the only resolution to use something else, don't use ZCM and it's Microsoft's fault?

I don't see where any WinPE option is built into ZCM. We are Linux on everything but 4000 end-users and this is to remain. Is WinPE the 3rd party product made by "ENGL"

Regards .... Eric
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
ex Trusted Contributor.
Trusted Contributor.

Re: Deploying Windows 10 1803 BCD error

You are absolutely correct - we are running 11.4.2.0. (typo)

Thanks for the responses! I'll digest and run with this, see if I can achieve positive results. Something tells me this will be an ongoing issue with Windows 10 as their updates are very intrusive.

- Eric
0 Likes
ex Trusted Contributor.
Trusted Contributor.

Re: Deploying Windows 10 1803 BCD error

Unfortunately...still living in a cesspool of Windows 10 imaging here.

To spell it out, clear as mud - We're using Windows 10 Education N 1809 (same with 1803) ISO but to DVD.

We install a brand new (base) onto an HP Elitedesk 800 G2 or G3. Have network cable unplugged all the while. No updates. Build/install which reboots the computer. Comes up asking 'what country' AT THIS POINT WE GO INTO AUDIT MODE via Shift-CTRL-F3, which brings you to a desktop with the little audit mode box. With PC still unplugged from the network, make sure WindowsStore and Installer Services are stopped and disabled. There is never any installing of any additives what-so-ever.

At this point, we set the audit mode window to Out of Box Experience, NO to generalize and select shutdown, click OK and it does a graceful shutdown. We turn on the box, PXE boot, zmg img an image error-free.

From here when we push computer down to another (whether is has or has not been in ZCM before) identical computer, it just spinning dots starting up, forever and evermore.....never letting you know what it is hung up on...just spinning until eternity dies out.

We've tried BIOS Legacy (with and without HP secureboot). Tried BIOS UEFI.
We've tried without running Audit Mode, as if any other normal MS consumer would do at home.
We've tried it standing on our heads singing dixie out of our ..., still nothing.

If we use win10 v1709, it images and runs like a champ ('ish), updates or no updates, legacy or UEFI mode - it images, it works. Anything higher, complete failure.

So, what on earth is the other 99.999% of the ZCM world doing to get Windows 1809 and above to image successfully that I'm missing? I wish to switch to SLED was an option but people are bread to note accept change.

Any other tips or tricks anyone has discovered to beat down this MS beast, please spread the love!!

- Eric
0 Likes
tpicrum Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

If you are pushing the image to other PCs, you will need to have the Generalize option checked. Besides that, if you aren't removing any provisioned apps, I don't know why you would have an issue. Are you able to blow the image out on a PC (until where it has the spinning dots), pull the drive and grab the "C:\windows\system32\sysprep\panther\setuperr.log/Setupact.log Maybe that will give us a little insight.. if it is even populated with any data.
0 Likes
ex Trusted Contributor.
Trusted Contributor.

Re: Deploying Windows 10 1803 BCD error

tpicrum;2498462 wrote:
If you are pushing the image to other PCs, you will need to have the Generalize option checked. Besides that, if you aren't removing any provisioned apps, I don't know why you would have an issue. Are you able to blow the image out on a PC (until where it has the spinning dots), pull the drive and grab the "C:\windows\system32\sysprep\panther\setuperr.log/Setupact.log Maybe that will give us a little insight.. if it is even populated with any data.


We have an extentive log of what has been tried and we've selected Generalized mode at one point with out success. I'm going to try installing Windows 10 (Bios = Legacy / partitions = MBR) , unplugged from network and select the generalized option at audit mode, shutdown, take image.

Yes, everytime we are able to image to the point of the spinning dots. I didn't think of yanking the drive for logs, will give that a shot, thanks.
0 Likes
astock Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

ex;2498436 wrote:
With PC still unplugged from the network, make sure WindowsStore and Installer Services are stopped and disabled.


Be extremely careful with disabling services before running sysprep, I also got a headache why my syspreped Windows wouldn´t come up and it came out it was one of those "unneeded" services that where disabled before taking the sysprep.

The part with the unplugged network is imperative as if Windows catches an update server in audit mode there will be trouble later on if the image wants to come out of sysprep.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

Note: The "Windows Installer Service" is a Critical System Service. "Windows Update Service" perhaps....
But generally agree I would not go with messing with too much during the initial Image Build....
Change those settings post deploy....but definitely don't mess with "Installer Service".....


--

Re: Deploying Windows 10 1803 BCD error

Quote Originally Posted by ex View Post
With PC still unplugged from the network, make sure WindowsStore and Installer Services are stopped and disabled.
Be extremely careful with disabling services before running sysprep, I also got a headache why my syspreped Windows wouldn´t come up and it came out it was one of those "unneeded" services that where disabled before taking the sysprep.

The part with the unplugged network is imperative as if Windows catches an update server in audit mode there will be trouble later on if the image wants to come out of sysprep.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.