When opening Security Explorer a “Library not registered….” exception dialog appears. Clicking “OK” continues with the program execution and successfully launches the application.
Figure 1
It is not always the same system files that are affected, so discovering the DLLs will require the use of a Windows Sysinternals utility called Process Monitor . Install Process Monitor and create a filter for the Security Explorer process (figure 2), then open Security Explorer.
Figure 2
Close Security Explorer once the error occurs and review the Process Monitor logs for “FAST IO DISALLOWED” events. This will indicate the library files that may be problematic, (figure 3).
Figure 3
Re-register the DLLs within an elevated command prompt by running the command below. In this example “msvbvm60.dll” is used.
32-bit environment: C:\windows\system32\regsvr32.exe msvbvm60.dll
64-bit environment: C:\windows\syswow64\regsvr32.exe msvbvm60.dll
Disclaimer:
“FAST IO DISALLOWED” is not always an indication of a problem and should not prevent an application from running, it is one of the two methods use by Windows to communicate with drivers. Security Explorer should continue to function using the default I/O request packets method after generating the exception.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center