Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Generic User Avatar

Disabling Driver Verification is the only way to start the server


  • Please log in to reply
1 reply to this topic

#1 TaintedDemonWolf

TaintedDemonWolf

  •  Avatar image
  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:36 AM

Posted 25 January 2024 - 04:23 AM

We have recently taken on a new client. I got access to their server running multiple Hyper-V virtual machines.

One server in particular is having an issue where it does not start up after reboot/shutdown until I log in and "Disable Driver Verification" with the F8 menu.

OS: Windows Server 2016 1607 (Build 14393.2248)

I have tried online and offline SFC and DISM fixes, both eventually came back clean but I was still having the issue.

I did some digging and came across the "sigverif.exe" as part of Windows as this checks if the files are digitally signed. So I ran that and it came back with 5 files as having an issue. All in C:\Windows\System32\Drivers and all have modified dates in Jan 2018.

File - Version
cdrom.sys - none
hidclass.sys - none
hidparse.sys - none

intelppm.sys - none

netvsc.sys - 10.0.14393.2007

So I am guessing I need to replace these files with properly signed ones in the correct version? Hopefully this solves my problem... But I need to find out where to get the files as a starting point. Or am I just chasing ghosts in solving the problem.

Attached Files



BC AdBot (Login to Remove)

 


#2 Shplad

Shplad

  •  Avatar image
  • Members
  • 6,554 posts
  • ONLINE
  •  
  • Gender:Not Telling
  • Location:Canada
  • Local time:01:36 AM

Posted 03 April 2024 - 06:24 PM

Are there any updates to this case?

 

I can tell you that sometimes Windows uses older system/driver files. I don't know why. I do know that sometimes newer "drivers" are just older drivers with later date signatures on them. This is a known fact.

 

You haven't stated the bare minimum required information here, which is Windows build/version.

 

Also, when was the last time Windows Update was run on the machine in question?


- Use this to collect and post information about your PC hardware, software and configuration (Whether or not you have crashing).

 

Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista

https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

 





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users