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

Exclude problems in SWV 7.5 SP1 HF1, including BSOD

Created: 13 Jul 2014 • Updated: 07 Aug 2014

Checking to see if anyone from Symantec is reading the forums.  I posted this problem nearly a month ago and have heard nothing.  I will add that in addition to the problems I originally reported, I've also found that removable drives I'm using are not auto-excluded.  I also use TrueCrypt to mount an encrypted container as 'S:' ... I cannot exclude this globally as I could with version 6 because it normally isn't mounted and a global exclude will result in a blue screen. 

Bottom line is 7.5 SP1 HF1 (7.5.760) has several serious issues with exclustions (layer and global).  The following is the original post before I made the above discoveries.

 

There are two problems resulting from the fact that the code responsible for adding layer and global exclude entries via the layer properties window do not check whether the specified path exists before adding the exclude.  This causes the following problems:
  . BSOD (STOP: 0x000000D3 in fslx.sys) when the path for a global exclude is invalid.
  . Improper processing of excludes when the path for a layer exclude is invalid

The following give the steps for reproducing the two problems:

1) BSOD when entering a global exclude for a path that is not present.
   . Deactivate a layer
   . Edit the layer
   . Select the "Exclude entries" tab in the Layer Properties window
   . Right click on the lower pane (the Global excludes pane)
   . Click 'New exclude entry'
   . Select 'Folder', enter any non-existing path using (eg, 'W:\' if it doesn't exist), check 'Exclude folders')
   . Click 'OK'
   . Reboot
   There will be BSOD upon reboot (STOP: 0x000000D3 in fslx.sys)

2) Improper handling of layer excludes in specific circumstances
   To reproduce this problem, create a layer for Notepad++, then:
   . Deactivate the layer
   . Edit the layer
   . Select the "Exclude entries" tab in the Layer Properties window
   . Right click on the upper pane (the layer excludes pane)
   . Click 'New exclude entry'
   . Select 'Folder', enter any non-existing path (eg, 'W:\' if it doesn't exist), check 'Exclude folders')
   . Click 'OK'
   . Select 'Folder', enter 'C:\', check 'Exclude folders'
   . Click OK
   . Close the properties window
   . Activate the layer
   . Create an empty .txt file in a subdirectory of C: (eg, C:\test\testfile.txt)
   . Use Notepad++ to change the contents of the text file and save the changes
   . Right click on the file in Windows Explorer and click 'Edit' ... the changes made by Notepad++ will be missing
   . Deactivate the layer and edit it - you will find the file in [SYSTEMDRIVE] of the writeable portion of the layer;
     the file should not be there because of the exclude for C:\

   Note: this problem will not happen if:
     . There are no nonexistent drives in the exclude list   -OR-
     . The nonexistent drives preceed 'C:\' in the list

Both of these problems occur because the layer properties edit code does not check the path like the code does when adding global excludes through the admin interface (File>Global Excludes...)

Operating Systems: