rzaretskiy
Members-
Posts
15 -
Joined
-
Last visited
Never
Reputation
0 Neutral-
ещё выложил лог работы DSIM - https://yadi.sk/d/UuyxYduekgdXjA там про klim6 написано: 2019-05-27 14:05:45, Error DISM DISM Driver Manager: PID=11828 TID=19748 Failed opening driver package for x86: INF Name='C:\Windows\System32\DriverStore\FileRepository\klim6.inf_amd64_1efef344f46b230e\klim6.inf' - CDriverPackage::OpenDmiDriverPackages(hr:0x80070003) 2019-05-27 14:05:45, Error DISM DISM Driver Manager: PID=11828 TID=19748 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:205 - CDriverPackage::Initialize(hr:0x80070003) 2019-05-27 14:05:45, Error DISM DISM Driver Manager: PID=11828 TID=19748 Failed to initialize the instance of CDriverPackage. - CDriverPackage::Create(hr:0x80070003) 2019-05-27 14:05:45, Error DISM DISM Driver Manager: PID=11828 TID=19748 Failed to create a driver package ATL object. - CDmiApi::DriverPackageOpenW(hr:0x80070003) 2019-05-27 14:05:45, Error DISM DISM Driver Manager: PID=11828 TID=19748 Failed to open a driver package object. - EnumDriverPackageRoutine(hr:0x80070003) 2019-05-27 14:05:45, Info DISM DISM Driver Manager: PID=11828 TID=19748 Could not add a driver into the driver enumeration list. This driver may be corrupt: C:\Windows\System32\DriverStore\FileRepository\klim6.inf_amd64_1efef344f46b230e\klim6.inf - EnumDriverPackageRoutine 2019-05-27 14:05:45, Info DISM DISM Driver Manager: PID=11828 TID=19748 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\klim6.inf_amd64_acf9280ab96a0806\klim6.inf is: SIGNED - CDriverPackage::InitSignatureStatus что в общем-то логично - у меня же система x64
-
Nikolay arinchev, логи выложил сюда - https://yadi.sk/d/XEG5Ljxd_lAj0w заметил одну интересную особенность - после возникновения ошибки (но перед тем как нажать OK) я посмотрел в c:\program files (x86)\Kaspersky...\klim6_x64\ - там лежит драйвер другой версии! более свежий - 17 (от марта 2019-го), а Вы мне прислали более старый драйвер.
-
Nikolay arinchev , драйвер klim6 установился (по крайней мере сообщение об успешной уecnfydrt получил), но попытка установки kes всё равно выдаёт ошибку установки драйвера klim6. заметил, что файла klim6.sys в c:\windows\system32\drivers\ нет, он есть только в C:\Windows\System32\DriverStore\FileRepository\klim6.inf_amd64_acf9280ab96a0806\klim6.sys в файлеsetapapi.dev.log такие строки: >>> [SetupCopyOEMInf - C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security for Windows\klim6_x64\klim6.inf] >>> Section start 2019/05/25 17:00:06.243 cmd: C:\Windows\System32\MsiExec.exe -Embedding EB855A39750F38D0BE007F4FE951A6C5 E Global\MSI0000 inf: Copy style: 0x00000000 ! inf: Driver package is already in driver store sto: {Setup Import Driver Package: C:\Program Files (x86)\Kaspersky Lab\Kaspersky Endpoint Security for Windows\klim6_x64\klim6.inf} 17:00:06.247 sto: Driver package already imported as 'oem21.inf'. sto: {Setup Import Driver Package - exit (0x00000000)} 17:00:06.252 inf: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\klim6.inf_amd64_acf9280ab96a0806\klim6.inf inf: Published Inf Path: C:\WINDOWS\INF\oem21.inf >> Section start 2019/05/25 17:00:06.256 cmd: C:\Windows\System32\MsiExec.exe -Embedding EB855A39750F38D0BE007F4FE951A6C5 E Global\MSI0000 dvi: Driver is already installed; no work to do dvi: Committing changes to the network graph >> Section start 2019/05/25 17:00:15.741 cmd: C:\Windows\System32\MsiExec.exe -Embedding EB855A39750F38D0BE007F4FE951A6C5 E Global\MSI0000
-
Dear Nikolay, mklif driver installation raises the same error: it asks for klif.sys driver so i put previously provided klif driver to the same folder, but result is the same. also i noticed that files klflt.sys and klif.sys are being copied to windows\system32\drivers, but mklif.sys not. any other suggestions? Regards, Roman
-
I also noticed warning in Event Log: Ошибка уведомления профиля о событии Load для компонента {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB}; код ошибки See Tracelogging for error details. update - this is not relevant; i've fixed the error with tail service, but both KES installation and driver installation still failing