Alexander Schulz

Same here... :-(

* vim * mc ("graphical" file browser)

* monitoring: check-mk-agent (and xinetd and maybe changes at the firewall rules for port 6556)

aahhh!!!! could not build xeniface because of a bug in Windows Driver KIT 10.0.17763.0 ... ahhh!!!! They had their `#pragma (push)` and `#pragma (pop)` not in sync to each other...

build of PV Drivers 8.2.2 was successfull Now I test on a german Windows 10 Pro x64 to install all the fun stuff, if this goes well, we have the...

for our brave testers: https://github.com/xcp-ng/win-pv-drivers/releases/tag/v8.2.2-beta

:exclamation: Found the reason why the drivers get not installed when the main installer runs :exclamation: `C:\Windows\INF\setupapi.dev.log` * Driver package signer is unknown. Assuming untrusted signer. * Driver package failed...

So if you install the drivers later (like mentioned in some troubleshooting guides and posts) this pops up:  and this is in the logfile `C:\Windows\INF\setupapi.dev.log`  ... :thinking: ......

Hmm... after some reading .. all the relevant things are there: * valid Certificate Chain - from Certum * valid Timestamp - from Symantec :-/ * valid Cross Certificate Chain...

Here someone has the same problem, but with Windows 7 (*still reading*): https://social.msdn.microsoft.com/Forums/office/en-US/b65222ea-d11a-41cd-8d9b-fef43aedb065/howto-sign-kernel-driver-for-automated-field-deployment?forum=wdk