Yep, that's what I'd expect too.  So for that reason I'm surprised last known good didn't fix your problem. 
You might try booting to recovery console and disabling all of the related services; that might be helpful as well. However, it's really up to the vendor in a situation like this - I'd ask them what, exactly, disabling the device in DM does in the registry - once you've got that, you can easily fix this now.
			
			You might try booting to recovery console and disabling all of the related services; that might be helpful as well. However, it's really up to the vendor in a situation like this - I'd ask them what, exactly, disabling the device in DM does in the registry - once you've got that, you can easily fix this now.
 
				
		 
			 
 
		 
 
		 
 
		 
 
		
 Facebook
Facebook Twitter
Twitter