SOLVED Task Sequence fails- only on one model machine

[Kave70]

Made a TS- to deploy an OS. Itruns on many different model machines, but continously get a failure on a particular lenovo model- we have 250 of these in production, so I need to figure this out. If I run it off of a usb task sequence media and not over the network, it succeeds. I made sure I had the newest drivers .
Attached is my smsts.log.

Any thoughts?
I'm stumped since it works on several other models.
Thanking you in advance,
Karen

 

[Kave70]

I believe I have narrowed it down to an error " Failed to copy Z:\EFI\Microsoft\Boot\BCD to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD. 0x80070020
Failed to copy Z:\EFI\Microsoft\Boot\BCD.LOG to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD.LOG. 0x80070020"
When comparing the log files of every failed machine, this always stands out. However, this same OS TS works fine on other machines on our network. Any thoughts?

 

[AnthoniusUK]

Did you find a solution to this? We had a perfectly fine task sequence that runs a migration to our current image and have successfully used it for the last year. However one office has computers not built to standard and we are sporadically seeing this error for the computers with SecureBoot and a similar error for those on legacy. We have yet to find a common denominator as we could have identical models with the same hardware have to completely different results.

 

[Kave70]

I ended up having to change the task sequence to choose either UEFI or BIOS - it works now.

 

[AnthoniusUK]

I ended up having to change the task sequence to choose either UEFI or BIOS - it works now.

Thank you for responding Alas, that wasn't our issue. Our TS allows for either of them, and some of our computers are on one, and some are on the other. I'm not sure what was. It was definitely something from inside the Operating System. As soon as we PXE built it with our image, it could boot into WinPE no issue. Obviously once PXE built, it completely made our need for migration to our image redundant. Sadly we had to resort to PXE building that whole office. The closest we got was related to resetting the appx's for win 8 and win 10 and resetting the SysPrep keys (Despite the fact that we weren't capturing an image). From here we could sporadically boot to WinPE, but we ran out of time before we could make it work consistently.

 

[SARANNOV&]

I have the same issue in my local environment. Any suggestions ?

Volume '\\?\Volume{86528e51-5917-4e28-94d5-1e89aa5c67c5}\' not found TSManager 20/02/2019 08:01:49 9180 (0x23DC)
BackupEfiBoot: Z:\, C:\_SMSTaskSequence\backup-EFI TSManager 20/02/2019 08:01:49 9180 (0x23DC)
Failed to copy Z:\EFI\Microsoft\Boot\BCD to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD. 0x80070020 TSManager 20/02/2019 08:01:49 9180 (0x23DC)
Failed to copy Z:\EFI\Microsoft\Boot\BCD.LOG to C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD.LOG. 0x80070020 TSManager 20/02/2019 08:01:49 9180 (0x23DC)
BcdBackup: C:\_SMSTaskSequence\BCD-EFI\bcd TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Executing command line: "bcdedit.exe" /export C:\_SMSTaskSequence\BCD-EFI\bcd TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Process completed with exit code 0 TSManager 20/02/2019 08:01:50 9180 (0x23DC)
A valid boot image ID must be present in order to boot into WinPE TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Failed to reboot the system. Error 0x80004005) TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Failed to initialize a system reboot.
Unspecified error (Error: 80004005; Source: Windows) TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Fatal error is returned in check for reboot request of the action (Restart Computer into Windows PE).
Unspecified error (Error: 80004005; Source: Windows) TSManager 20/02/2019 08:01:50 9180 (0x23DC)
An error (0x80004005) is encountered in execution of the task sequence TSManager 20/02/2019 08:01:50 9180 (0x23DC)
MP name must be set in an environment variable TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Non fatal error 0x80004005 in sending task sequence execution status message to MP TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Task Sequence Engine failed! Code: 80004005 TSManager 20/02/2019 08:01:50 9180 (0x23DC)
Task sequence execution failed with error code 80004005 TSManager 20/02/2019 08:01:50 9180 (0x23DC)

 

[Kave70]

I ended up having to change the task sequence to choose either UEFI or BIOS. Did you try that?

 

[SARANNOV&]

I ended up having to change the task sequence to choose either UEFI or BIOS. Did you try that?

Thank you for the response. Actually we already have enabled choose either UEFI or BIOS.

 

[anthonius.uk]

It may be a bit early for me to post this, however we have managed to have a bit of a break through. After this issue returned sporadically, we started to investigate again.
We assigned a drive letter to the system drive in Diskpart and manually disabled bitlocker (despite the Disable Bitlocker step) and suddenly it started behaving. As a solution it almost feels too easy considering how much time I spent on this last time. I am going to script this into a step or two in the task sequence and try again. Hopefully this will solve the issue for any others that have this problem.

 

[chunfz]

At the end of the task sequence, add restart computer and choose to boot from the currently installed default operating system. I succeeded!!!!!!