We have fixed this problem. It required reinstalling Windows XP SE. This ended up being the only way to get the .dll reinstalled and correctly registered. March 12, 2007. We have been running two visual basic.net routines with out any problems for a few months when suddenly they stopped running with the following error (below). Both routines make use of the scripting.dll. The error messages are as follows: 'EFFAFileListCreator.exe': Loaded 'f:\effa file list generator_vbnet\bin\interop.scripting.dll', No symbols loaded. 'EFFAFileListCreator.exe': Loaded 'c:\windows\assembly\gac\microsoft.visualbasic\7.0.5000.0__b03f5f7f11d50a3a\microsoft.visualbasic.dll', No symbols loaded. An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in EFFAFileListCreator.exe Additional information: COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. Unhandled Exception: System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {0D43FE01-F093-11CF-8940-00A0C9054228} is either not valid or not registered. at EFFAFileListCreator.frmMain..ctor() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 553 at EFFAFileListCreator.frmMain.Main() in F:\EFFA File List Generator_VBnet\EFFALIST.vb:line 2The program '[42384] EFFAFileListCreator.exe' has exited with code 0 (0x0). ===================================================================================================================== We have not been able to solve this problem. Anyone have any suggestions? Pete -- modified at 19:19 Monday 12th March, 2007