Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Accidently deleted boot images and cant get them back

%3CLINGO-SUB%20id%3D%22lingo-sub-3040879%22%20slang%3D%22en-US%22%3EAccidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3040879%22%20slang%3D%22en-US%22%3E%3CP%3EI%20deleted%20the%20boot%20images%20from%20my%20software%20library%20and%20cant%20find%20a%20way%20to%20recreate%20them.%20I've%20tried%20creating%20a%20windows%20PE%20boot.wim%20using%20the%20ADK%20and%20also%20importing%20from%20a%20location%20in%20the%20SCCM%20folder%20tree.%20Nether%20worked.%20Any%20advice%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%20is%3C%2FP%3E%3CP%3EError%3A%20Data%20Source%20Information%3CBR%20%2F%3E%E2%80%A2%20Source%20location%3A%20%5C%5CSTR-sc01%5CE%24%5CProgram%20Files%5CMicrosoft%20Configuration%20Manager%5COSD%5Cboot%5Cx64%5Cboot.wim%3CBR%20%2F%3E%E2%80%A2%20Boot%20Image%3A%201%20-%20Microsoft%20Windows%20PE%20(x64)%3CBR%20%2F%3E%3CBR%20%2F%3EError%3A%20Package%20Information%3CBR%20%2F%3E%E2%80%A2%20Name%3A%20boot%3CBR%20%2F%3E%3CBR%20%2F%3EError%3A%20Errors%3CBR%20%2F%3E%E2%80%A2%20The%20specified%20file%20can%20not%20be%20imported.%20Make%20sure%20the%20file%20is%20not%20read%20only%20and%20you%20have%20read%20and%20write%20access%20to%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3040879%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3042757%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3042757%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20running%20my%20console%20on%20the%20primary%20site%20server%20so%20I%20think%20it%20has%20access.%20However%20to%20be%20sure%2C%20I%20have%20deployed%20an%20app%20package%20as%20suggested%20and%20obtained%20a%20cmd%20shell%20running%20as%20nt%20authority%5Csystem.%20This%20shell%20allowed%20me%20access%20to%20the%20folder%20containing%20the%20wim.%20attrib%20boot.wim%20does%20not%20show%20the%20file%20flagged%20as%20read%20only%20so%20I%20think%20its%20read%2Fwrite.%20The%20full%20path%20is%20E%3A%5CProgram%20Files%5CMicrosoft%20Configuration%20Manager%5COSD%5Cboot%5Cx64%5Cboot.wim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3042697%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3042697%22%20slang%3D%22en-US%22%3Eok%2C%20but%20does%20CM%20have%20access%20to%20the%20folder%3F%20aka%20the%20local%20system%20account%3F%20You%20can%20check%20access%20to%20it%20using%20the%20high%20level%20steps%20within%20this%20blog.%20%3CA%20href%3D%22https%3A%2F%2Fwww.recastsoftware.com%2Fresources%2Fhow-to-access-the-local-system-account%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.recastsoftware.com%2Fresources%2Fhow-to-access-the-local-system-account%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041541%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041541%22%20slang%3D%22en-US%22%3EI%20used%20the%20Domain%20Admin%20account%20which%20has%20Full%20control%20on%20the%20.wim%20file.%20I%20also%20copied%20the%20wim%20to%20another%20folder%20where%20I%20already%20had%20full%20permissions.%20Both%20gave%20same%20error.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041421%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041421%22%20slang%3D%22en-US%22%3EThe%20one%20listed%20within%20the%20error%20message%20above.%20%22Make%20sure%20the%20file%20is%20not%20read%20only%20and%20you%20have%20read%20and%20write%20access%20to%20it.%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041288%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041288%22%20slang%3D%22en-US%22%3EWhat%20solution%20are%20you%20referring%20too%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041281%22%20slang%3D%22en-US%22%3ERe%3A%20Accidently%20deleted%20boot%20images%20and%20cant%20get%20them%20back%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041281%22%20slang%3D%22en-US%22%3EDid%20you%20check%20the%20solution%20listed%3F%3C%2FLINGO-BODY%3E
Occasional Contributor

I deleted the boot images from my software library and cant find a way to recreate them. I've tried creating a windows PE boot.wim using the ADK and also importing from a location in the SCCM folder tree. Nether worked. Any advice greatly appreciated.

 

Error is

Error: Data Source Information
• Source location: \\STR-sc01\E$\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim
• Boot Image: 1 - Microsoft Windows PE (x64)

Error: Package Information
• Name: boot

Error: Errors
• The specified file can not be imported. Make sure the file is not read only and you have read and write access to it.

 

6 Replies
Did you check the solution listed?
What solution are you referring too
The one listed within the error message above. "Make sure the file is not read only and you have read and write access to it."
I used the Domain Admin account which has Full control on the .wim file. I also copied the wim to another folder where I already had full permissions. Both gave same error.
ok, but does CM have access to the folder? aka the local system account? You can check access to it using the high level steps within this blog. https://www.recastsoftware.com/resources/how-to-access-the-local-system-account/

I'm running my console on the primary site server so I think it has access. However to be sure, I have deployed an app package as suggested and obtained a cmd shell running as nt authority\system. This shell allowed me access to the folder containing the wim. attrib boot.wim does not show the file flagged as read only so I think its read/write. The full path is E:\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim