Is Dll-files.com Safe
Latarsha Dorrance
You can download it and upload it to VirusTotal, that will not only give you the MD5, which you can copy/paste into Google to search and verify that it's the same MD5 as the valid DLL, but it will also scan the DLL with many antivirus engines to verify that it is not detected as an infection.
I personally wouldn't download a DLL (especially if it's a Microsoft DLL, i.e., part of Windows) from any website. I'd just run SFC and let Windows reinstall the DLL, that way you know it came from a safe source. If it's a non-MS/Windows DLL, then you should be able to replace it by reinstalling the software that it was installed by.
Well, the MD5 should come up in the results, and based on what sites in the search results say about the MD5, you should be able to determine if it's the right file or not, but if reinstalling the software didn't fix it, then there must be something else going on because the DLL should be there, if it is there, then it's more likely that the DLL just didn't register correctly.
Personally, I'd contact the software vendor's support before jumping through all these hoops and taking risks on downloading a DLL from someone other than the software vendor to try and fix a problem with the software.
wait i think i installed it wrong... im going to try to install the program one more time and see if that fixes it... but the dll came up as clean, and had been scanned before, with 2 good reviews saying goodware. Seems ok i guess...
In PHP, we use .dll files for different extensions. These are specific for the usage. Multiple .dll files exists by default. Sometimes for the specific requirements, we need to enable or add extension and place .dll files in the extension directory. In this case, we found there are multiple sources and multiple versions of same .dll file. We choose correct extension by using hit and trial method only. Some of these versions are for thread safe PHP while some are for non-thread safe PHP.
I have a friend with a problem. He a few computer issues with spyware and what he thought was a virus. He mentioned just doing a system restore to and earlier time. I told him it was worth a shot, so he did it and now when he starts his computer all he gets is a blue screen of death that reads:
As far as fixing this, replacing the corupt file seems to be the most logical choice, but since he is unable to start the computer because of this blue screen of death, how do I replace the file? Should it still let me load in safe mode? Then I can change it like that?
Edit/Delete Message
Other Options:
You could try loading windows into the command prompt and replace the file through there. Also there is the Windows recovery console on the CD if you load it in and boot from the CD.
That is assuming Windows is on the C drive. Also you might want to take a copy of gdi32.dll from a working version of Windows XP like maybe the computer you are working on? Instead of the link I provided just so you get the correct version.
Also, if when you replace the file and you notice that other files start becoming corrupt it is usally a sign that your hard drive is dieing in which case you will need to get a new one and try to pull as much data off the old one as possiable before it completley dies.
It is not safe to delete those dll files. Those listed files supports 32 bit applications running in 64 bit machine.Instead of deleting dll files try to register dll by typing
regsvr32 /s wow64win.dll in command propmt with administrator privillege
You can use it to clean out temp files, get rid of tracks you make using Internet Exporer, get rid of history files from document writing, and also to clean the registry without fear of trashing it. I have used it since version one without issues of any kind.
Thanks Gary, I'll do it. Also managed to get Mechanic 5 installed & running - scary how many duplicate files there were - I deleted a bunch of the ones that allowed me to, excepting the ones that asked if I was sure, mostly dll. files relating to my HP printer, Norton, Sierra air card etc. don't know enough to know if it is safe to remove those. I do know that I know enough to be dangerous!!! Really appreciate your continued advice,
Certain anti-cheats kick the player from game because of "untrusted system file", for example EAC does so for the game Rust since a recent update. It seems to be at the game developers' discretion, as some EAC-powered games have suffered from amdihk DLL in the past.
There are good technical reasons for anti-cheats of a variety of games to desire blocking unsigned/untrusted driver files in the system32 and system driver folders. I can know, as an anticheat developer (from another game) myself.
AMD, or any driver publisher, should NEVER ship unsigned driver files. "AMDIHK64" (AMD DVR component) is, as far I know, the only of such file that lacks a digital signing certificate. It's not just not valid, but completely absent, throughout recent releases of Radeon software.
Its not just anti-cheats that are affected, there are obvious reasons why DLL files of known, major (driver) software that are placed in system folders need to be signed. A lot of software can do trust checks and eventually fail. For the anti-cheat of popular games using EAC, you have now impacted hundreds of thousands of users, and they may decide to manually remove amdihk DLL file in safemode, leading to them not benefitting from AMD DVR functionality.. just in a bid to play the game. This isn't ideal.
Again, software/driver publishers should have developers that know what proper project practise is. Shipping out 99% valid signed DLLs and a single or a few unsigned files, is bad practise. Under correct practise, no issues like the anticheat one would arise. The solution is obvious.
Please note that I was able to reproduce the problem by a clean install of Windows 10 build 1903 and immediately installing the latest Radeon Adrenalin software package; ATI drivers really place that unsigned file into your system32 folder, it's not corrupted or infected, it's not our PC's, it is AMD doing that by mistake.
I will personally solve it by removing the DLL file in windows safe mode, but I realize tons of other people are affected, so it needs to be reported. Note: I attached the latest version of the mentioned problematic file into this topic. It got included in the official driver update of 2 days ago, and lacks a digital signature entirely. I don't know if amdihk32.dll is also affected, since I don't have it.
Because also, any software engineer that you ask can tell you why driver publishers should never deliver unsigned DLL's. It's so obvious.. most AMD DLL's are signed, just not this one, and it's put in a sensitive location that anti-cheats don't like if its not signed and placed there.
There's no way to deny this is an issue and bad practise on the driver developer's side, but I can also guarantee you this won't be solved for a long time to come. Unless they realize now that Rust players started getting kicked, I mean realize the consequences of this bad practise, and do something for real.
Same issue here with The Division 2. It seems the issue comes and goes. It won't let me load the game at first (error message) but at the second attempt, it works. Very annoying and just started for me. Never had this issue before. And a bit strange that they are using unsigned driver files. Just bad all around. Perhaps a simple mistake that will be fixed next update. At least I am hoping so.
after installing 16.12.1 cant play planetside 2 which is !! from late 2016. It never got fixed. And like i said obviously a lot of people have been submitting issue reports in the meanwhile. other than the links i previously provided to show how common this issue is around the web, I found a search term that indicates this scale even better: =amdihk64.dll - a lot of the results (not all) are related to Anti-cheats of variety of games kicking for this official AMD file.
Note to your situation specifically: EAC seems to have started being more strict recently for unsigned files in critical folders like here system32, like with Rust, maybe other AC's like the one from your game also started doing this. This is possible an anti-cheat industry move, because kernel based hacking is on the rise (harder to detect) and those are usually not signed. So, AMD unwittingly made themselves a target to these AC's by not signing some files that are used (and located) in ways like this DLL file amdihk64 is. While this is completely avoidable, by as you and I said, digitally signing driver files like they are supposed to be, avoiding such problems for gamers. They now gotta go into safemode cuz file is in use by whole OS, and delete this file to play (not get kicked) sometimes. So it's also not as simple as AMD saying "Hey, report this to that game publisher or anti-cheat software" because the issue is a result of AMD doing things like it shouldn't (always driver files that operate on a level like system32 need to be signed, as I said also all driver and software publishers, especially programmers, would understand why)
What bothers me also is that developers of games affected (like now Rust with EAC) are not sure and advising users that it's their PC's problem: like at -us/articles/115001271745-Untrusted-System-File while as I said this issue is so much a direct placement by AMD Adrenalin drivers of the untrusted file amdihk64.dll straight into your system32 folder.. like, the file is literally contained within AMD driver package.
If it doesn't get 'told' to AMD it means nobody took the time to report it to them. If the issue is as wide spread as you indicate...there should be numerous issue reports received by AMD engineering. Generally, that's not the case. You should furnish this link to anyone with the same issue. Don't assume that anyone else has reported it. If AMD gets 1-2 reports...that's not enough to get their attention...if they receive numerous reports, that puts it in a different category.
c80f0f1006