see if this can help:
http://www.microsoft-discu
Main Topics
Browse All TopicsDoes it hurt to remove the Everyone group from both the share and NTFS permissions if you were to share the entire C drive? I did that the other day on an XP Pro machine and rebooted it a couple of times fine but now it wont boot. It gets a blue screen message that says:
autochk c000021a fatal system error. The session manager intitialization system process terminated unexpectedly with a status of, 00xc000003a
I was wondering if it was related. There was 1 piece of software installe afterwards as well and wonder if that could be it too.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
see if this can help:
http://www.microsoft-discu
Have you attempted to boot into safe mode? or can you not get that far?
If you can boot to safe- log in as administrator ( if you don't remember your admin password try just hitting enter- blank password). If you can get that far you should be able to add your everyone group back in and geive it at least read/execute/list permissions.
Also make sure that administrator as full control.
Even though I removed the everyone group I made sure his user acct which has admin rights has full control for the share and NTFS permissions. I guess my question is whether or not it is a good idea to remove the everyone group at all. He wanted to make sure nobody could access his shared drives except from him so I removed everyone except for him and the system account. Im wondering if thats what caused it since I rebooted a couple of times fine before this happened.
He said when he tried safe mode it just kept scrolling the lines of text as its loading and said it wouldnt stop but I think it did stop and he just thought it was still going. Im trying to find out where it stopped at.
Is there a command I can run from the recovery console to put the everyone group back? Will it matter that the administrator acct is removed from the share when trying to do this or when it asks for the admin password at the start of the recovery console?
TSI-WLV,
You can check out the links below for more info on Recovery Console.
But to your original question - I have had to re-read it a couple of times. I do not believe removing the everyone group can be held responsible for that errror. Did you uninstall any other programs or make any other config changes in between reboots.
Recovery Console Links:
http://www.microsoft.com/r
http://commandwindows.com/
Authenticated Users must be users of the System - you make it have the same properties as Everyone and replace everyone with it.
If someone doesn't authenicate when loging in they are not granted permissions. This is the recomend way of securing XP-
You can find a process on MS site - if you need to or just google it.
So you will be removing Norton System works -first- I would suppose, then test, if your problem is gone you're cool. Re-install Norton with minimum services and test again before turning anything else on.
in fact you can use the security templates to harden you machine.
by import the proper INF file from c:\windows\security\templa
any way this How to reset security settings back to the defaults:
http://support.microsoft.c
Answering just to the question:
NO, removing "everyone" from permissions for entire disk, does not hurt.
EXCEPT if system is already setup with simple security, and programs and services disregard the need for administrative rights. So the safest way to remove Everyone from permissions, is at fresh install.
NOTE: Removing Everyone is NOT the same as giving Everyone DENY rights! Don't even try denying Everyone!
First of all, it is REALLY BAD to share your C drive. dont do it. (Besides, windows already does it with a share called C$.) Second, if you are sharing, you should create a group of users to access the shared folder.
Third, to fix your permission problem, I would suggest you look into a disk I use called "The ultimate boot disk." It is a bootable copy of linux that will enable you to modify NTFS permissions.
Fourth, Norton Systemworks is worthless.... I have never seen a computer actually get fixed with this program, but I have seen quite a few blue-screen from installing it.
Good luck, hope this helps.
Business Accounts
Answer for Membership
by: ibu1Posted on 2007-01-07 at 23:01:33ID: 18265147
Note the following approcah will not replace any system files.
* C:\WINNT\system32\config\* .*
Can you boot to your Win XP cd? If so then when it finally boots to the CD choose "Repair Console" this will allow you to use the command line. From here do something like this. Or if the file system is FAT32 you can use a Win98 bootdisk to do this. www.bootdisk.com
COPY /Y C:\WINNT\repair\RegBack\*.
This will replace the registry to the last time the registry was backuped. Hopefully you didn't backup the registry at the time the problems started to happen.
Also if you desire not to copy over the entire registry you can do it one hive at a time. Following is a list of the files that are the registry hives. I would suggest starting with the System hive and then reboot and if the problem still persists do the Software hive next. Note these files don't have a file extension on them
DEFAULT
SAM
SECURITY
SOFTWARE
SYSTEM
I would suggest to first backup these hives from the C:\WINNT\system32\config\ to folder of your making
or choice just don't back them up to the C:\WINNT\repair\RegBack\ folder.
You will probably need to reapply any services patches that you have previously installed.