Share via

Driver AsIO.sys cannot be loaded

Anonymous
2024-10-24T18:00:05+00:00

On start up I get Driver AsIO.sys cannot be loaded, a security setting is detecting this as a vulnerable driver and blocking it from loading. Since this started the left and right side of my screen aren't aligned properly making the screen appear split. Any suggestions?

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

23 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-06T22:40:22+00:00

    Hi. I also had this issue when I upgraded to Windows 11 24H2. The saga is in two parts.

    Part One: I suddenly got the error that the driver MsIo64.sys could not load on my device because a security setting detected it as a vulnerable driver. Google research indicated this driver was related to AURA RGB software on my ASUS-based computer. Sources said to update the ASUS "Armoury Crate" software to resolve the issue. I did that and it did not resolve the problem. I then located on an ASUS utility called "Armour Crate Uninstaller" and ran that, which seemed to cure the MsIo.sys problem, but another error immediately popped up: the AsIo.sys error appeared.

    Part Two: I found another source that said to manually remove the AsIo.sys driver from C:\Windows\sysWOW64 (i.e., move it somewhere else but don't delete it in case needed later). That I did and it stopped the error message from popping up with (so far) no apparent negative effects.

    There is also a discussion of this issue here: 24H2 Vulnerable Driver Blocklist detecting driver AsIO.sys in Windows after login | Windows 11 Forum .

    Hope that helps.

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-02-07T23:32:33+00:00

    Dave: great! This is a general issue with upgrading to Win 11 experienced by ASUS utilities users, and your "fix" is stop using them?

    Someone needs to figure out what specifically causes this error and provide us a fix, not a **** kludgey workaround.

    10+ people found this answer helpful.
    0 comments No comments
  3. DaveM121 868K Reputation points Independent Advisor
    2024-10-24T18:34:57+00:00

    Hi, I am Dave, I will help you with this.

    AsIO.sys is a virtual driver usually associated to Asus PC Probe or ASUS AI Suite.

    The best option would be to uninstall whichever of those Asus utilities that are installed on your PC, restart your PC, then download and install the latest version of the utility Asus provide on the support page for your PC on their website.

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-02-28T10:42:53+00:00

    I find the situation inexcusable. I reached out to both Asus support and Microsoft support, yet ultimately, it was up to me, a user with no programming knowledge, to resolve the issue with my PC. This is perplexing.

    Firstly, the method Asus employed to gather information about my system was overly complicated for users without technical expertise. A more effective approach would be for them to remotely access the PC to diagnose or fix the problem. At the very least, they should guide users towards downloading a diagnostic tool that can automatically identify issues. The process involved too many steps (30 steps to be exact, I kid you not).

    The final recommendation from Asus was to uninstall AI Suite 3 using a cleaner and install "Armoury Crate". However, I continued to experience issues with AsIO.sys triggering messages on Windows 11. It would have been helpful if Asus had instructed me to DELETE the driver, which they did not.

    When I contacted Microsoft support and explained the issue, they took control of my PC, conducted numerous diagnostics, and ultimately advised me to reinstall Windows (a common suggestion). They suggested reinstalling Windows 11 Pro while keeping my files, which, although retaining data, is still an inconvenient and incomplete solution.

    Upon discovering this forum, I decided to independently attempt deleting the problematic driver. My plan was, if unsuccessful, to resort to Microsoft's recommended reinstallation. The task manager confirmed this problematic driver was not being used, providing me confidence that I could delete it. After removing the driver, three additional drivers appeared, which I also deleted. I restarted the PC after each deletion. Once the error messages ceased, I verified through "Armoury Crate" that the system temperatures and other probes functioned correctly without the offending drivers. They did.

    However, the support process from Asus, conducted via email, was lengthy (December 24 - January 21) and did not resolve the problem. Instead, they suggested uninstalling old software and installing new versions, followed by offering a €5 discount on the Asus Store. For future PC purchases, I intend to avoid using Asus products. This experience has led me to question the level of customer support provided for their premium line products. Moving forward, I prefer a company that not only produces quality products but also ensures ongoing support and reliability for their customers.

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-12-05T20:32:30+00:00

    Hi:

    I'm hijacking Giles' reply as I can't seem to reply to Dave's original post.

    I have an Asus desktop and I am getting the same message: "Driver: AsIOsys - A security setting is detecting this as a vulnerable driver and blocking it from loading. You'll need to adjust your settings to load this driver."

    I searched for both of the Asus utilities Dave recommended (Asus PC Probe or ASUS AI Suite) and I don't have either on my system.

    Not sure what to do next. I know next to nothing about how my PC runs. Talk to me like I'm 4 someone, please, because this is driving me nuts!

    I have an active MS365 subscription, if that matters.

    8 people found this answer helpful.
    0 comments No comments