Quote:
|
Originally Posted by Alain-James
Well Secur32 can't be ended the same way as everything else, because it is specifically the process which manages ctrl-alt-suppr related processes 
I may check in the activable processes if one can check it off, but I'd prefer not. It's really a vital aspect of the OS. But ultimately I may have to come to your solution Danlisa if the Secur32 version is a non-issue 
Thanks in advance Seafarer  |
Secur32 is a dll, not an executable... It can't be exited or disabled because it isn't a complete program that runs in its own process, its a library that is loaded by pretty much every process. It is a core part of the OS, and it provides most of the security & user account functions in windows.
Just because this is where the crash occoured, doesn't necessarly mean this module caused the problem. For example, sh3 might have called secur32 with bad parameters, so the module threw an exception. The module that called secur32 process should caught that exception, and dealt with it somehow.
In this case there was nothing to handle the exception so windows had no choice but to kill the process.
The version you have listed (6.0.6000) is the version number of all of the DLLs in stock windows vista. I have v6.0.6001, which is vista SP1.
Because this DLL is used pretty much everywhere its not necessarily a starforce issue either (but it might be).
Quote:
|
Originally Posted by ICZEOZN
I use an administrator user account, but I believe the "Run as administrator" command is superior. I may be wrong, but I believe Vista has both an "administrator" account and an "Administrator" (with a capital "a") account.
I suppose you could give that a try. When I did that, I think the update was already installed and I had just installed it again with the "Run as administrator
|
There is still only one administrator account, but what happens is with UAC on vista if you are an administrator it doesn't give you all of the administror privildeges initially. Your logon has the same rights as a non-admin user account. If you right-click on a program and select "run as administrator" then it runs the program with full administrator priviledges.
Some other stuff happens with file & registry virtualisation which means stuff that writes to restriceted areas of the registry and filesystem looks like it works, but doesn't really. This is what causes most problems for people with updates not getting applied etc. (I have turned this off)
If you use "run as administrator" to run a program the filesystem and registry writes aren't virtualised, and go to the real thing.
To make sure SH3 is sorted out, find SH3 and "run as administrator". This will ensure starforce gets a chance to install properly. Then run the starforce update with "run as administrator" to let it sort its thing out... then try SH3 again. If that fails, try SH3, with "run as administrator".
If it still doesn't work at least we know most likely it isn't starforce causing the problem.
I have been running SH3 on vista for 12 months now, and I have had zero problems. I have avoided the whole starforce problem... (shh...)
Hope this helps.