Help
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
I have found a fully automated fix to correct both the Microsoft Windows AntiSpyware and Giant AntiSpyware 'Critical Error 101' which I will share with you at Grinler's request. I have tested it and retested it on my system numerous times.
It consists of a DOS batch which uses the pskill utility by Sysinternals to automate the killing of the process gcasServ.exe for XP home or Windows 2000 users. XP Pro users do not need to download pskill and may use the taskkill utility which comes with the XP Pro Operating system. See *Note below.
XP Pro users - use the line in the batch with taskkill and omit the pskill line in the batch
XP home or Windows 2000 users - use pskill and omit the taskkill line in the batch. You may download pskill from Sysinternals, which operates the same way as taskkill and unzip it to C:\Windows.
Directions:
1.) Copy the text in the quote box to a notepad text file.
2.) If you have XP Pro, omit the line in bold below from the text file which reads: "pskill gcasServ.exe", and proceed to step 4.
3.) If you have XP Home or Windows 2000, delete the line in bold which reads: "taskkill /F /IM gcasServ.exe" from the text file, and then save the file as in step 4.
4.) Save the file to your desktop as 101fix.bat, NOT 101fix.txt. (To do that, be sure to set the "save as type' to all files)
5. ) To run, Just double-click the 101fix.bat icon on your desktop whenever you get the critical 101 error. If you stiill experience problems, see the **Note below about using MSConfig (second paragraph), and that should fix it.
*Note - Warning: If you have Panda AV 2005, its real-time protection will erroneously detect pskill as a hacker tool (false positive) and immediately disinfect it. Therefore you should use the manual method of terminating gcasServ.exe in Task Manager in this case, prior to running 101fix.bat.
**Note - Important: In the process of trying to break Microsoft Antispyware/Giant to reproduce and test this error, I once ran into an instance where I still got the critical error 101 despite running 101fix.bat. If that happens, simply do this: Disable gcasServ.exe in MSConfig - selective startup, and then reboot. Then run the fix and you will be back to normal. To disable gcasServ.exe in MSConfig do this: Click Start-->run-->type in msconfig -->OK. Click startup and uncheck the process gcasServ.exe. Then reboot. Run the fix. Once the MS-AS/Giant Bullseye appears in the system tray icon, you make then go back and you can re-enable gcasServ.exe in MSConfig. I know MSConfig is not in Win 2000, so if anyone has that problem, you may may download WinPatrol to manage your startups.
For more info please refer to this post:
http://castlecops.com/t120958-NEW_ERROR_10..._5_15_2005.html
It consists of a DOS batch which uses the pskill utility by Sysinternals to automate the killing of the process gcasServ.exe for XP home or Windows 2000 users. XP Pro users do not need to download pskill and may use the taskkill utility which comes with the XP Pro Operating system. See *Note below.
XP Pro users - use the line in the batch with taskkill and omit the pskill line in the batch
XP home or Windows 2000 users - use pskill and omit the taskkill line in the batch. You may download pskill from Sysinternals, which operates the same way as taskkill and unzip it to C:\Windows.
Directions:
1.) Copy the text in the quote box to a notepad text file.
2.) If you have XP Pro, omit the line in bold below from the text file which reads: "pskill gcasServ.exe", and proceed to step 4.
3.) If you have XP Home or Windows 2000, delete the line in bold which reads: "taskkill /F /IM gcasServ.exe" from the text file, and then save the file as in step 4.
4.) Save the file to your desktop as 101fix.bat, NOT 101fix.txt. (To do that, be sure to set the "save as type' to all files)
5. ) To run, Just double-click the 101fix.bat icon on your desktop whenever you get the critical 101 error. If you stiill experience problems, see the **Note below about using MSConfig (second paragraph), and that should fix it.
Quote
Net start DcomLaunch
sc config DcomLaunch start= auto
cd \
IF EXIST C:\Program Files\Microsoft Antispyware\ .(
cd C:\Program Files\Microsoft Antispyware\ .
) ELSE (
cd C:\Program Files\GIANT Company Software\GIANT AntiSpyware\.
)
REM use the following line if you have XP Home or Win 2000 and have downloaded pskill
pskill gcasServ.exe
REM XP Pro users use the following line - no need to download pskill
taskkill /F /IM gcasServ.exe
gcasDTserv.exe -Embedding
gcasServ.exe
GiantAntiSpywareMain.exe
exit
sc config DcomLaunch start= auto
cd \
IF EXIST C:\Program Files\Microsoft Antispyware\ .(
cd C:\Program Files\Microsoft Antispyware\ .
) ELSE (
cd C:\Program Files\GIANT Company Software\GIANT AntiSpyware\.
)
REM use the following line if you have XP Home or Win 2000 and have downloaded pskill
pskill gcasServ.exe
REM XP Pro users use the following line - no need to download pskill
taskkill /F /IM gcasServ.exe
gcasDTserv.exe -Embedding
gcasServ.exe
GiantAntiSpywareMain.exe
exit
*Note - Warning: If you have Panda AV 2005, its real-time protection will erroneously detect pskill as a hacker tool (false positive) and immediately disinfect it. Therefore you should use the manual method of terminating gcasServ.exe in Task Manager in this case, prior to running 101fix.bat.
**Note - Important: In the process of trying to break Microsoft Antispyware/Giant to reproduce and test this error, I once ran into an instance where I still got the critical error 101 despite running 101fix.bat. If that happens, simply do this: Disable gcasServ.exe in MSConfig - selective startup, and then reboot. Then run the fix and you will be back to normal. To disable gcasServ.exe in MSConfig do this: Click Start-->run-->type in msconfig -->OK. Click startup and uncheck the process gcasServ.exe. Then reboot. Run the fix. Once the MS-AS/Giant Bullseye appears in the system tray icon, you make then go back and you can re-enable gcasServ.exe in MSConfig. I know MSConfig is not in Win 2000, so if anyone has that problem, you may may download WinPatrol to manage your startups.
For more info please refer to this post:
http://castlecops.com/t120958-NEW_ERROR_10..._5_15_2005.html
This post has been edited by negster22: 27 August 2005 - 07:46 PM
Back to top
