joengelhart Posted December 24, 2014 Report post Posted December 24, 2014 Hello, I have a weird problem that keeps happening each month after I run the Scheduled updates on my image and try to image something I'm getting: "Windows failed to start"..... File "vmstorfl.sys" Status: 0xc0000098. (see attached picture) I have been having to install my image on a computer run windows updates and then recapture the image because I cannot get it to update in SCCM without this happening. This is the second month I have tried to update my image and this happens. If anyone has an idea how I can fix this it would be much appreciated. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted December 25, 2014 Report post Posted December 25, 2014 are you following the guide I wrote ? http://www.windows-noob.com/forums/index.php?/topic/4683-using-sccm-2012-rc-in-a-lab-part-12-updating-an-operating-system-image-using-offline-servicing/ Quote Share this post Link to post Share on other sites More sharing options...
joengelhart Posted December 26, 2014 Report post Posted December 26, 2014 Hi Thanks for getting back to me. I have followed those instructions exactly. Once I get everything going and try to image a computer, on first boot this is what comes up. Any ideas? Quote Share this post Link to post Share on other sites More sharing options...
giftedwon Posted December 30, 2014 Report post Posted December 30, 2014 first would be to check out OfflineServicingMgr.log on the server. then you can drill down from there Quote Share this post Link to post Share on other sites More sharing options...
joengelhart Posted January 5, 2015 Report post Posted January 5, 2015 I have checked the log but it all looks normal. No errors or anything Quote Share this post Link to post Share on other sites More sharing options...
AaronBISSELL Posted January 9, 2015 Report post Posted January 9, 2015 I had something similar happen after using the Scheduled Updates on my image - as well when I mounted the image via PowerShell to install and enable .NET 3.0 and 3.5 on our W8.1 image. I was able to resolve it by redistributing the Tools pack as well as the Settings pack. My poking around lead me to believe it was something with the unattend.xml file. After redistributing those tool packs, the image behaved as expected. Still not entirely sure why. Quote Share this post Link to post Share on other sites More sharing options...
joengelhart Posted January 27, 2015 Report post Posted January 27, 2015 I had something similar happen after using the Scheduled Updates on my image - as well when I mounted the image via PowerShell to install and enable .NET 3.0 and 3.5 on our W8.1 image. I was able to resolve it by redistributing the Tools pack as well as the Settings pack. My poking around lead me to believe it was something with the unattend.xml file. After redistributing those tool packs, the image behaved as expected. Still not entirely sure why. Could you explain how you did this?? I would love to stop having to pull down my images each time to patch. I'm using a windows 7 image Quote Share this post Link to post Share on other sites More sharing options...
