Juan said:
VanguardLH has written on 7/20/2013 4:40 AM:
Why would I want to turn off System Restore?
Because you're fearful of mount points that aren't currently active.
Current 1
Default 1
Failed 0
LastKnownGood 2
Under HKLM\SYSTEM, I have ControlSet001, ControlSet002 and
CurrentControlSet.
So CurrentControlSet = CurrentControl001. No point in search in both
subkeys since they'll have the same settings (i.e., you'll see doubled
settings in 2 keys but they are both the same).
Then why did they supply the triple stars? Certainly, they were meant to
get attention?
Wouldn't matter if there were no stars and even if in lowercase. You
seeing "no mount points" would've still triggered your inquiry as it
would look, to you, like something was amiss.
Besides, maybe you were having a problem, like USB-attached drives
that don't properly issue their presentation data or it is non-unique
which results in enumeration problems in the registry (Enum key). It
is something you might want to look at. Most times not. If there had
been a problem then running mountvol might've been a troubleshooting
step; else, why did you run that command? If you're going to play
around with the mountvol command, it's possible you create a
definition that you forgot to remove later.
You could backup your registry (export it, for example) and use
mountvol to remove those definitions. Then see if something doesn't
run correctly; however, it could be days, weeks, or months before
those registry entries were needed again. For enumeration, and if the
device issue valid and complete presentation data for enumeration, it
would simply get reentered and you wouldn't have a problem later.
I've already mentioned what my "no mount points" definition pointed
to, and obviously it wasn't a critical problem or even one needing to
be addressed. Now it's up to you to figure it out (since what you've
offered is too little data to determine what's defined in your
registry for those class GUIDs).
http://en.wikipedia.org/wiki/NTFS_volume_mount_point
Possible some of your mount points are junction points, something more
used since Vista.
http://technet.microsoft.com/en-us/library/cc753321.aspx
http://technet.microsoft.com/en-us/library/cc938934.aspx
Junctions have been around since probably Windows 2000. Just because
Microsoft didn't include any enduser tools to manage them didn't
obviate the feature from NTFS. You might have junction points defined
by some software you installed. For example, I create "References"
junction point in My Documents to point a C:\References so I can see
my ref docs under my docs without having to know where they are
actually located, and can do the same in every user profile's My Docs
so all users would be sharing the same ref docs folder.
http://windowsitpro.com/systems-management/using-mount-points-imy-documentsi
There are lots of reasons to create mount points. You saw someone
else ask about them, took up and waved their banner, but the cause is
not yours (i.e., you're not having real problems, just imagined ones).
Since you decided to take up someone else's question of:
Can I safely remove these from the registry?
Yes, they can be safely removed *if* you know what they are for and
are willing to track all the dependencies in the registry to get as
much a complete picture of their definitions as possible, or you're
willing to risk later problems but backed up those entries to restore
them later if needed.
Remove them if you want. See what happens, if anything (that you
notice since re-enumeration will be hidden to you for re-inserted USB
devices). If they are mount points used for redirection in folders,
well, it's still safe to delete the mount points but then you lose the
redirection (but not the target folder and files).
