W willhoy Well-known member Joined Feb 13, 2018 Posts 54 Apr 11, 2018 #1 We had to reboot a 2016 server today, and it is now in a Invalid Boot Device scenario. Ran an offline DISM and got the following. Attached is the DISM log and CBS folder. Any help would be greatly appreciated. CBS: CBS.zip - Google Drive View attachment dism.log
We had to reboot a 2016 server today, and it is now in a Invalid Boot Device scenario. Ran an offline DISM and got the following. Attached is the DISM log and CBS folder. Any help would be greatly appreciated. CBS: CBS.zip - Google Drive View attachment dism.log
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 May 3, 2018 #2 Hello and welcome! We are extremely sorry for the delay! Do you still require assistance?
W willhoy Well-known member Joined Feb 13, 2018 Posts 54 May 4, 2018 #3 softwaremaniac said: Hello and welcome! We are extremely sorry for the delay! Do you still require assistance? Click to expand... Negative. It turned out to be a problem we created ourselves. We changed the driver startup state in the reg for dattofltr.sys to assist in System State backups. Doing so caused the no-boot. Reversing it resolved our issue. Thanks though!
softwaremaniac said: Hello and welcome! We are extremely sorry for the delay! Do you still require assistance? Click to expand... Negative. It turned out to be a problem we created ourselves. We changed the driver startup state in the reg for dattofltr.sys to assist in System State backups. Doing so caused the no-boot. Reversing it resolved our issue. Thanks though!
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 May 4, 2018 #4 Glad to hear that! Take care.