Finding and Installing the Latest .NET 3.5 patches

After installing Tool Suite and depending on the user environment, they may need the latest .NET 3.5 patch update. You can find the latest .NET 3.5 patches available here:

List of the Latest .NET updates for Windows 10. (Pick the latest one.)

Microsoft Update Catalog

The Windows .NET 3.5 SP1 installer:

.NET 3.5 SP1 Installer

.NET 3.5 SP1 Installer #2

Restore a Tool Suite Network File

The Tool Suite Network file is called:

ToolSuite.sdf

The Tool Suite Network file is stored here:

C:\Program Files (x86)\Freewave Technologies\Freewave Suite\data

Periodically when you start Tool Suite, it will ask you if you want to Backup you Database (DB). Normally this backup of your Network file will be located here:

C:\Program Files (x86)\Freewave Technologies\Freewave Suite\backups

To Restore a Tool Suite Database:

1. Shutdown or Quit the Tool Suite application.

2. Rename the ToolSuite.sdf file in the C:\Program Files (x86)\Freewave Technologies\Freewave Suite\data directory to ToolSuite.sdf.BACKUP

3. Copy any of the backup files to the data directory (Try the latest one first):
a. The Backup Directory is C:\Program Files (x86)\Freewave Technologies\Freewave Suite\backups

b. The Data directory is C:\Program Files (x86)\Freewave Technologies\Freewave Suite\data so copy a single backup copy here.
4. Rename the file to just "ToolSuite.sdf". 
a. Only copy/rename these files when the Tool Suite Application not running. 

5. Then restart the Tool Suite application and your network should be there.

Fatal Error after installing Tool Suite due to system unable to locate .Net 3.5:

This issue is caused by Windows 11 not having .NET Framework enabled by default, in order to fix the issue.

Performing the following procedure will resolve the issue:

1.Uninstall ToolSuite

2. pressing win+r and type optional features

Enable the following: (highlighted in green)

3. Click "Ok"

4. Reboot and complete a fresh installation of Tool Suite

5. This should get rid of the fatal error on the PC!

COM Port Error:
The underlying error is when there’s an issue with the virtual serial port. Like if there’s some sort of failure in their virtual serial port HW/SW while polling is running.

user.config file is read only or hidden error:
If you get the following error about the user.config file being hidden or read-only. They navigate out to that location and delete the user.config file. You may also need to delete the parent directory as well.

In Tool Suite 2.10 it is located here:

C:\Users\<UserName>\AppData\Local\FreeWave_Technologies
Then a sub directory of the Tool Suite version.
In Tool Suite 2.11 it is located here:

C:\Users\<UserName>\AppData\Local\FreeWave_Technologies,_In
Then a sub directory of the Tool Suite version.

In Tool Suite 2.11 it is located here:

C:\Users\<UserName>\AppData\Local\FreeWave_Technologies,_In
Then a sub directory of the Tool Suite version.

SQL Compact Edition Error "1935" during installation:

• https://answers.microsoft.com/en-us/windows/forum/all/sql-compact-edition-error-1935/eb22c127-10e9-4e01-9dd2-6f5a58ec7774
• https://docs.microsoft.com/en-us/troubleshoot/windows-server/deployment/fix-windows-update-errors

Getting the Following Error when Accessing any of the Tool Suite apps except Update and Network Diagnostics:

Note the SerialPortMonitor in the screenshot above.
In the tslog.txt file you will see entries like the following:

System.TypeInitializationException:

The type of initializer for 'Freewave.Environment.SerialPortMonitor' threw an exception. ---> System.Management.ManagementException: Invalid class 
The key issue here is the Invalid Class.

Follow this link to clear the WMI Repository in Windows:

c-sharp-invalid-class-in-a-simple-wmi-query

The Linked procedure is the following:

To verify that WMI is corrupt:

1. Click Start.

2. click Run

3. Type wmimgmt.msc, and then click OK.

4. Right-click WMI Control (Local), and then click Properties.

5.It should list Win32_Process is an invalid class.

6.This error validates that WMI is corrupt.

Steps to repair WMI:

1. In the start menu type "cmd" and then right-click the Icon for this and select "Run as Administrator"
Type "net stop winmgmt" and press "Enter".

2. Open a Windows Explorer and locate the path to C:\ windows\system32\WBEM\ folder and rename the Repository folder to something else like RepositoryOLD (right click and choose 'Rename Folder').
restart the computer.
3. In the start menu type "cmd" and then right-click the Icon for this and select "Run as Administrator".

4. Type "net stop winmgmt" and press enter

5. Type "winmgmt /resetRepository" and restart the computer on last time.