When i run GTA4 in Gamebooster, every time I open it I recieve the following message:

"Game Booster 3: GameBooster.exe - Unable To Locate Component

This application has failed to start because CRYPT32.dll was not found.

Re-installing the application may fix this problem."

but after I click the "ok" button 11 time I can start the game and run it with little issue. Only bugs I run into ingame wether using gameboooster or not is the texture of buildings and streets will stop loading and go transparent/ invisible after playing the game for so long. My question is how important is this "CRYPT32.dll" and how can I deal with the texturing issue?

Found this within five minutes on google:

How to Fix Crypt32.dll Errors

Important: Do not download crypt32.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of crypt32.dll, it's best to obtain it from its original, legitimate source.

Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the crypt32.dll error.

1. 
   Restore crypt32.dll from the Recycle Bin. The easiest possible cause of a "missing" crypt32.dll file is that you've mistakenly deleted it.
   If you suspect that you've accidentally deleted crypt32.dll but you've already emptied the Recycle Bin, you may be able to recover crypt32.dll with a free file recovery program.
   Important: Recovering a deleted copy of crypt32.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.
   
2. 
   Run a virus/malware scan of your entire system. Some crypt32.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the crypt32.dll error you're seeing is related to a hostile program that's masquerading as the file.
   
3. 
   Use System Restore to undo recent system changes. If you suspect that the crypt32.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.
   
4. 
   Reinstall the program that uses the crypt32.dll file. If the crypt32.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.
   Important: Try your best to complete this step. Reinstalling the program that provides the crypt32.dll file, if possible, is a likely solution to this DLL error.
   
5. 
   Update the drivers for hardware devices that might be related to crypt32.dll. If, for example, you're receiving a "The file crypt32.dll is missing" error when you play a 3D video game, try updating the drivers for your video card.
   Note: The crypt32.dll file may or may not be related to video cards - this was just an example. The key here is to pay very close attention to the context of the error and troubleshoot accordingly.
   
6. 
   Roll back a driver to a previously installed version if crypt32.dll errors began after updating a particular hardware device's driver.
   
7. 
   Run the sfc /scannow System File Checker command to replace a missing or corrupt copy of the crypt32.dll file. If this DLL file is provided my Microsoft, the System File Checker tool should restore it.
   
8. 
   Install any available Windows updates. Many service packs and other patches replace or update some of the hundreds of Microsoft distributed DLL files on your computer. The crypt32.dll file could be included in one of those updates.
   
9. 
   Test your memory and then test your hard drive. I've left the majority of hardware troubleshooting to the last step, but your computer's memory and hard drive are easy to test and are the most likely components that might cause crypt32.dll errors as they fail.
   If the hardware fails any of your tests, replace the memory or replace the hard drive as soon as possible.
   
10. 
    Repair your installation of Windows. If the individual crypt32.dll file troubleshooting advice above is unsuccessful, performing a startup repair or repair installation should restore all Windows DLL files to their working versions.
    
11. 
    Use a free registry cleaner to repair crypt32.dll related issues in the registry. A free registry cleaner program may be able to help by removing invalid crypt32.dll registry entries that might be causing the DLL error.
    Important: I rarely recommend the use of registry cleaners. I've included the option here as a "last resort" attempt before the destructive step coming up next.
    
12. 
    Perform a clean installation of Windows. A clean install of Windows will erase everything from the hard drive and install a fresh copy of Windows. If none of the steps above correct the crypt32.dll error, this should be your next course of action.
    Important: All the information on your hard drive will be erased during a clean install. Make sure you've made the best attempt possible to fix the crypt32.dll error using a troubleshooting step prior to this one.
    
13. 
    Troubleshoot for a hardware problem if any crypt32.dll errors persist. After a clean install of Windows, your DLL problem can only be hardware related.
    

Applies To

The crypt32.dll error message could apply to any program or system that might utilize the file on any of Microsoft's operating systems including Windows 7, Windows Vista, Windows XP, and Windows 2000.

As for the texture problem, your GPU might not be able to handle the game, try turning down the graphic settings. If that still doesn't work, you need to upgrade your computer

Ah thanks, I suspect Norton got rid of it. I had a nasty trojan that nearly made my computer unaccessable I recently got rid of. Is the file important for play? I'm not having any major issues except for when i call for noose backup or airsupport the game will crash immediately upon pressing back-up keys.

To fix the texture issue, try reducing your graphics settings.

thanks guys, mod you can close this post

Nothing to see here!

---

This topic has been closed by G17 Media staff.

If you feel that this topic has been closed in error, please report this post.