To answer your question, yes, but in all honesty I'm don't remember working on this issue myself. We stopped work on this issue last year to concentrate on our Windows 7 service, but in the past few months we have been working on the Windows 10 service again and we don't have this issue.
Looking at our task sequence, at the beginning we set a variable OSDBitLockerStatus=Protected using WMI: WMI Namespace: root\cimv2\Security\MicrosoftVolumeEncryption WQL Query: select * from win32_encryptablevolume where driveletter = 'c:' and protectionstatus = '1' Then we use the built-in 'Disable BitLocker' step if OSDBitLockerStatus=Protected. Then we restart in Windows PE: [cid:image002.png@01D301A7.D5532AC0] The rest of the task sequence is fairly standard after that. I would surmise that this allows BitLocker to be disabled in Windows and allows the boot image to be staged before rebooting to WinPE. Sorry I'm a bit cagey with my answer, the original issue was some time ago and to be honest I had forgotten we had that issue at all. We have had consultants in helping us work on the new Windows 10 service and either they, or one of my colleagues, must have added this. Let me know if this helps. Dave From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: 19 July 2017 16:16 To: mdt...@lists.myitforum.com; mssms@lists.myitforum.com Subject: [MDT-OSD] RE: Windows 10 OSD 'Failed to install boot image' from Software Center Dave, did you ever find the root cause here? We just ran into the same issue last night on a machine. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West Sent: Wednesday, November 23, 2016 5:08 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com> Subject: [MDT-OSD] RE: Windows 10 OSD 'Failed to install boot image' from Software Center As this is a test build I'm only running the built-in Windows Defender, no other Anti-Virus is installed. I get your point about access denied being the cause. Initially I thought it might be BitLocker, but the 'disable BitLocker' step in the task sequence completes successfully. It seems that the key is the line 'Failed to copy Z:\EFI\Microsoft\Boot\BCD...' which then leads to the ultimate failure of 'BootLoader::restore: C:\_SmsTsWinPE, Z:\...' as I don't think it is mounting the BCD to Z: properly, if at all. I don't know anything about the specific process that is used so I just don't know how to diagnose it any further :( Dave From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: 23 November 2016 17:58 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com> Subject: [mssms] RE: Windows 10 OSD 'Failed to install boot image' from Software Center 0x80004005 does not equal "Access Denied". File in use is often indicative of anti-virus scanning a file and then locking it. J From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Feret, Greg Sent: Wednesday, November 23, 2016 9:21 AM To: mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Windows 10 OSD 'Failed to install boot image' from Software Center Task sequence execution failed with error code 80004005 Equals access denied. I would say you are having trouble writing to the disk for some reason. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West Sent: Wednesday, November 23, 2016 7:06 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com> Subject: [MDT-OSD] Windows 10 OSD 'Failed to install boot image' from Software Center Hi all, We are having an issue here with our Windows 10 image in that if we try and initiate an OSD from Windows via Software Center the task sequence fails with 'Task sequence execution failed with error code 80004005' but if us PXE it works fine. An extract from the log seems to indicate there is a problem staging the boot image... Backing up existing boot system. BackupEfiBoot: Z:\, C:\_SMSTaskSequence\backup-EFI 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 BcdBackup: C:\_SMSTaskSequence\BCD-EFI\bcd Executing command line: "bcdedit.exe" /export C:\_SMSTaskSequence\BCD-EFI\bcd Process completed with exit code 0 0x80070020 = The process cannot access the file because it is being used by another process. The process continues until... Installing boot image to hard drive Backing up existing boot system before trying to set up new boot system BootLoader::restore: C:\_SmsTsWinPE, Z:\ Saving bcd store to C:\_SmsTsWinPE\boot\BCD Failed to install boot image. Unspecified error (Error: 80004005; Source: Windows) Failed to install boot image PLY00055. Unspecified error (Error: 80004005; Source: Windows) Failed to reboot the system. Error 0x(80004005) Failed to initialize a system reboot. Unspecified error (Error: 80004005; Source: Windows) Fatal error is returned in check for reboot request of the action (Restart in Windows PE). Unspecified error (Error: 80004005; Source: Windows) An error (0x80004005) is encountered in execution of the task sequence Set authenticator in transport Task Sequence Engine failed! Code: 80004005 **************************************************************************** Task sequence execution failed with error code 80004005 My favourite error, 80004005 = Unspecified error :( This is on a laptop with UEFI and BitLocker (TPM enabled). The task sequence successfully disables BitLocker and then tries to stage the boot image but fails. The system partition is C: so I assume the reference to Z: is the process temporarily mounting the boot partition. Has anyone come across this or can offer any advice to diagnose this? Any advice would be greatly received. Dave West Senior Operations Analyst Technology and Information Services | 1 Kirkby Place | Plymouth University | Drake Circus | Plymouth | PL4 8AA | UK Tel: 01752 587247<tel://+44752587247/> | Email: dave.w...@plymouth.ac.uk<mailto:dave.w...@plymouth.ac.uk> ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form. ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass> This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
