So the kvc.exe never goes by itself online, unless called by using cmd? Because I think I keep the current setup with kvc.exe as it is. You said that before, if I never update Win10 then all is working well. I understand if people use updates, etc. then the kvc needs updating/improving. But for my case, I stay like this and it works ;-) And also, if I ever want to use some of those 'other' features kvc offers, I can just do so. Thank you again for all your help. YOU made it possible that I can indeed use my 'old' driver at boot and all is well. Best regards and Skoll.
KVC provides offset values for the drivers.ini file, which change practically every month—and sometimes even more frequently when Microsoft releases a hotfix. BB doesn’t have this problem. It can pinpoint the exact location of the patch, even in version 26H1 (x64 processors only). Plus, it’s tiny and contains a driver that appears for just a millisecond, pretending to be the sam.evtx log. Then it disappears, and nothing can react to it. You can try it out, for example, on a friend’s computer.
Ok, I will not get even hotfixes. But does KVC go online by itself for check??? And about the BB, for some reason I don't get it, how to install exactly. I don't use powershell and the commands with kvc were clear. Do this, then that and voila. I looked into the description of bb.exe and frankly did not get what to do exacly, statring from the first thing which would be uninstalling...
Kvc won't load the offsets on its own without a command. If you want to change them manually, it's very simple. Copy bb.exe to c:\windows\system32 and replace the entry in the registry that follows Code: autocheck autochk * as shown in the image below: Check that the line in the file c:\windows\drivers.ini is correct DriverDevice=\Device\kvc Then restart your computer. All the script does is automate the process of adding and removing items. It isn't necessary for anything.
Okay, that sound very simple. So, do I leave the kvc.exe in system32? Do I have to kvc uninstall anything? And do I replace in that .ini file the omnidriver to the driver I use? And last, do the files kvc.exe and kvc.pass stay in system32 or do I remove/delete them? I don't want to mess anyting up. I told you that right now all works well... So just to be sure. Thank you.
You don't need kvc; you can type “kvc uninstall” and delete that file. You only need two files: bb.exe in c:\windows\system32 and drivers.ini in c:\windows The latter should have the following config section (replace it if it's different) Code: [Config] Execute=YES RestoreHVCI=NO Verbose=YES DriverDevice=\Device\kvc IoControlCode_Read=2147491912 IoControlCode_Write=2147491916 The [DriverX] section remains unchanged because it specifies the driver you are loading
Well, just did this and its not working now. The driver did not load after boot. I removed with cmd kvc and deleted in system32 kvc.exe/dll/pass and put in there the bb.exe. Changed the reg as you described and changed the driver.ini as follows: [Config] Execute=YES RestoreHVCI=NO Verbose=NO DriverDevice=\Device\kvc IoControlCode_Read=2147491912 IoControlCode_Write=2147491916 [Driver0] Action=LOAD AutoPatch=YES ServiceName=fanio ImagePath=\SystemRoot\System32\drivers\fanio.sys DriverType=1 StartType=1 Then rebooted and that was that. So maybe some cmd command is required after all? Also, does this have something to do with it: File: C:\Windows\System32\ekmglcaf.xsb ? So there is either another way, or I have to just install kvc again.
Check the registry entry (press the windows key + r and type “regedit”) to see if it exists, as shown in my screenshot, under the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager In drivers.ini, you can also change: Verbose=NO Then you'll see what's happening during bootup It definitely works on Windows 10 and 11 up to and including version 26H1
Will you be able to take a photo with your phone while it's booting up? When will it start writing on the screen? P.S. Send me a private message. If you have TeamViewer, I can take a look at what's going on and why, with your guidance. I'll be around for about another hour.
No worries. Will install kvc again. As for the boot screen, nothing is shown. Maybe it needs the script to run?!? Anyways, don't stay around for this. Its the weekend ;-) Your kvc works perfect and I just install it again as before. Thanks again!
Yes. Just downloaded shortly before doing this. BTW, the omnidriver I replaced with My Driver Name. Is that correct? Or maybe that is the reason its not working?
I see probably nothing at boot because I made Verbose OFF. And of course I put in the .ini from your original download, just changed that driver as I posted. Also made that change in registry as I showed. And put all in proper folders, including bb.exe. In any case, I have now removed it all and put kvc back in. All working again. Thanks again and have a great weekend.
I'm glad it works, and I've added UTF-8 handling to ensure it can always handle edge cases—like a power loss during an operation—and save the state You can download it from GitHub and test it; it works on every system I have, but I only have Windows 10 and 11 (25H2 and 26H1). However, the logic is designed to work on older versions. Even if the drivers.ini file is saved in UTF-8, the program will convert it to UTF-16 LE during startup. This is necessary due to, for example, Chinese driver names. Have a nice day as well
Hello again, and just to make sure, I have used the kvc again. That worked and works! So where did you add UTF handling? The bb.exe or the kvc.exe or both?
Both versions from GitHub have forced conversion enabled, so even if someone saves the file in ANSI/ASCII/UTF-8, it will still be UTF-16 LE after a restart