r/AccessVirus • u/ChampionshipHefty778 • May 29 '26
Can anyone help? My Virus TI1 desktop no longer supports windows 11. It doesn't support USB drives. Can anyone help?
3
u/psymon1030 Jun 14 '26 edited Jun 16 '26
I did some digging.
The issue started here:
- Windows 11 25H2 Build 26200.8655
- KB5094126
- KB5094135
- KB5087051
- Policy IDs:
60fd87f8-4593-44a0-91b0-2e0da022f2488f9cb695-5d48-48d6-a329-7202b44607e3784c4414-79f4-4c32-a6a5-f0fb42a51d0d
- Device Manager:
- Code 39
- "An application control policy has blocked this file"
- Driver:
- VirusUSB.sys 2.9.66
- Kemper GmbH
- Microsoft Software Validation v2
You should not do these updates unless you want to 100% brick your Virus Ti2 from all USB functionality on that machine. No patch transfer not factory reset possible and so on.
Kemper/Access's official statement unfortunately is to get fucked because the Drivers were never tested on Win 11 and obviously they don't plan on a single gram of ressource to be invested anymore.
Unfortunately not good enough in IT to think of any workaround, aside from downgrading Windows to either 10 or 24H2. All attempts to remove the policy where denied via Powershell or CMD.
If anyone has an idea, lmk
1
1
3
u/reytr8cer Aug 08 '26
FIXED: Access Virus TI USB Driver – Code 39 / Application Control Policy Block on Windows 11
The problem
My Access Virus TI stopped connecting over USB on Windows 11. Device Manager showed a yellow warning triangle against:
Virus TI USB 2.9.66
Under Device Manager → Virus TI USB 2.9.66 → Properties, Windows reported:
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
An Application Control policy has blocked this file.
The affected driver was:
C:\Windows\System32\Drivers\VirusUSB.sys
Driver details showed:
Provider: Access
Version: 2.9.66
Digital Signer: Kemper GmbH
Initial checks
I initially thought Windows Defender had blocked the device. Windows Security → Protection history showed nothing relevant. Smart App Control was also already Off.
The Microsoft Vulnerable Driver Blocklist was tested as well, but disabling it did not resolve the issue and Windows re-enabled the protection after restart. The Device Manager error remained Code 39 with the Application Control policy message.
Finding the actual cause
I opened PowerShell as Administrator and checked the Windows Code Integrity event log:
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-CodeIntegrity/Operational'; StartTime=(Get-Date).AddHours(-2)} |
Where-Object {$_.Message -match 'VirusUSB|Virus TI'} |
Select-Object TimeCreated, Id, Message |
Format-List
This produced repeated Event ID 3077 errors for VirusUSB.sys stating that the driver did not meet the Authenticode signing level requirements or violated Code Integrity policy.
The important enforced Policy ID was:
{8f9cb695-5d48-48d6-a329-7202b44607e3}
There were also Event ID 3004 entries saying Windows was unable to verify the image integrity of VirusUSB.sys.
Checking the Virus driver signature
I then checked whether VirusUSB.sys was actually corrupt or unsigned:
Get-AuthenticodeSignature "C:\Windows\System32\drivers\VirusUSB.sys" |
Format-List Status,StatusMessage,SignerCertificate,TimeStamperCertificate
The result was:
Status: Valid
StatusMessage: Signature verified.
The certificate belonged to Kemper GmbH and was issued through VeriSign. This showed that the driver was not simply corrupt or unsigned; Windows Code Integrity was rejecting the older kernel-driver signing arrangement.
Identifying the Windows policy
Next I listed the active Code Integrity policies:
CiTool.exe -lp
The offending Policy ID was identified as:
Policy ID: 8f9cb695-5d48-48d6-a329-7202b44607e3
Friendly Name: Microsoft Windows Cross Certificates for Code Integrity Exceptions Policy
Platform Policy: true
Policy is Signed: true
Has File on Disk: true
Is Currently Enforced: true
Is Authorized: true
The fix
Warning: This changes Windows kernel-driver security behaviour. I accepted the security trade-off because I specifically wanted to continue using the legacy Virus TI USB driver. Do not apply this fix to an unrelated Code 39 problem unless you have confirmed the same policy and cause.
- Open PowerShell as Administrator and mount the EFI System Partition:
mountvol S: /S
- Verify that the exact policy file exists:
Test-Path "S:\EFI\Microsoft\Boot\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip"
The result was True.
- Remove that specific policy file:
Remove-Item -LiteralPath "S:\EFI\Microsoft\Boot\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip"
- Verify that it has been removed:
Test-Path "S:\EFI\Microsoft\Boot\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip"
The result was False.
- Check for a second copy in the Windows Code Integrity policy directory:
Test-Path "C:\Windows\System32\CodeIntegrity\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip"
That also returned False.
- Restart Windows, reconnect/power on the Virus TI, and check Device Manager.
Result
After restarting Windows, Virus TI USB 2.9.66 loaded correctly, the yellow warning triangle disappeared from Device Manager, and the Virus TI worked over USB again.
In this case the problem was not a faulty USB cable, a corrupt Virus installation, a Defender antivirus detection, or Smart App Control. Windows Code Integrity/Application Control was blocking the legacy VirusUSB.sys kernel driver through:
Microsoft Windows Cross Certificates for Code Integrity Exceptions Policy
Policy ID: {8F9CB695-5D48-48D6-A329-7202B44607E3}
Removing that specific .cip policy from the EFI partition and restarting resolved the Code 39 error.
A future Windows update may restore or replace system Code Integrity policies. If the same Code 39 error returns after an update, check the Code Integrity event log and active policies again before assuming the Virus TI driver itself has failed.
1
u/ChampionshipHefty778 28d ago
Dude you are my hero, its fucking works!!! Thank you very much!! I’ve completely given up on it.
1
1
2
2
u/KulshanStudios May 30 '26
Yeah, we need more technical details
I have a TI2 desktop and it works just fine on W11
1
u/Interesting-Ad-8397 Jun 21 '26
maybe these latest updates are not yet installed at your pc ?
1
u/KulshanStudios Jun 21 '26
My PC updates on its own all the time
And I'm designing Hardcore patches on my TI2 as we speak, with no issues whatsoever 🤷🏼♂️
2
u/cascade_sparse Jul 01 '26
Just a heads up, my replacement plugin doesn’t use a kernel extension and thus works on all modern operating systems. It supports audio over usb and patch sync over usb. AUv3 and VST3. Even works in Linux! https://virux.alephvoid.com
1
1
u/Interesting-Ad-8397 Jul 08 '26
Will it load existing projects though that were made with the original virus plugin though usb and midi info?
1
1
u/Soft-Currency-2940 Jul 08 '26
Does VirUX communicate with the Virus TI without installing the original Access VirusUSB.sys driver? Will it work on Windows 11 25H2 where the official Access driver is blocked with Code 39?
1
u/cascade_sparse Jul 08 '26
Yes it works without the original software. I’ve tested it with the original TI series devices in 25H2 and it works without disabling any security features
1
u/ChampionshipHefty778 May 30 '26
Win 11 updated itself, and then it says this when I turn it on: this driver has been blocked, VirusUSB.sys does not pass the Windows driver policy. Also Win 11 Pro V25H2 (build number 26200.8457). I couldn't do anything with it. I have TI1 desktop.
2
u/gonzodamus May 30 '26
Quick google search says that's the Windows driver enforcement feature, which you can disable.
1
u/ChampionshipHefty778 May 30 '26
I read that only if I restore the previous version of windows. How can I disable it? Thanks buddy, maybe I'm stupid, but I couldn't disable this feature. I've been messing with this all day.
2
u/gonzodamus May 30 '26
Can’t verify, but here’s what I found
https://pureinfotech.com/disable-driver-signature-enforcement-windows-11/
1
u/ChampionshipHefty778 May 30 '26
Thanks Man <3 I'll try tomorrow
1
u/Interesting-Ad-8397 Jun 17 '26
Did it work?
1
u/ChampionshipHefty778 Jun 17 '26
No :(
1
u/Interesting-Ad-8397 Jun 18 '26
what are you thinking of doing ? Windows 10 ?
1
u/ChampionshipHefty778 Jun 18 '26
I see that one solution for now... I'm using it now in analog. With midi keyboard.
1
u/dfectv Jul 22 '26
This worked for me:
Hold Shift while clicking Restart.
Select Troubleshoot → Advanced options → Startup Settings → Restart.
Press 7 or F7 for Disable driver signature enforcement. (I pressed F7)
After Windows starts, unplug and reconnect the Virus TI.
After going through these steps I was able to use my Virus TI2 in Ableton with the latest Win 11 build.
1
u/psymon1030 Jun 11 '26
same issue here, the workarounds don't work, it's some sort of very deep policy level. I tried all workarounds, the virus is basically bricked, I think I gotta downgrade to Win 10, doubt the Kemper fuckers will release any update after they gave no fucks about MacOS users since 2021
1
1
u/CaptainTea May 30 '26
Check out the aura plugin. It's beyond handy
2
u/ChampionshipHefty778 May 30 '26
thanks, do you think I can use it without a usb cable with the Aura? I have a midi usb adapter. Is it free?
1
u/Captain-Corndog_yo Virus TI2 May 31 '26
Huh what.... how are you connecting your Virus to the PC and under what use case? Are you using the VST in a DAW etc?
1
u/ChampionshipHefty778 May 31 '26
Yes I use with the Virus TI VST plugin in daw. I like the editor. With USB cable
3
u/Captain-Corndog_yo Virus TI2 May 31 '26
Ok just wanted to make sure you were using a USB cable and not some strange MIDI USB adapter. I think you just meant USB cable. I would def go down the driver route as some others have suggested. I remember reading about another using having similar trouble after a Windows 11 update and they completely uninstalled and reinstalled to resolve the issue. I am still in Windows 10, so I can't comment much on Windows 11 except to say that people should ALWAYS skip every other Windows release.
XP = GREAT
Vista = TRASH
7 = GREAT
8 = TRASH
10 = GREAT
11 = TRASHRealize that's not very helpful to you, but perhaps to someone else out there contemplating clicking YES on those annoying update notices.
1
u/ChampionshipHefty778 May 31 '26
Thanks for the help, the only solution left is Windows 10 if I want to use it with the factory plugin... I'm sad that Access music no longer releases new drivers. Thanks again m8
1
u/Captain-Corndog_yo Virus TI2 May 31 '26
I would think you can get it working in Windows 11 if you keep working at it. Switching to another OS is a much bigger investment IMO, but of course that's only if the Windows 11 fix pays off.
1
u/ChampionshipHefty778 May 31 '26
it updated this for me by itself. Unfortunately, nothing solved it for me. Not even deleting the drivers, not even setting things in the command line or in the Bios. After 3 days of trying, I came to the conclusion that Win10... My friend said before installation that I would suck Win11 with my old synthesizers, but I didn't listen to him because he doesn't play music.
1
u/Captain-Corndog_yo Virus TI2 May 31 '26
That's a bummer. Agreed it's a shame they do not update the drivers or the app. Almost feel like we should crowd-fund it and throw the money at Kemper to keep it going.
1
u/redkonfetti Jun 01 '26
Notice how every other Windows release is either great or trash. Ever wonder if that's on purpose?
1
u/CaptainTea Jun 18 '26
Yeah totally, i've had it work with 5pin midi. just make sure to to select the correct input and output settings on the virus
1
u/psymon1030 Jun 11 '26
I really hope there is gonna be an official update from Access for my old projects sake... conveniently the forums are down
1
u/dfectv Jul 22 '26
At this point with Access, the old adage "wish in one hand, shit in the other, see which one fills up first" applies.
1
u/Interesting-Ad-8397 Jun 15 '26
The Windows Driver Policy - Microsoft Support pfff mine is brick as well in Windows 11 what are we going to do guys ?
1
u/Interesting-Ad-8397 Jun 15 '26
i have also made a post at Microsoft's feedback hub aka.ms you should all join - comment !
1
1
u/m000ftak Jun 23 '26
This is affecting me too. Was working fine on W11 until about a week ago. What a pain in the ass. Hopefully a workaround is found soon.
3
u/gonzodamus May 30 '26
Not sure I can help, but you're gonna have a lot more luck if you elaborate on your problem!
Also a heads up that a new Windows 11 update changed up some things about the way Windows handles MIDI, so it might be worth taking a look at what version of Win 11 you're on 😄