Unexpected failure. Error code: 490@01010004 this occurs in both win 7/vista 32/x64 whenever you click on diskmanagement in computer management. you think the brilliant over paid coders at microsoft would have fixed this by now but nah. the error itself seems to be harmless but would you to think they would check the event logs after testing the OS for a week or 2 to see if any errors get spit out? guess not.

Yep, your right, thanks.

Hello, Today I noticed the same error (vds basic provider error code: 490@01010004) on one of our hyper-V guest server (Windows Server 2008 R2). The server has been logging this error 10 or more times a day since 1st of June 2010! I searched the Internet and found this KB:http://support.microsoft.com/kb/979391. So acording to Microsoft"this event can be safely ignored"! Whenever I open the Event Log all I see is this error logged thousand times. That's why I don't find ignoring the error a very wise resolution. At least according to Microsoft it do not indicate any problem. Daniella Slavcheva

Totally agree with you Daniella. If it is so benign you'd think Microsoft would release a hotfix to prevent it from being logged, after all Error alerts are supposed to be there to give us a heads up that there is a problem that needs sorting! Let's hope SP1 gives us some respite.Darren

The virtual Disk Service is looking for the location path property of the disk controller. Physical hardware disk controllers have this property, and so won't generate this error, but a virtual software disk controller (such as those used in Hyper-V guest environments) does not have this property for the Virtual Disk Service to find. That is what generates this error. I agree with Microsoft on this one. This event can be safely ignored.

Jason, then that virtual disk subsystem needs a little redesign / revision, doesn't. The single most important piece of IT equipment is the server harddrives. Having this error happen on a mission critical server numerous times per day is not acceptable because every last instance has to be investigated - that costs money. Funny thing is, our free Linux servers have had built in loopback devices and other ways to mount ISOs that do not emit superfluous errors.

I'm with jts69, and other posters, on this one. Event ID's have to be examined, and having superfluous events logged which are known to be 'harmless' represents lazy and careless development, not to mention utter hypocrisy in regards to MS own published Best Practices. FAIL.

Frustrating error, and "May Safely Ignore" is rather a lame response from MS. I also find it annoying when researching an error to get their generic "EventID not found" page. But that being said, I may have found a work-a-round that will work after many different failed attempts to eliminate the error from my logging. Change your Virtual Disk Servce from Manual to Automatic. Since this event error only occurs at boot-up, I assumed it wasn't loading quick enough to prevent an event error in the log. I made this change about 10 start-ups ago, and since changing the service to Automatic, the error has not reoccurred. I don't know if this will work for the group, but it seems to be an adequate work-a-round for me. (Thus far) Go to: ADMINISTRATIVE TOOLS>SERVICES>VIRTUAL DISK---> Change from manual to automatic Hope this works for ya all. Cheers!