PrintConfig.dll
PrintConfig User Interface file version info
Library on Windows 2 known copies with hashes 1 Sigma rule names it
Is it the real PrintConfig.dll?
C:\Windows\system32\DriverStore\FileRepository\prnms003.inf_amd64_26228fe75304afdf\Amd64\C:\Windows\system32\DriverStore\FileRepository\prnms003.inf_x86_886904471556cc25\I386\2 known copies
10.0.19041.508 (WinBuild.160101.0800) · C:\Windows\system32\DriverStore\FileRepository\prnms003.inf_x86_886904471556cc25\I386\PrintConfig.dll · signed by Microsoft Windows
5dc99d652052692c4830f506b1a32efaf119d9a65a5d9228ae0545b1926dee8210.0.19041.508 (WinBuild.160101.0800) · C:\Windows\system32\DriverStore\FileRepository\prnms003.inf_amd64_26228fe75304afdf\Amd64\PrintConfig.dll · signed by Microsoft Windows
c69c1be0e0990fad586773eca926097ef1fc9dc87ffd8fbb628a4c3a824de479From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.
What detects it
Sigma names PrintConfig.dll in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.