Monday, December 17, 2012 1:57 PM
well.. on all my windows 2012 server installs i always had device setup manager errors.. at first i didnt paied to it too much attention but after some installs i got bored of this and wanted to dig into it, especially when hyper v role is installed.
(This workaround works for domain and not domain joined hosts)
I think this is something Microsoft has to address..
I found that it happens whenever there's a creation of snapshots, so on a hyper host more frequently then on a win 2012 box without it.
whenever a snaphost is invoked doesnt' matter from what application, device setup manager involved in mounting it ask for its driver wich obviously comes from inside the box.
After a better understanding of what the problem was i wanted to dig into policies.. and here i got this 2 policies to workaround it..
local computer , turn off windows update device driver searching and specify search order for device driver source locations.
After disabling the first and enabling the second by choosing search windows update only if needed my errors gone away.
It sounds like windows 2012 has a problem with the driver in the box so with these policies after a first local search going to WU for the driver solves it.
Would like someone from Microsoft address better this.. Thanks
Hope it helps someone..
Monday, December 17, 2012 4:41 PMModerator
Could you please outline your steps so that someone from the MSFT side reproduce the issue?
Reading through your post, it seems that you are very familiar with your situation, however there is a lot of detail that is missing form the description that would be useful to the folks at MSFT in fully understanding your experience.
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.
Monday, December 17, 2012 4:56 PM
Of course.. :)
will try to sum it up, even with my bad english..
till now i did about 10, 2012 installation, all standard version, right after the first boot in most of them there were device setup manager error that even with the most recent updates got fixed.
I found them initially annoying not a real problem on normal 2012 server without hyper v role.. but on installations with the hyper role and since right because of the role errors increased i wanted to investigate.
So as i mentioned the error it is related to win 2012 gettin the driver when mounting a shadow copy volume.
to address this anyway even without the hyper role, its quite simple..
by enabling shadow copies on volume "c" for example and repeatedly creating them .. each shadow copies created generate one device setup manager by calling its driver.
i want to add something else, all my installations as been done on dell equipments, so i thought eventually this could be related to the inbox drivers created by dell and microsoft togheter before the 2012 official release.
by adjusting those two policies, no more errors since ofcourse they oblige device setup manager to look elsewhere for the driver and not just inside the server they lead DSM to search on Windows update after the local box.
I can suppose the shadow copy driver has a problem, but dont understand if it related to hardware dell for example or just itself.
do you think i should explain somethin more ?
let me know
Monday, December 17, 2012 9:37 PM
So are you saying that if you update the device drivers your problem disappears?
It is common practice (or should be) to always update to the latest drivers, either right after installation, or to slipstream them into the distribution. And, if you are having a strange problem, looking for a new device driver or BIOS update should be one of the first steps in troubleshooting to see your problem has a known fix. It is not uncommon at all for drivers that come with the Windows installation media to be out of date. Drivers come from the hardware vendors, not from Microsoft (except for Microsoft hardware like mouse and keyboard). In order to get drivers onto the distribution media, vendors need to submit their drivers to Microsoft a couple of months before the DVD is released. As a result, it often happens that there are changes to the drivers after they were submitted.
Monday, December 17, 2012 10:14 PM
its ten years i'm working full time on servers, i know what you mean..
i know my english is not so good but i thought i was clear..
i can repeat in few words.. i am not updating anything, all servers are fully update and many with an external wsus, its windows that inside takes a volsnap driver with may be something wrong in it... or dont know whatelse.. i just know that, as i explained, permitting device manager trough these policy to look for out of the box resolve the issue, so since this workaround works.. i assumed inside something is odd.
i dont understand at all from what this come from.. i just know what i had to do to fix it for the moment..
since i am installing windows server 2012 i think like everyone in the world.. and the error is there at the first boot, i connected the problem to an eventually Dell hardware incompatibility somewhere.. because if not.. i think many should have same error.