Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to load a driver. Name changes every run #231

Closed
Git-North opened this issue Jan 1, 2025 · 2 comments
Closed

Failure to load a driver. Name changes every run #231

Git-North opened this issue Jan 1, 2025 · 2 comments

Comments

@Git-North
Copy link

The changes was made to my system as well. Since Tron didn't find anything on my system, I used the restore point that was created to get my system back to the state before I ran Tron. I hated the Win 11 context menu and explorer when I first started using Win 11, but have learned to like the change. I didn't like the change back to the classic menus and explorer. The other issue I ran across is when TDSSKiller run, it tries to install a driver in the windows\system32\drivers directory. Each time TDSSKiller is run, the name of the driver file changes (1st run 41022176.sys, 2nd run 44003320.sys). I did run it a 3rd time from the stage_0_prep directory, but didn't write down the driver name, but it was different from the two above. No sure if this is normal. The driver was blocked by Norton 360.

Screenshot 2024-12-31 160056

Originally posted by @danielsjam in #229 (comment)

@danielsjam
Copy link

danielsjam commented Jan 2, 2025

Update on TDSSKiller - I did a clean win 11 install on a second computer just to verify how TDSSKiller work when run. See screenshot - the driver is required for more advanced threat detection. I ran it three times and the driver file name is different each time. This in my opinion is normal behavior. The driver was blocked by Windows defender, but you can add an exception to allow it to be installed.

01:40:56.0269 0x1d24 KLMD registered as C:\WINDOWS\system32\drivers\37580127.sys
01:42:21.0370 0x2384 KLMD registered as C:\WINDOWS\system32\drivers\06108784.sys
01:48:03.0289 0x1ab4 KLMD registered as C:\WINDOWS\system32\drivers\07026585.sys

Screenshot 2025-01-02 014836

@vocatus
Copy link
Contributor

vocatus commented Jan 9, 2025

Recommend removing Norton from your machine. There is no reason to run 3rd party A/V programs on any Windows OS above 8 these days, they cause more problems than good.

@vocatus vocatus closed this as completed Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants