Re: System Drive Renaming Issue

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I understand

but you can never trust users to follow orders - espically after 2 months

Thanks

Bob erdmann


"James wood" wrote:

> We haven't installed anything additional since the update rollup, so all our
> services were still pointing to C:. The MS article states that you should not
> uninstall or install anything if you experience the issue. Of course the
> article came out 2 months after the Update Rollup.
>
> We did learn one thing. If you don't change the drive letter back to C: (or
> System drive), before the reboot, then the last drive letter stays. At that
> point, a lot of third party services don't start.
>
> "Bob Erdmann" wrote:
>
> > Worked great
> > Found an 5.0.2.2195.6661 version file and had only a few problems.
> >
> > Myself - I would add two more steps to the fix.
> >
> > After the reboot - add run regedit and search and replace all drive letters
> > that are wrong. In my case I had to replace @50 entries of F:\ path with C:\
> > path.
> > Then add reboot again
> >
> > This corrected a few event viewer errors
> >
> > Thanks
> >
> > Bob Erdmann
> >
> > "James wood" wrote:
> >
> > > We have had this same issue. Here is a work around that we have found
> > >
> > > 1) Rename c:\winnt\system32\dllcache\mountmgr.sys to mountmgr.old
> > > 2) Copy the file mountmgr.sys from SP4 to c:\winnt\system32\dllcache.
> > > 3) Rename c:\winnt\system32\drivers\mountmgr.sys to mountmgr.old
> > > 4) Check Computer Manager --> Disk Management.
> > > a. If the System Drive is C: then just reboot.
> > > b. if the System Drive is another letter then follow the steps is MS KB
> > > 223188. Then reboot.
> > >
> > > Caution if you have installed the patch KB835732 outline in MS alert
> > > MS04-011, you may experience a BSOD.
> > >
> > > Make sure to use the mountmgr.sys version 5.0.2.2195.6661.
> > > The version 5.0.2195.6897 causes the BSOD.
> > >
> > > Hope this helps.
> > >
.

Quantcast