General discussion

"Safely Remove" internal C: drive?

I re-installed Windows XP Home on my desktop computer yesterday. The install went fine except that the "Safely Remove Hardware" icon is ever present in the doc, showing my internal SATA C: drive!

Why is this and how can I correct it?

Discussion is locked

Reply to: "Safely Remove" internal C: drive?
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: "Safely Remove" internal C: drive?
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Such happens. For no known reason.

Just don't look at it. It will refuse to work anyway.
Might be better in Windows 7, but I doubt if it's a good idea to spend USD 200 for this reason only.


- Collapse -
That's well known for SATA drives.

XP is an older OS that has this issue. No plans to fix it.

Since it doesn't stop us from using the OS, why would it get fixed?

- Collapse -

I wasn't expecting Microsoft to fix it. Happy But since the original install on the same hardware did not have this problem, I assume there is a fix.

- Collapse -
There may be a workaround.

But given it works without any workaround and we can hide that item without any effort there has been little need to fix it.

Example? There are folk that can't stand any warnings in the Event Viewer. I see them spend months tracking them down rather than using the machine. Different goals I fear.

Yes you can research how to hide items like this but it is not a bug that is fatal or creates any issue worth fixing.

CNET Forums

Forum Info