Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: eangulus on July 22, 2004, 02:23:23 AM
-
I have had headaches from trying to nut out a problem. After installing Avast home edition free any exe files created with Installshield will not execute.
I ge5t absolutly nothing. Not even an error message. Only sign of me double clicking is a split second of a busy cursor and a quick scan of avast.
I did a system restore to prior the Avast and all works fine again. This is 100% avast doing it as I have spent 3 days now doing clean installs and installing stuff untill it broke. Avast was the problem.
Is this a settings issue or is it a bug in the software. I am running the latest version on Windows XP SP2 with all windows update files installed.
Please help.
-
So you now don't have avast installed any more?
I know where to look for a problem like this.
Did you happen to use Norton Antivirus on your machine before installing avast?
Thanks
Vlk
-
Since SP2 is not officially released it still may contain "bugs". I've seen several issues still with sp2, this may be one. What happens if you use installshield and avast without sp2?
-
In this case I doubt the problem is directly related to SP2. We've been running and testing avast on XP SP2 and it works great.
-
To answer the norton one. No. I didn't have norton installed. As I have already said I have done "Clean" install.
Regarding Avast prior to SP2....yes. As a precuation I have tried Avast and SP1 and it still caused the issue.
The o0nly thing that has been different sinche the last time I ran Avast was that this is the first time I have used the latest version. previously I had the older version and it self updated itself. This time a redownloaded a new version and it is causing these dam headaches.
-
Did you use the default settings in resident sheild?
Try turning on the "show detailed info on performed action"
and see what avast is doing when you try to run installshield.
Perhaps you set it to block it.
-max
-
I'd say it's the 16-bit subsystem that's broken. I'd just try removing avast entries from \windows\system32\congif.nt and the registry key HKLM\System\CurrentControlSet\Control\VDD.
-
Just to throw a spanner into the works....
I got it working via setting a restore point. Installing Avast. Then returning to the restore point and reinstalling again. This time it is working 100% fine.
-
I would like someone to investigate this further please.
I just tried the same situation on a clena install then installing the latest build of SP2 2164
I had to do the same thing. I have to create a restore point install avast. return to install point then reinstall avast. It won't even work with just uninstalling avast and reinstalling.
There is obviously a problem with avast and SP2 in one way or another.
-
IMHO I would say it is NOT a Avast problem since Avast is beautifully working without sp2. So the thing that changed is Windows (sp2), not Avast. So blame Microsoft and not a working product like Avast. Besides as MS stated "DO NOT RUN SP2 IN A OPERATIONAL ENVIRONMENT"
And as Vlk said: Avast is working fine with sp2, so it is more likely YOUR system that causes the problems.
-
I'm having the same problem. When I did a system scan it started identifying many safe exe files such as backed up installation files and the primary exe files for major programs were identified as viruses and were apparently quarantined or something. The files are still in the folders but my system will not execute them. I desperately need a fix for this and Avast is definately responsible for this problem.
-
Well I am running SP2RC2 with no problems whatsoever.
Avast build 4.1.418 VPS 0431-0
Which SP2 are you running? I am running v.2149 XP Pro
And I must tell you that XP was installed 1 time and has been running like a champ since! My wife's is XP Pro SP! and no problems either.
8)
-max
-
Latest vps is 431-1, time for a update :D
-
Avast just updated itself ;)
0431.1 8)
-max
-
I am using SP2 however I do not know how to find out which version. I understand this is a common problem and also that avast may have conflicted with norton, I have uninstalled avast and these files still will not run. Avast cleaner doesn't fix the problem either.
Vlk said he knows where to look for a problem like this, I need to know.
-
here is a link to fix associations
http://www.xs4all.nl/~laar2002/tweak/file-association-fixes.html
hope it helps-max
-
I've tried fixes for externsions, that doesn't seem to be the problem. I can run some exe files, especially ones that I've just downloaded, it seems to be the ones created with InstallShield. I'd say that it seems about 50% of the exe files on my computer are corrupted in some way.
-
Isn't this just a problem of the MSI?
-
I tried to reinstall MSI and that didn't work either. I am, at this point, convinced that these exe files have been corrupted by avast.
I also believe that the company is writing off this major error and hasn't been very helpful to the several people that have reported it.
After two days of the aftermath of these corruptions I have found that the files are irreparable.
-
Even if the issue IS SP2 MS does not garuntee updates to work with other software.
We have all heard the news regarding software companies out trying to make sure their software is SP2 ready.
So weather or not it is MS or Avast at fault the fact of the matter is it is Avast's responsibility to fix the dam thing.
Oh and to those that asked what builds I tested on: 2149 & 2162
-
I don't believe the files could be corrupted by avast! - unless a virus is found (and when it is, you're clearly notified), all the files are manipulated in read-only mode. If you want to check, just download the files again (or copy the "corrupted files" somewhere else, where avast! is not installed and do a fresh download) and compare the content of the files.
-
Josh,
I also believe that the company is writing off this major error and hasn't been very helpful to the several people that have reported it.
Vlk has suggested to something to eangules, I can't find back here if eangules did it. So the help definatly was/is there.
The problem as some are facing here is not reproduceble by Avast or they would have solved it. I tried it here on 3 systems and no error at all. Evreything is working. So don't accuse Alwil of writing off a error. They NEVER do that.
eangules,
So weather or not it is MS or Avast at fault the fact of the matter is it is Avast's responsibility to fix the dam thing.
So if it is MS to blame you expect Alwil to fix the problems MS has? What kind of strange world are you living in. If a Ford breaks down, that means Toyota or any other car manufacturer has to fix it?
I have spoken with several Alfa and Beta testers for MS products and they all agree, Avast and sp2 are working together without problems. I have two systems running for testing purposes, and there also no problem. Personally I am thinking that the few people who have this problem, also have something else in common. Could be drivers, a application, hardware or something like that, which is causing this behaviour. Since people speak of a clean install I am wondering how they did that exactly.
Put on a firewall before going online to get/install ALL
updates/patches?
Installed the first patches/updates from the update cd?
Installed all drivers including mobo drivers before installing anything else?
etc etc
Many people say they know how to install a os, but it has been proven that only a few know how to do it the correct way.
-
Calm down everyone, please.
Have you tried removing the two entries I was talking about?
We're not able to simulate the problem. I have avast loaded here on the latest build XP SP2 and I can run all 16-bit programs (both Win16 and DOS) without any problems... :-\
-
Btw, I remember that long time ago, InstallShield had problems with something... I don't know what exactly it was (new version of Windows... fast CPUs... really don't know) - but a big number of InstallShield-created installations couldn't be started. Of course, it wasn't MSI at that time (though nobody said it's MSI here either, did they?)...
I'm not saying it has anything in common with this particular problem, just that the problem may actually be somewhere completely else that you'd expect ;)
-
Did anyone who has this problem already looked in the system and event log? There may be a lot of errors there telling more about the real problem.
-
There would appear to be some bug between Avast and Windows XP SP2. I have this problem with InstallShield installers 2.x and 3.x only after installing Avast in SP2. Before installing Avast they work fine and if I run the same installer with the exact version of Avast in SP1 they work fine.
Some info:
Fresh install tested both SP1 and SP2
SP2 is latest public (2149), did not get to testing prior builds.
No event log evens suggesting anything.
Related post with relevant info.
http://forum.avast.com/index.php?board=2;action=display;threadid=3282 (http://forum.avast.com/index.php?board=2;action=display;threadid=3282)
If I disable avast from sys tray all togehter, still does not allow execution. If I disable the 16-bit/DOS component of avast in config.nt, the insaller will work fine. I happen to be trying to install a relatively updated program whos auther apparently doesnt use a very new version of InstallShield. I can reproduce it with many InstallShield 2.x and 3.x installers. One for testing can be downloaded from:
Website
http://www.runtime.org/ (http://www.runtime.org/)
File URL:
http://www.runtime.org/gdb.zip (http://www.runtime.org/gdb.zip)
Took a bit of digging but I was about to go insane trying to install some programs. Temporary fix of course is to remark the avast component out of config.nt and then add it back after install. Can someone please look at this. I was all excited about Windows XP SP2 until this came up. From my understanding some isntallers are a bit flakey in SP2 because of new MSI installer service but this should not be related.
Thanks
-
Remove the reference to the avast sys file from \windows\system32\config.nt . This will solve the problem.
Also, please export the following registry key and send the .reg file to my email address: HKLM\System\CurrentControlSet\Control\VirtualDeviceDrivers.
Thanks
Vlk
-
Hi. I have one more simple question. What did you guys install first? Avast, or SP2?
Thanks,
Vlk
-
Thank you vlk for the help... I used a slipstreamed install of SP2 to install windows, then immeadietly (atleast on my test install) installed Avast on first reboot.
There is nothing in the VDD registry entry on either of my computers I have tried this on.
Also, I noticed this thread was started in reference to Avast Home, it indeed happens with both home and pro.
From my experience with installers in SP2 it would appear something isnt happening correctly on a fresh install of Avast in SP2. Notice earlier in this thread the reference to using system restore and then reinstalling Avast. I have some time on a spare machine today so I will try to run a installer tracking program to see what is difference when initially installing avast vs installing a 2nd time after a system restore. ;)
-
From my experience with installers in SP2 it would appear something...
Sure, at that key (and related HKLM\System\ControlSet001\Control\VirtualDeviceDrivers or 002, 003) you should have an avast driver (aswMonVd.dll) :'(
-
There is nothing in the VDD registry entry on either of my computers I have tried this on.
I'm afraid this is not true. It seems to be that the SP2 installer somehow screws this key. Just do the export and see the reg file. I'd bet my hat that the entry won't be empty... (although regedit sees it as empty)
We're now making avast installer immune to this but I guess we should also notify MS about this...
Cheers,
Vlk
-
We're now making avast installer immune to this but I guess we should also notify MS about this...
Vlk, I'm not sure this is related but some time ago, the avast driver entry repeats indefinitely here, line after line... It was discussed before without a solution or, better, right now I don't have this repetition (maybe it was solved ::)). Hope this help.
-
Hmm.. nope.. not under currentcontrolset or controlset001 or otherwise.. I will manually add it to my machine when I get home and give it a try again. Note, avast's repair fuction did not solve this either (missing registry entry).
-
Hmm.. nope..
So you did the export and the entry was empty??
Or what 'nope'? :)
-
Yeah...
The registry was completely empty. I manually added the path to aswMonVD.dll to the VDD key and now I can run old install shield setups without removing the 16 bit mon from config.nt.
Strange, I was looking in to some friends machines who use avast home and were trying SP2 build 2149 also. about 4 of 6 machines had the problem, 2 didnt and had the registry key properly. One of the two had aswMonVD.dll listed twice as mentioned earlier in another thread.
-
The registry was completely empty.
I guess you don't understand what I said: my proposal was not to check the key by looking at it in RegEdit but rather export it to reg file and inspecting the file.
What I was saying is that even though regedit shows the key as empty, it is in fact not. It contains invalid data. And that's what's causing the problems.
-
It contains invalid data. And that's what's causing the problems.
This happened before with NAV... Adding two groups of zeros (00,00) and everything after that was corrupted (disappear) :o
-
OK. I am now 100% certain it isn't just me. I have now tried on a 3rd system and same thing happens.
To explain in detail so to allow someone to replicate the problem.
First of you have to have a system with clean install or at least NEVER ever had Avast on it even if uninstalled.
Then you install SP2 (i run XP pro btw)
Reboot as per nessacery.
Now create a restore point and name it Pre Avast. This step is not what I had done before but will allow you to get working again.
Now install Avast. Reboot.
Now try and run what I think are Installshield created .exe files. The 3 I tried was the Win32 MySQL setup program (latest version), Canon A40 Drivers, and PixelVeiw TV Software. All so far are Installshield apps.
When you double click you will see avast scan it before running. then nothing at all happens. no setup no errors nothing at all.
Now to get working again you must follow these steps. Uninstall and reinstall won't work.
Use System Restore to go back to Pre Avast but Post SP2. You will notice the above applications are working again. Then Re install avast and reboot. You will now notice that everyhting is working as per normal now. Avat installed and all exe files running.
This is the issue I have had with the past 5 reinstalls on my main machine plus 2 friends computers. Can't remember what builds of SP2 I used but I did mention them earlier in this thread.
-
Isn't anyone going to try to emulate this issue or as I am seeing more often amongst these forums that Avast seems to ignore its customers.
-
eangulus
Isn't anyone going to try to emulate this issue or as I am seeing more often amongst these forums that Avast seems to ignore its customers.
I'm one of those customers and I think that remark was totally uncalled for.
-
I dont need to emulate it, there is a problem with sp2. The avast setup fails to create the entry in the VDD key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDevicesDrivers every time I try it..
Fresh install of SP1 updated to SP2, then instlall Avast.. Fails
Frest slipstreamed install of even SP2 final, then install Avast.. Fails
I have to manually add the entry pointing towards "C:\Program Files\Alwil Software\Avast4\aswMonVD.dll" every time. Then it works fine as usual.
A note to Vlk and Technical (not sure since I dont know what OS version the guy is running, but) you may want to check this thread out. http://forum.avast.com/index.php?board=2;action=display;threadid=6600;start=msg51300#msg51300
Might be related.
-
bilemke are you sure you have sp2 final? When I do a clean slipstreamed sp2 install, then install Avast 4.1.418, it created the registry entry properly and everything works as expected.
-
yup.. sp2 final.. Downloaded it last friday or saturday if I remember correctly.. Anyway, it is build 2180 and the signed version of the file at that, not the one that was unsigned.
-
Bilemke, did you install Norton antivirus before in this system?
I think not, but... Are you using a new installation of Windows (clean)?
The VDD key should be there even without avast ::)
-
@Techincal..
1. Yes, clean install.. Nothing installed after a frest install of Windows SP2 before installing Avast. I hate Norton Products.. messy installer/remover.
2. Yes, to clarify, the vdd key is there and blank before and after Avast install.
-
Very odd, I installed in a MS VPC 2004 guest, as well as on my host system, it worked on both. Are you formating the drive or installing over existing windows? Are you slipstreaming SP2? Is it a legal copy of windows?
It's really bizarre that on a fresh install of windows it would work for me and not you since we basically have identical systems at that point.
-
What t6he hell are you guys talking about? This is not to do with the key. I read that thread when I was first trying to find a solution and it wasn't the problem.
Can someone PLEASE try to emulate my issue as per instructions prior.
Even if knowone else can then at least I will have an answer.....
-
First of you have to have a system with clean install or at least NEVER ever had Avast on it even if uninstalled.
Then you install SP2 (i run XP pro btw)
Reboot as per nessacery.
Now create a restore point and name it Pre Avast. This step is not what I had done before but will allow you to get working again.
Now install Avast. Reboot.
Now try and run what I think are Installshield created .exe files. The 3 I tried was the Win32 MySQL setup program (latest version), Canon A40 Drivers, and PixelVeiw TV Software. All so far are Installshield apps.
When you double click you will see avast scan it before running. then nothing at all happens. no setup no errors nothing at all.
Now to get working again you must follow these steps. Uninstall and reinstall won't work.
Use System Restore to go back to Pre Avast but Post SP2. You will notice the above applications are working again. Then Re install avast and reboot. You will now notice that everyhting is working as per normal now. Avat installed and all exe files running.
This is the issue I have had with the past 5 reinstalls on my main machine plus 2 friends computers. Can't remember what builds of SP2 I used but I did mention them earlier in this thread.
eangulus, take it easy, please. We're reading your thread and trying to understand what we can do but, I myself can't reproduce your system (there is not SP2 in other languages than English right now...) :-\
-
@Technical and eangulus
I beleive we are still on the topic.
eangulus, have to you tried doing the same thing as you mentioned in your first post, but without using system restore, and then checking if the registry key referrenced so many times in this thread is both there and correct?
Also, yes, I have tried emulating what you described with system restore.. For some reason, after a system restore operation, Avast will correctly produce teh said registry key and all will be good. :)
@norxh
Note, the differences in VLK PRO, PRO and Home are not that drastic or important.. But, if someone thinks it matters, yes.. I have tried it on all of the 3.... Even a persons machine that I beleive had a VLK version of PRO. :o
And for the last time >:( fresh clean install of slipstreamed sp2. I always destroy the entire existing copy of windows before installing again. Upgrading a old install sucks!
@Everyone
The final point is, some may not be having the problem, but others deffinately are. I can easily reproduce the problem on several machines. Said problem being strictly the registry key mentioned does not get produced on all installs and I have to manually add it. Then Avast work 100% great.
BTW, yes I can reproduce it on many machines. All will run anything else flawlessly. Hardware is in ideal working conditions and considerable variety amongst them all.
Finally, all names mentioned above, do not take anything I said personally, I am just getting a little frustrated. If avast setup has/had a nice logging feature I would run it. It may have one already that I am not aware of, but no one has suggested it so is it safe to assume it doesnt?
-
Almost foregot,
@eangulus
Yes, when this problem occurs InstallShield 2.x and 3.x installers will fail to run properly.
I have fixed this every time by manually fixing the registry key. Please try this if you have yet to get the installers you need to run. It should fix it for now.
-
Does this help any?
C:\Program Files\Alwil Software\Avast4\Setup\setup.log
Your discussion is way over my head but, there is a log.
-
Dont want to ask too much.. but may I ask, does someone know at what point setup is supposed to make this key? Or is it one of the installed services is supposed to make it on first run? Setup.log doesnt say much, only when/where/what files.. etc.. Some basic things like CLSID's and shared dlls.. But never a reference to aswMonVD.dll except for moving it.
-
Bob, now I like your signature... Very good change indeed 8)
Oh, sorry, I'm off topic :P
-
Dont want to ask too much.. but may I ask, does someone know at what point setup is supposed to make this key? Or is it one of the installed services is supposed to make it on first run? Setup.log doesnt say much, only when/where/what files.. etc.. Some basic things like CLSID's and shared dlls.. But never a reference to aswMonVD.dll except for moving it.
funny thing. i can reproduce it now. i'm using the exact same disc image and avast installer file as before, in VPC2k4, you can run a VPC without ever commiting any changes so each time you do a cold boot of the VPC, its reverted back to the original hard disk image. So, I can say nothings changed for sure. Anyway, I ran about 10 times, reverted each time, and its reporducable every time. The installer does not write to the VDD key. Here is all regmon picks up during the install, right near the end:
5674 79.67422089 avast.setup:452 OpenKey HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers SUCCESS Access: 0xF003F
5675 79.67447790 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5676 79.67462904 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5677 79.67476984 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5678 79.67489332 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5679 79.67513944 avast.setup:452 CloseKey HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers SUCCESS
Not WRITEs. I tried running it with and without the preexisting 2 null bytes,
-
Norxh, I'm Flamengo :P
-
1. Why the emotions, guys? Is this some kind of stress situation? Calm down, it's just a minor issue between your AV program and the new enhancement of your OS...
2. I'm currently on vacation and cannot simulate/debug the issue but I've forwarded it to a dev that will take care of it.
3. Thanks to everyone who helped to pinpoint the problem.
Greetings from Paris,
Vlk
-
@Vlk
All is ok, just one of the more concerning (yet relatively small) bugs/problems I have seen with Avast...
And hey, the emotions are there.. use them.. Not like we used a lot or anything.
Oh yeah, Have a nice vacation in France.
-
Why the emotions, guys? Is this some kind of stress situation?
Well we're not in Paris ;D
-
Hi,
I tried to simulate this problem following eangulus' instructions - vmware with WinXP clean install and the registry entry was written correctly. Please all who can reproduce this problem, send me export of registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers, before avast is installed on SP2 and after installation, to forejt at asw dot cz.
-
@Forejt
Will do, actually plan on getting sp2 final installed on my machine (personal primary, not a friend, family, customer) finally.. today or tommorow..
Note, I assume you saw this post....
Dont want to ask too much.. but may I ask, does someone know at what point setup is supposed to make this key? Or is it one of the installed services is supposed to make it on first run? Setup.log doesnt say much, only when/where/what files.. etc.. Some basic things like CLSID's and shared dlls.. But never a reference to aswMonVD.dll except for moving it.
funny thing. i can reproduce it now. i'm using the exact same disc image and avast installer file as before, in VPC2k4, you can run a VPC without ever commiting any changes so each time you do a cold boot of the VPC, its reverted back to the original hard disk image. So, I can say nothings changed for sure. Anyway, I ran about 10 times, reverted each time, and its reporducable every time. The installer does not write to the VDD key. Here is all regmon picks up during the install, right near the end:
5674 79.67422089 avast.setup:452 OpenKey HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers SUCCESS Access: 0xF003F
5675 79.67447790 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5676 79.67462904 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5677 79.67476984 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5678 79.67489332 avast.setup:452 QueryValue HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD SUCCESS ""
5679 79.67513944 avast.setup:452 CloseKey HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers SUCCESS
Not WRITEs. I tried running it with and without the preexisting 2 null bytes,
2nd, doing what eangulus did (i tried it out) with sytem resotre will result in the registry entry being creadted/modified correctly. However, this should not be required to get it installed. So I will send you before and after install of avast (not doing the system resotre trick) and and a after doing the sytem restore if needed.
-
Wow, took me a long time to get sp2 installed.. Been debating a new machine for the last week and didnt want to waste my time installing windows on my old machine...
Anyway, registry right after windows, before avast install, after avast install but before restart, and after restart after install of avast.......
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers]
"VDD"=hex(7):00,00
The same every single time.. Exacltly what is produced anytime you make a new empty Multi-String Value (REG_MULTI_SZ).
-
For me, installing SP2 does not bring any trouble with that Registry key.
It remains at it was before:
C:\Arquivos de programas\Avast\aswMonVd.dll 8)
-
For me, installing SP2 does not bring any trouble with that Registry key.
It remains at it was before:
C:\Arquivos de programas\Avast\aswMonVd.dll 8)
It isnt installing sp2 after having avast installed on a pre sp2 install of windows that causes problems.. it is isntalling avast on a fresh install of windows xp sp2.
-
It is isntalling avast on a fresh install of windows xp sp2.
Thanks bilemke... This will be a serious problem to be solved in version 4.5 of avast :-\
-
Eangulus,
I also facing the same problem of mysql doesn't install after I installed Avast Home / Professional into my PC with Windows XP Service Pack 2. It very weird why Avast Block the installation? May be it block the mysql service and not allow to be install??? I have try remove Avast and install mysql, it still doesn't work. Funny ??? Hope Avast technical support personnel can resolve this issue.
Thank you.
-
May be it block the mysql service and not allow to be install???
avast is an antivirus and if the setup files are ok, it won't block the installation.
Maybe they are infected ???
I have try remove Avast and install mysql, it still doesn't work.
Did you try or succeed removing avast?
Funny ??? Hope Avast technical support personnel can resolve this issue.
Well, they need to know more about what is happening to help you... If you have a firewall, if you have another antivirus installed, etc. etc.
-
Yes, I try to remove the Avast from my system. Now I install mySQL then follow my Avast! Nope Problem!.. It works... :) ;) :D ;D
Thank!
-
This could be related to the problem in this thread. Microsoft's SQL server uses a old version of InstallShield to instlal. Not sure about MySQL but it is possible.