Please make sure the correct Filters are set when capturing procmon logs, e.g. Procmon logs are extremely detailed, hence we need to know the exact time when the issue occurs. Procmon logs are very powerful, but at the same time the amount of data is huge as well, so please make sure the filters are set correctly, and the correct observation time is noted down so we can cross-reference easily with the CET log files.Īlways include a fresh set of CET log files (log0-4, bgInstall, launchlog, etc) from the same session when obtaining procmon logs, and please note down the computer date/time (down to the seconds) during the issue occurrence.
When to include: When CET has missing dlls or any files, hanging/slow for unknown reasons that aren't shown in the logs This allows us to tell the user to install the latest version of Microsoft VC++ Redistributable to resolve their issue.Īnother use case would be, CET hangs for a long time when opening the print dialog, by using procmon, we can determine that CET is attempting to reach an unreachable network printer (through its network activity) and is failing. smlib.dll) being unloadable, but the DLL file in question indeed exists on the disk and is not corrupted, so what is going on here? Procmon can tell us that smlib.dll depends on vcredist10.dll and CET tries to load vcredist after loading smlib and cannot find vcredist, so it crashes. One use case would be let's say CET complains about some DLL file (e.g. You can find it on this Microsoft Documents webpage. This means it can determine which file that CET is trying to access at a given point in time. registry access, disk access, network activity. Procmon (Process Monitor) is a Microsoft SysInternals utility that can record the system-related actions that are done by a program, i.e.
0 kommentar(er)
