Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog

If You Have Windows Bootup Issues After Installing SVS Agent

Created: 12 Aug 2008 • Updated: 29 Jul 2010 • 10 comments
Tenacious Geo's picture
0 0 Votes
Login to vote

After we deployed the SVS Agent to all of our computers, there were a handful of computers that got stuck in a reboot loop. Ouch! We knew the issue started after the SVS Agent was installed, so we wanted to uninstall it. However, we could only get into Windows Safe Mode and were unable to uninstall from there.

After doing some digging, I found that there can be issues with the SVS filter driver during startup if it conflicts with another application (like certain versions of Symantec AntiVirus) or if it is a Windows 2000 computer that already has software that load filter drivers during bootup.

I ran across an Altiris Knowledgebase article 43245 that referenced the path to the SVS filter driver in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FSLX\ImagePath

The ImagePath is usually set to:

\??\C:\WINDOWS\system32\drivers\fslx.sys

(C:\WINDOWS for XP or C:\WINNT for Windows 2000)

My idea to recover these computers from the reboot cycle was to change the ImagePath in the registry in Safe Mode to something that isn't the correct path to fslx.sys. It worked! This allowed us to get back into Windows normally and work on troubleshooting the bootup conflict caused by the SVS Agent.

Comments 10 CommentsJump to latest comment

erikw's picture

We noticed some computers that are also rebooting in a loop after SVS install. This behaviour was caused because SVS placed the driver not only in c:\windows\system32\drivers, but also in c:\windows\system32.
Try it yourselve.
Place fslx.sys in c:\windows\system32, and you will notice that the machine wil loop again.

Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+1
Login to vote
Tenacious Geo's picture

So you're saying that if fslx.sys is only in system32 it won't have reboot issues? I wasn't clear from your post.

-Geo

-3
Login to vote
Scott Jones's picture

Our standard approach for getting a machine back up when SVS is causing a boot problem (of whatever nature) is to rename fslx.sys (in [WINDIR]\System32\drivers). Easier, quicker, and you're less likely to make a mistake.

Scott Jones
Technical Product Manager
Symantec Endpoint Virtualization

Scott Jones
Business Critical Engineer, Endpoint Virtualization
Symantec Corporation
www.symantec.com
 

-4
Login to vote
Tenacious Geo's picture

Scott what have you found as the causes for reboot conflicts and how were you able to remedy the conflict?

-Geo

+1
Login to vote
Ed_Garza's picture

I had a laptop that was in a reboot loop after the SVS agent install.

After logging into the machine and deleting all the references to Altiris so that CSA would trust the Altiris installation it resolved out issue.

-1
Login to vote
Seth's picture

We have had the SVS client on all machines for some time. Our systems did not start this(BSOD Loop) until our Symantec Endpoint updated itself the night of the August 11th. We have Symantec working on this. Two ways we used to stop this: 1. Uninstall SVS in safe-mode. 2. Stop/Disable the Symantec Endpoint service in safe-mode. Will update here when i hear from symantec.

+1
Login to vote
Jordan's picture

Seth, and other experencing this problem, please see this post about how to work around the problem.

The actual solution is to upgrade SVS (it's only real old versions of SVS having this problem) but you might need to follow these steps to get out of the BSOD loop.

If a forum post solves your problem please flag is as the solution

-2
Login to vote
Tenacious Geo's picture

I'm not sure that the latest SVS version is the fix, because we are running SVS 2.1.2095 and still see a conflict with Symantec AntiVirus 10.1.5.

-Geo

-5
Login to vote
Jordan's picture

Did you re-boot?

Also we'll have a KB article up with more info, we're seeing sketchy results from the program ignore list but so far no issues with any version of SVS after 2.1.2032

If a forum post solves your problem please flag is as the solution

-3
Login to vote
mgarza896's picture

We also had this problem. Booting into safe mode and renaming the file fixed the BSOD issue. We then installed the latest version 2.1.2088. The version we had issues with was 2.0.1403.

-1
Login to vote