Issues with WebView2 Browser
Tascus uses an embedded WebView2 (Edge) browser to display work instructions and some reports.
If these do not display, there may be an issue with the WebView2 installation,
WebView2 Not Initialising
Symptom
On application startup:
Embedded WebView2 browser does not load
No error message shown
The following folders are not created in the application directory (C:\ProgramData\Tascus):
Tascus.exe.WebView2
Tascus Launcher.exe.WebView2
On working machines, these folders are created automatically when the application opens.
What This Means
If the .WebView2 folders are not created, the Microsoft Edge WebView2 runtime has not initialised. This is a WebView2 runtime resolution failure.
Root Cause
The Microsoft Edge WebView2 Runtime is:
Not installed machine-wide
Installed per-user only
Corrupt or not registered
Blocked by corporate policy (AppLocker / WDAC / Defender)
Disabled via Group Policy
Required Fix
1. Install WebView2 Runtime (Machine-Wide)
Install:
Microsoft Edge WebView2 Runtime – Evergreen Standalone Installer (x64)
Important:
Use the offline / standalone installer
Install machine-wide
Do NOT use the bootstrapper version
2. Confirm Runtime Location Exists
After installation, this folder must exist:
C:\Program Files (x86)\Microsoft\EdgeWebView2\
3. Ensure Runtime Is Not Blocked
Confirm the following are not restricted:
msedgewebview2.exe
WebView2 runtime components
Edge WebView2 execution under AppLocker / WDAC / Defender
4. Confirm Edge Components Are Not Disabled
WebView2 depends on Microsoft Edge components.
If Edge is removed or disabled via Group Policy, WebView2 will fail silently.
Notes
WebView2 requires the x64 runtime, even if the application is 32-bit.
Running the application as Administrator does not resolve this issue.
If the runtime is correctly installed and not blocked, the
.WebView2folders will be created automatically on application launch.
Verification
After successful runtime installation:
Launch the application
Confirm that the
.WebView2folders are createdConfirm embedded browser content loads correctly
If the issue persists after completing the above steps, the problem is likely related to:
OS image configuration
Enterprise security policy
WebView2 runtime registration failure
How to reconnect to work instruction folders
If your work instructions are located on a shared network drive, sometimes the connection can be lost, meaning no images are displayed when the Tascus sequence runs. We've now added features to check and retry to connect.
