jfeyen Super Contributor.
Super Contributor.

Re: Deploying Windows 10 1803 BCD error

Try reuploading the TUXERA driver.

I just got a working sysprepped image Windows 10 UEFI build 1803 with ZENworks 2017 U2 + March imaging update.

Kr,

Joeri
0 Likes
pwolff2000 Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

bryanlakatos;2481651 wrote:
No luck with ZENworks. Still doing imaging with Clonezilla and an NFS share. Works perfectly.


We have the same spinning dots. We fix the clone by forcing the computer off, starting with a Win10 repair CD/USB stick, choose Troubleshooting, Command Prompt, run chkdsk c: /f, when chkdsk completes type exit at the prompt, eject CD/USB, power down. Power back on and the cloned computer should boot. I know this isn't a long term fix, but I only have a few labs to re-image this year and I am tired of fighting imaging issues every new Windows/Zen version. Call it the redneck fix....;)
0 Likes
xsisbest1 Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

I'll be working on my windows 10 1803 image next week and will post my results. So far with 1803 I've created a nice mdt deployment but not a zen image. Everything works fine though using Zen to push down my deployment though if it's any consolation.
I've come to the conclusion I will not be able to multicast my mdt deployment so I will need to configure a Zenworks image to do so. I do have a an unattend I could share just in case there is something in there you may not be seeing. I know in the past I had to remove anything that had to do with Internet Explorer in the unattend file or it would fail. But not hang like your mentioning so I doubt it's that.
0 Likes
tpicrum Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

I've been having the same exact error. I build all images in a VM environment. When building the 1803 the image I used Audit mode. (shift+F3 before minisetup) I tweaked the image and did remove most provisioned apps with the "windows 10 Debloater" powershell script from GitHub. Build 1709 went flawlessly. It seem to be an issue with one of the apps.
Also, sysprep will eventually complete, when it reboots, mini setup will run but takes a LOOONG time. It will come up but the time it takes to complete is ridiculous.

more details -
I also built a new unattend file from the 1803 Wim.

I'm attempting to remove each app, one by one and sysprepping to see what is the root cause. I'll reply back with an update. It would be nice if they kept things the same.

When I sysprep the machine without removing any apps, it comes up flawlessly. It has to do with the app removal.
0 Likes
tpicrum Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

I sysprepped a freshly installed windows 10 1803 with no alterations. Minisetup started BUT, in the setuperr.log I did receive the following errors again . There has to be something going on with Windows 1803 sysprep. :mad:

2018-09-29 02:47:21, Error TOOL BCD: BiUpdateEfiEntry failed c000000d
2018-09-29 02:47:21, Error TOOL BCD: BiExportBcdObjects failed c000000d
2018-09-29 02:47:21, Error TOOL BCD: BiExportStoreAlterationsToEfi failed c000000d
2018-09-29 02:47:21, Error TOOL BCD: Failed to export alterations to firmware. Status: c000000d
2018-09-29 02:47:25, Error SYSPRP ClipCleanUpState resetting WNF_OLIC_OS_LICENSE_TERMS_ACCEPTED failed with NTSTATUS=c0000022
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

I would look at the next to last message as more important than the last.....
I think the preceding errors result in the final message....

Does the Systmem have an SSD Drive?
Seems that was a partial cause in some of the hits...
I do know that 1803 did break some SSD Drive compatibility....
But really the root causes were far from consistent and most come down to no solution....
--
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
EGruber1 Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

Hello,
two weeks ago I started to try deploying win10 with Zenworks. We used Zenworks imaging for about 4 years with Win7 without any problems, but when I started now with Win10, I also ran into the problem with the spinning dots.
I tried it with a VMWare master machine and a physical one. In both cases the same problem. I finally only made an image from a machine in audit mode, without any changes to it. I made an image and loaded it down at the same machine, the machine ran into the running dots. Is still no solution available, so that imaging with zen will work again?
@tpicrum: Did you find out which app is responsible for this problem?
regards
E. Gruber
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

Best to Add/Remove Apps and Patch post restore.....
Not really a ZENworks thing...but MS really broke quite a few thing with imaging in Windows 10....at least in regards to how they used to work.

I would also recommend to start looking at WinPE based imaging vs Linux Based imaging.....
Using WinPE, you can still use the familiar ZCM imaging commands and ZMG files but will add faster new hardware support.

From there.....it will be a smaller step to start doing some of the newer imaging methods via ZENworks...such as what is basically a scripted OS install....that MS is trying to push.



EGruber1;2493419 wrote:
Hello,
two weeks ago I started to try deploying win10 with Zenworks. We used Zenworks imaging for about 4 years with Win7 without any problems, but when I started now with Win10, I also ran into the problem with the spinning dots.
I tried it with a VMWare master machine and a physical one. In both cases the same problem. I finally only made an image from a machine in audit mode, without any changes to it. I made an image and loaded it down at the same machine, the machine ran into the running dots. Is still no solution available, so that imaging with zen will work again?
@tpicrum: Did you find out which app is responsible for this problem?
regards
E. Gruber
--
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
EGruber1 Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

Thank you for your answer Craig,
do you know anywhere a tutorial/howto how I could start WinPE-based imaging and still using ZCM?
regards
E. Gruber
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

I would recommend ZCM 2017 Update 2 or Later...Since that is when "Legacy ZCM Imaging Commands" were added to ZCM Imaging.

see - https://www.youtube.com/watch?v=cMmwvxnYglE
--
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
Micro Focus Expert
Micro Focus Expert

Re: Deploying Windows 10 1803 BCD error

But in short....the ZCM PXE Server can be set to Send WinPE boot files just like it sends Linux Boot Files.
From Windows...You can run "img" commands just like from Linux to make ZMG Files just like always.
This makes the Learning Curve Smaller.....

However...Once you are in WinPE...you now have access to branch out to lots of other "Native MS" imaging options as well.

Ask Ask Ask....
there are quite a few folks on here who have made the switch and have more current hands on experience than I.
--
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
Highlighted
EGruber1 Absent Member.
Absent Member.

Re: Deploying Windows 10 1803 BCD error

Hello,
CRAIGDWILSON;2493438 wrote:
I would recommend ZCM 2017 Update 2 or Later...Since that is when "Legacy ZCM Imaging Commands" were added to ZCM Imaging.

see - https://www.youtube.com/watch?v=cMmwvxnYglE


thank you very much for the video. Configuring 3rd party imaging was no problem. but when I try to take an image, I alwas get the message 'imagex reported an error' without explanation of the error. I tried different shares on different machines. I don't know how to debug this error, because winpe has very limited functionality (Win 10 1809).

Can you please tell me: Would it be still possible to add ZCM addon-images and do automated imaging as it with the linux-based method was?

regards
E.Gruber
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.