<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Okta Verify Fails to Launch Due to WMI Repository and OS Corruption

Okta Verify
Okta Classic Engine
Multi-Factor Authentication
Okta Identity Engine

Overview

Windows operating system corruption affecting the Windows Management Instrumentation (WMI) repository prevents Okta Verify from launching. Administrators resolve this issue by repairing the corrupted files using native Windows diagnostic tools. The user cannot open Okta Verify on a Windows machine. Standard troubleshooting steps, including clearing temporary files, clearing application data, and completely reinstalling Okta Verify, fail to resolve the issue. The Okta Verify process appears in the Task Manager, but the user interface fails to render.

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Okta Verify
  • Windows Operating System

Cause

System-level corruption within the Windows operating system, specifically affecting the WMI repository and core system files, causes the issue. Okta Verify relies on these underlying Windows components to perform device posture checks, validate cryptographic signatures, and maintain secure network connections. The operating system corruption triggers a cascading failure that prevents Okta Verify from launching. Administrators identify this corruption in the Okta Verify logs by locating a combination of the following WMI module, cascading signature, and cascading network failure errors:

[Win32DeviceInformation.GetLocalFixedDrivesByWMI]: Failed to collect disk information because of The specified module could not be found. (Exception from HRESULT: 0x8007007E)

ValidateFileSignature: ... Failed Signing verification

[DeviceSignalManager.RefreshDeviceSignalConfigurations]: Failed to get the signals configuration... exception - An error occurred while sending the request.

Solution

How Do Native Windows Diagnostic Tools Resolve The Issue?

 

Open the Windows Command Prompt, run the System File Checker utility, run the Deployment Image Servicing and Management tool, and restart the computer.

 

  1. Open the Windows Command Prompt as an Administrator.
  2. Run the System File Checker utility to scan for and replace corrupted system files:
sfc /scannow
  1. Run the Deployment Image Servicing and Management (DISM) tool to repair the Windows component store:
DISM /Online /Cleanup-Image /RestoreHealth
  1. Restart the computer after both commands complete successfully.

 

 

Loading
Okta Verify Fails to Launch Due to WMI Repository and OS Corruption | Okta Support