Mss32.dll Windows 10

[Billi Mayhue]

Errorsrelated to mss32.dll can arise for a few different different reasons. For instance, a faulty application, mss32.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.

In the vast majority of cases, the solution is to properly reinstall mss32.dll on your PC, to the Windows system folder. Alternatively, some programs, notably PC games, require that the DLL file is placed in the game/application installation folder.

The mss32.dll file is the Miles Sound System dynamic link library. It enables sound files to be loaded efficient into multimedia applications that require music and sound effects. For instance is the package containing the mss32.dll necessary for "WinAmp" and other audio players in order for them to work properly.

Errors related to the mss32.dll file are commonly appearing while running or installing certain applications. Errors can even occur while starting-up, shutting-down or installing a windows operating system. Errors occur because some kind of unexpected problem with the mss32.dll file is causing malfunction. This kind of errors are typically caused when the mss32.dll file is missing, corrupted or deleted by accident.

Do you have information that we do not?

Did our advice help or did we miss something?

Our Forum is where you can get help from both qualified tech specialists and the community at large. Sign up, post your questions, and get updates straight to your inbox.

Hello, let me say that I have beatin GTA3 and Vice City on PS2 and Xbox. I wanted to see if it was good on PC, so I accquired GTA3 for the PC. I have the play disc and install disc. I installed it, put in the play disc, and hit play GTA3. It said "please insert correct disc." I had a patch, which let me play the game without the play CD. I hit that, and it said "Could not find mss32.dll. Reinstalling the program may fix this." Mss32.dll is right in the program file. I meet the system requirments, I have a 128mb card and 256 RAM and a 2 GHz processor. GTA2, Midnight Club 2 and The Sims 2 work fine with Mss32. Mss32 stands for Microsoft Sound System for System 32- now if only I could fix it. Please help!

Copy the crack from the folder and paste it where your GTA 3 is installed.If you have that MyTyMo nocd you need to delete the crack(first you need to put it)and then put the nocd into the folder where gta 3 is installed.Don't put any patches.If you putted one,reinstall the game and then copy the crack and the other stuff.If you can't find any nocd put the second disk and play it.

You are a douche. Did you see how hard you bumped this. I mean looks at C82's specs then if you look in his sig you will see that they have improved significantly. Infact, he's a frolicking moderator.

The issue is not exclusive to this machine, operating system, OS version, or specific hardware. I have had 3 different computers, all with different hardware and OS versions at some point and the problem persists/has persisted no matter what the hardware or OS setup.

I realised that the problem is the same with the 3 games listed at the top of the post as opposed to the latest total war games because they all have Miles Sound system as part of the software, whereas, Rome 2, Atilla and Warhammer total war titles do not, and I therefore do not have this issue with the latest titles crashing. MSS32.DLL is the file associated with the fault 99% of the time.

I have asked several forums for extensive assistance with this issue only to find no solution in the end, despite some really helpful people and suggestions, usually moderators. I have contacted both Sega (useless and pointless at the same time - the techical support they offered on several occasions was laughable at best, they truly are clueless), Creative Assembly (no reply) and also the creators of the miles sound system programme (no reply).

*Install/reformat/reinstall windows and different operating systems (have used windows xp 32 bit, windows vista 32 bit, windows 7 64 bit, windows 8.1 64 bit and currently windows 10 64 bit) - at the moment I have a dual boot option with the same issue occurring on both operating systems.

*changed graphics settings for all 3 games, using both maximum and minimum settings, crash still occurs no matter the graphics option. my most recent systems have had no problem with lag on these games when max graphics applied anyway.

There are other things I have tried but at this moment in time cannot think of them. Needless to say, I have tried just about everything I have come across - the issue remains. I have even specifically purchased new computers and hardware to combat this particular problem - same issue, every time.

