HP Support Forums
Join in the conversation.
Hi Mark,
The Drive Letter change was suggested as a means of eliminating that error. I am not sure whether it would work... as mentioned earlier, changing the Drive Letter for one of the connected devices did work in one case - not in another.
You'd know if you bought your computer with a second disk... It would be a second "data" disk - not the "Recovery" partition, not the "HP_Tools" partition - a real second disk of it's own that shows up in Computer. No worries.
I have not seen this "HDR1" error on any of my systems and only just started reading about it. I suspect that you've stumbled on a program bug and now it's buried in the registry. I think that is why in some cases the change to the Drive Letter works and in others it does not - it depends, for one thing, what this "IS" - and it depends on where the actual registry error is located. I do not understand Windows registries, but I do understand programming. One can sometimes fix or break things by doing something that appears totally unrelated.
This could be some sort of Infection. What I have read suggests this is not the case. I have read very little of what is out there. See my note about Norton... Then know this - just because I don't like Norton, does not mean I think it failed. I do not think at this point that your computer is infected.
I think reinstalling the OS would fix it. I am just not sure the fix would "stick". I do not know where the issue originated - so whatever you did to cause it in the first place could be repeated (not deliberately, of course) - Poof! The error could return. Not to say, you won't end up reinstalling ... It makes sense to try other "less painful" options first.
Commentary:
I am not directly familiar with Western Digital backup tools... I've read the usual. I have one of the HP 1T backup boxes - I do not uses the HP software; the box just sits connected USB 3.0 as a auxiliary disk: I use it with SyncToy 2.1 for daily backups. The HP box has been reliable so far (about eight months). We use a Synology NAS Server for network backups that we like very well. I use Cobian Backup 10 for the Windows systems to talk to that one. Not fancy, but it is fast enough, free, really easy to use, reliable, and it emails me log files. What more can one ask?
I am not a fan of Norton. I do not have Norton on any of the several computers in my Home Office. I cannot comment on its use.
--------------------------------------------------
EDIT ... 5/7 11:19 p.m.
Option 1:
"Go Back in Time"
You didn't say how long this has been going on... If the error is relatively new, that is, it has not been around for a long time, it might make sense to see if you can get rid of it by going back to a time when you did not see it on the computer - stepping back, so to speak.
Using "System Restore" can take your computer back to any point at which a restore point was created. Restore points are created by the system when updates are added, when programs are installed or changed, and when "Restore Points" are scheduled by the user(s) of the computer. Only the computer's programs and data are affected by a System Restore; the user's personal data and files are not changed.
Restoring Windows to a Previous Point (Windows 7) – HP and Compaq Computers
For Vista:
Using Microsoft System Restore – Notebooks – Vista and Windows 7
If you do not have System Restore enabled... Oh, well, no time like the present to get it set up for next time. 
end of edit...
==================================================
Option 2:
IF this error can be cured by changing the Drive letter on, say, the Western Digital connection, then that is a place to start.
Option 2:
IF this "bug" insinuated itself into the registry entries of just two of the programs of your system, then you might cure it by reinstalling those two programs.
Option 3:
IF this "whatever it is" is a general registry error, then you MIGHT be able to dig it out with a Registry Cleaner. I used to be more of an advocate of registry cleaners than I am at present. I have had limited success with cleaners - it seems that the more desparate your need, the less likely they are to succeed. 
Nonetheless, I will give you the link of a cleaner that I trust to work as well as any and the one that I believe will not damage your computer.
Tools List:
Registry Cleaner – CCleaner (Download the free version):
http://www.piriform.com/ccleaner/download
NOTE about using CCleaner: IF you use the Applications cleaner tab in CCleaner (this is a separate section from the registry cleaner), be sure to check/uncheck the program list or CCleaner might remove things you may want to keep.
NOTES on Registry Cleaners:
Registry cleaners will usually do no harm – however, anytime you affect the registry with changes, you risk your system’s stability. CCleaner does include the offer to make a backup of your registry prior to making any changes.
If you select to download and install another registry cleaner, please uninstall CCleaner. One of these things on the system at a time is enough…
If a registry Cleaner does not offer to do a backup prior to making changes: be sure you EXPORT the registry manually PRIOR to using the cleaner. If anything happens that you don’t expect, you will have an extra layer of protection on which to fall back.
IMO: Stay away from Registry Mechanic. I have had this on my systems – it has been cleansed, removed, deleted, and dropped in the Zeros bucket. This is a Personal Opinion.
--------------------------------------------------
I hope this helps!
--------------------------------------------------
When you appreciate the Help you receive…
Please Click the Kudos Star on the Left to say "Thank You"!
Is it Solved? Make it easier for other people to find the Answer:
Please Mark my Post “Accept as Solution” to say "Yes!"
Remember: The more information you provide, the better help you receive.
Always Include: (Computer) Product Number , Printer – Model Number ,
Operating System and an Error Description
Never give out your Serial Number
--------------------------------------------------
2012 Year of the Dragon!
