Error -5009 : 0x8002802b

iviv · 24 Mar 2014 at 22:33

I recently had the hankering to play Red Alert 2 again, so got my First Decade DVD out and tried to install it. Unfortunately when the setup runs, it immediately fails during the 'preparing the InstallShield Wizard' step with the error:

Error Code: -5009 : 0x8002802b
Error Information:
>Ctor\ObjectWrapper.cpp (163)
>Ctor\ObjectWrapper.cpp (391)
>Kernel\Component.cpp (1163)
>Ctor\ObjectWrapper.cpp (34)
>Ctor\DriverWrapper.cpp (31)
>Kernel\Component.cpp (1152)
>Kernel\CABFile.cpp (384)
>SetupDLL\SetupDLL.cpp (1526)
PAPP:Command & Conquer The First Decade
PVENDOR:Electronic Arts (http://www.EAGames.com/)
PGUID:66D6F3BD-CA23-41A4-9FA3-96B26B32528C
$11.0.0.28844
@Windows (9200) BT_OTHER 112.0

A quick google says this is an installshield error, and the best way to fix it is to delete C:\Program Files\Common Files\Installshield except... I don't even have that folder in the first place.

I've tried running it as an admin, didn't help at all.

I'm running Win 8.1 64bit.

oldbag · 24 Mar 2014 at 22:36

Hi, try googling, there are some youtube vids on it, not sure if they are what you need though.

marc2003 · 24 Mar 2014 at 22:38

have you tried running it in compatibility mode?

oldbag · 24 Mar 2014 at 22:41

I remember vaguely trying to get it to work on win 7 without much luck.

oldbag · 24 Mar 2014 at 22:42

Can you install it on a vm? If you have windows pro I think you can put xp on?

iviv · 24 Mar 2014 at 23:15

marc2003 said:
have you tried running it in compatibility mode?

Not sure why I didn't try that first, actually!

Just tried it in compatability mode for windows XP. The setup thing didn't even get as far as it had been before. It created the file setDD76.tmp which stopped responding immediately. Checking with process explorer, this is creating lots of ISBEW64.exe processes (Currently at 17) each using no CPU and minimal memory.

However, that did allow me to find where the ISBEW64.exe process is (For some reason C:\Program Files (x86)\Common Files\Installshield
I was sure I'd checked there, but apparently not.

Anyway, deleting the 'professional' folder inside there has fixed the problem. I blame me expecting it to be in the 64-bit program files folder.