For clarification - this problem only happens with total war games that use the miles sound system and therefore mss32.dll and other related files and the warscape engine (meaning I do not have this issue with the likes of Medieval 2 total war and Rome 1 total war). Since Creative Assembly (thankfully and mercifully) stopped using Miles Sound System with the warscape engine, the issue does not affect Total war Rome 2, Total war Atilla or Total war: Warhammer - which I CAN play with no problem at all with slight driver exceptions which are easily fixed. Following this, I can play the latest total war games on full settings with no problem, and can therefore only come to the conclusion that this is definitely NOT a hardware problem and that it points to either a general software problem, a problem with the actual games using miles software (which doesn't explain how some people can play with no issue at all whilst others cannot?) or a software issue in general (help required, patch required, anything really?)

I have spent a great deal of money, time and effort trying to find a fix for this with no solution. The reason I do this is because I love the total war games, especially Shogun 2 and have done since the days of medieval 1. to some, it's too much effort and not worth bothering about. To me, it means a great deal, and as I have come across many people via forums and internet searches with this and similar issues, I can only assume it means a great deal to others as well.

Whilst I would suggest that the issue remains a problem with Creative Assembly and Sega and that they should be the ones to fix the problem, I doubt very much this is going to happen after 6 years+. Trying to get help with the problem via SEGA support simply proves that some departments are not worth having and that certain tech support people should be out of a job! Harsh as it seems, but they are not the only video game publisher who have this particular approach.

I am therefore asking ANYONE who have any idea what the problem is and how to fix it to help me (and others). If a patch could be created, officially or unofficially it would be welcomed. I am more than willing to troubleshoot the issue again, though would request guidance when doing so this time around in case I am doing something wrong? I will post error reports (I have plenty) and a dxdiag from both win 7 and 10 if needed.

Firstly, I'm not entirely sure what you mean by playing .bik in game folder with mpc-hc? Can you please clarify and provide more information or some instructions as to how to do this for testing purposes?

In respect of the windows 7 update problems, unfortunately it is still a case (on my pc and my mothers at least) that windows 7 seems to be unsupported in terms of windows updates. I have even left the check for windows updates programme running for several hours with no progress whatsoever. Unfortunately, I think this is a push toward windows 10 via bullying techniques by Microsoft. Could be wrong of course.

I have had a brief look at the codec hell page you referenced, thank you very much, I will take a better look at it tomorrow when I should have a little more time to do so. In regards to mpc-hc - would this improve my situation any simply by installing it?

On a side note: Since posting I had the idea of making the mss32.dll file which comes with the game 'read only'. So far it seems to have made the game more stable, but then again, the game can go for a couple of days without crashes, and then be hounded by them, so, not sure of any result at this point without further testing.

3. That's just microsoft going full retard around the same time of W10 release (W7 problem though isn't directly related to that). This should help (it's a pretty known, normal and surpassed problem by now).

5. Not like I want to be pitiless, but dlls are already bloody read-only files conceptually. Process needs functions, load library, do whatever it has to do. But you really don't touch it. And anything you did is certainly a placebo (assuming you didn't also change your behavior somehow, in which case something may be at play).

Game is continuing to crash as usual today, so the latest changes were as you say - meaningless. I will D/L mpc-hc before the next time I run the game. What I can do incidentally is to provide you with a crash log generated by the game itself, but as I am unfamiliar with the file type associated with the log I have no idea how to open them or how to read them - see attached.

Ok, you have to provide more instruction, because I haven't got the slightest idea how to use Microsoft 'windows software development kit' that downloaded when I downloaded visual studio? I have had a look through the files and honestly don't have a clue what I am looking for even with information explaining (badly) how to use it for debugging.

I think there is an issue of miscommunication going on here. Again I am not a computer techie and so I don't have the level of knowledge that I think you think I have. I simply use computers to play games, go on the internet and save documents and photographs etc. Beyond that, I am clueless, and quite frankly I am angered by the fact that neither Creative Assembly nor SEGA have attempted to address this issue and fix it. It shouldn't be left down to the likes of me to search the internet for HOURS and hours on end looking for a solution to a problem I know nothing about and do not understand. So please keep that in mind.

3a8082e126