Well, we definitely have shot ourselves in the foot. I'll try to pull those drivers from the boot image.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Thursday, July 20, 2017 6:49 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: Error updating boot image The driver may or may not be old. The problem is that driver injection into boot images comes from the original location that you imported the drivers from and **not** the package source location. Many folks mistakenly delete the files they originally imported the drivers from thinking that they are no longer needed and thus essentially shoot themselves in the foot. You only recourse here is to restore the drivers exactly as they were in the locations noted or to remove the drivers from the boot image. J From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray Sent: Thursday, July 20, 2017 7:03 PM To: mssms@lists.myitforum.com <mailto:mssms@lists.myitforum.com> Subject: [mssms] Error updating boot image CM2012 R2 SP1 CU4. When I try to import drivers and update the boot image, I get this error: I tried attaching the dism.log file, but it's too large. I believe the relevant stuff is below. It looks to me like it's trying to find an old driver that no longer exists on the server. Not sure what I can do about this, but I need to update my boot image. Help! Best Regards, Mike Murray Desktop Engineer/IT Consultant - IT Support Services California State University, Chico 530.898.4357 <mailto:mmur...@csuchico.edu> mmur...@csuchico.edu Remember, Chico State will NEVER ask you for your password via email! For more information about recognizing phishing scam emails go to: http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml
smime.p7s
Description: S/MIME cryptographic signature
