can't access System Volume Information
I cannot access the System Volume Information in order to delete the Sobig.B virus. Virus program does not remove it. I have changed the permissions for the user to allow for full access control but even after rebooting I cannot access the folder.
I used this command to make the changes:
cacls "driveletter:\System Volume Information" /E /G username:F
It is a XP Home edition with NTFS.
What can I do?
I used this command to make the changes:
cacls "driveletter:\System Volume Information" /E /G username:F
It is a XP Home edition with NTFS.
What can I do?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
war1
I've completed items 1-5. I've viewed the ms kb file but unless I've read it wrong there's only one way to make it accessible for XP Home NTFS. I ran through it all and that's where I'm stuck.
I'm logged in as the administrator but not in Safe Mode. How can I log in to Safe Mode?
thanks,
I've completed items 1-5. I've viewed the ms kb file but unless I've read it wrong there's only one way to make it accessible for XP Home NTFS. I ran through it all and that's where I'm stuck.
I'm logged in as the administrator but not in Safe Mode. How can I log in to Safe Mode?
thanks,
refer to: Windows XP Professional using the NTFS File System on a Workgroup or Standalone Computer
ASKER
when I right click on the folder, goto properties I don't see a security tab or an option to add a user. what have i done wrong?
Reinstall XP Home.
AWP,
Here's an easy way to start Windows XP in Safe Mode. Scroll down to Windows XP
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2001052409420406
Here's an easy way to start Windows XP in Safe Mode. Scroll down to Windows XP
http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2001052409420406
to get into safe mode, hold down CTRL or continiously tap F8 right before the starting windows screen appears. In the menu that appears choose safe mode.
***IMPORTANT NOTE: The steps suggested for XP Pro also works for Home Edition. But, you have to get into safe mode to try the procedure. ***
Uncheck simple file sharing and you will see the security tabs.
Uncheck simple file sharing and you will see the security tabs.
pls remember, in XP Home you have to go into safe mode to see the security tab
ASKER
that's the other thing - i'm accessing this machine remotely. If I boot into Safemode it won't be online and I won't be able to access it will I?
no
ASKER
ok, i'll walk someone through it on the phone. i'll let u know
Can't be done remotely.
check if you can do it with "Safe Mode with Networking". If not have the user do it locally.
ASKER
It still cannot access the internet in Safe Mode with Networking. They are mailing the laptop to me and I'll do this.
ok.
ASKER
I have now accessed the System Volume Information but cannot get out of Safe Mode.
ASKER
the unit wants me to turn the system restore back on to start normally, but will not let me turn it back on because i'm in safe mode.
could you post the exact error message you're getting?
ASKER
The FxSobigb.exe file from Symantec encountered an error while processing. It will not complete. This is in safe mode, as I cannot access normal mode.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Oops sorry Crash
:-)
ASKER
Crash - I'm in safe mode if that matters.
When I ran the sysedit - it said that config.sys couldnt open and neither could autoexec.bat
When I ran the sysedit - it said that config.sys couldnt open and neither could autoexec.bat
The only thing that would be pertinent in the autoexec.bat file is enviroment variables that are parsed by the OS and I doubt that this would causing the said problem. config.sys is not used in XP.
ASKER
I've checked to make sure it was applied.