Windows Installer Error 1603 (0x643) and Device Installation Restrictions
On Windows, the Universal Sensor can fail to install with MSI Installer Error 0x643. This error is Windows Installer error 1603. One cause is a Device Installation Restrictions policy that stops the installation of the SenseOn kernel driver. Organisations usually use this type of policy to block USB devices.
This page shows how to find this cause and how to correct it.
Summary: Add the device ID
Root\SeeDrvto the allow list in your Device Installation Restrictions policy. Apply the policy. On each device where the installation failed, reset the wait before the next attempt.
Symptoms
- The bootstrapper installs and runs, but the sensor does not install. The installation fails with
MSI Installer Error 0x643. - Each new attempt fails in the same way.
- The installation is successful on some devices and fails on other devices. Usually, it is successful on servers and IT workstations, and fails on standard user workstations. The cause is usually a policy that applies only to the user workstations.
Error 1603 is a general Windows Installer code. It means that a fatal error occurred during the installation. Error 1603 has other causes too, for example TLS interception. Find the cause before you change a policy.
Find the Cause
On a device where the installation failed, open these two files in C:\Windows\Temp:
| File | Contents |
|---|---|
release_install.log |
The full installer log. |
senseon-driver-install.logs |
The driver installation log. |
The cause on this page applies only when the driver installation fails with code 3758096968. The log shows this line:
Cannot execute seedrvlib_install. Error: Failed to update driver (code 3758096968)
In release_install.log, the InstallDriver action then returns 1603. Windows Installer then rolls back the installation.
Code 3758096968 is 0xE0000248 in hexadecimal. This code is the Windows error ERROR_DEVICE_INSTALL_BLOCKED. Windows shows this error as "The installation of this device is forbidden by system policy".
Do not use only the bootstrapper log. The bootstrapper log at
%ProgramData%\senseon-bootstrapper\logs\bootstrapper.logrecords the 1603 result. It can contain only the rollback after the failure, and not the step that failed. Use the two files above.
If your logs do not contain this code, the failure has a different cause. Do the steps in Troubleshooting.
Cause
The Universal Sensor contains a kernel driver with the name SeeDrv. Device Installation Restrictions is a group of Windows policy settings. These settings control which devices Windows can install.
Organisations often use these settings to block USB devices. To do this, they prevent the installation of all devices that are not on an allow list. If the SenseOn driver is not on this allow list, Windows does not install the driver. The sensor installer then records a fatal error and rolls back the installation.
In Group Policy, the settings are in Computer Configuration > Policies > Administrative Templates > System > Device Installation > Device Installation Restrictions. You can also deploy the same settings with Intune.
The administrator override does not correct this problem. The override is the setting Allow administrators to override Device Installation Restriction policies. A system service installs the Universal Sensor, not an administrator. Windows also blocks the driver when you enable the override.
Correct the Problem
Step 1: Allow the SenseOn Driver
- Open the Group Policy Object (GPO) that applies Device Installation Restrictions to the affected devices.
- Go to Computer Configuration > Policies > Administrative Templates > System > Device Installation > Device Installation Restrictions.
- Open Allow installation of devices that match any of these device IDs.
- Select Enabled.
- Click Show.
-
Add this device ID to the list. Do not remove the current entries.
Root\SeeDrv -
Click OK to save the setting.
If you use Intune for this policy, add the same device ID to the same setting in the Intune profile.
This change allows only the SenseOn driver. It does not change the effect of the policy on USB devices or on other devices.
Step 2: Apply the Policy
Test the change on one affected device before you apply it to more devices.
- In an elevated command prompt, run
gpupdate /force. If you use Intune, start an Intune sync. - Restart the device.
Step 3: Start the Installation Again
If a device did not try to install the Universal Sensor before, no other step is necessary. Run the install command as usual.
If the installation failed on a device before, the bootstrapper does not try again immediately. After a failure, the bootstrapper waits before the next attempt. The wait increases after each failure, and can be up to 24 hours. The bootstrapper keeps the wait in a file on the disk. A restart of the device or of the service does not reset the wait. If you run the install command again, the wait also does not change.
To start the next attempt immediately, run these commands in an elevated PowerShell session:
Stop-Service senseon-bootstrapper
Remove-Item "C:\ProgramData\senseon-bootstrapper\sensor-update-attempts.json"
Start-Service senseon-bootstrapper
If you do not want to run these commands, keep the device on. The bootstrapper tries again automatically after the wait ends.
Step 4: Examine the Result
-
On the device, make sure that the two SenseOn services have the status Running:
Get-Service senseon-bootstrapper, senseon-seed -
Log in to SenseOn.
- Go to Assets > Devices.
- Make sure that the list shows the device with a recent Last Seen timestamp.
If the Installation Fails Again
Another Device Installation Restrictions setting can also block the driver. For example, a Prevent setting that matches the driver can override the allow list.
Windows records blocked device installations in C:\Windows\INF\setupapi.dev.log. Search the file for SeeDrv. The entry for SeeDrv shows the policy that blocked the driver.
If you need help, send these files from an affected device to SenseOn Support:
C:\Windows\INF\setupapi.dev.logC:\Windows\Temp\release_install.logC:\Windows\Temp\senseon-driver-install.logs
Before You Deploy
Some Device Installation Restrictions policies block all devices that are not on an allow list. If you use this type of policy, add Root\SeeDrv to the allow list before you deploy the Universal Sensor. This prevents the failed installation and the wait that this page describes.
Other settings, such as a Prevent setting that matches the driver, can also block it. Refer to If the Installation Fails Again.
Related Pages
- Troubleshooting for the general checks for problems with the Universal Sensor.
- Installing the Universal Sensor for the install command.
- Endpoint Requirements for the network connections that the Universal Sensor needs, and for TLS interception. TLS interception can also cause error 1603.
- USB Controls for how to block removable media with Group Policy.