Page 1 of 1
Problems installing the NeoEE patch
Posted: Mon Apr 08, 2019 3:58 am
by fluxem
Hi,
first i want to apologize for my bad english. Im from germany....
Yesterday i tried to install the NeoEE patch on windows 10. i deactivated my Antivirus software.
It always stops at the beginning of the installation and says: „Please wait while windows configures NeoEE installer“
I waited for about half an hour, but nothing happened
I hope someone can help me - i really wanna Play this Game online
Re: Problems installing the NeoEE patch
Posted: Mon Apr 08, 2019 7:12 am
by Bogdan_xD
Deactivate Antivirus -> turn windows firewall off - > Re-Download the NeoEE Patch -> now it should work to install it -> add to antivirus and windows firewall exceptions the entire Empire Earth folder -> reactivate both antivirus and firewall
Re: Problems installing the NeoEE patch
Posted: Mon Apr 08, 2019 7:37 am
by fluxem
Bogdan_xD wrote:Deactivate Antivirus -> turn windows firewall off - > Re-Download the NeoEE Patch -> now it should work to install it -> add to antivirus and windows firewall exceptions the entire Empire Earth folder -> reactivate both antivirus and firewall
aaah, the firewall:)
I‘ll try it this evening. Thank you!!
Re: Problems installing the NeoEE patch
Posted: Mon Apr 08, 2019 12:26 pm
by fluxem
Hello again
now i tried again with deactivated Antivirus and Firewall.....
it stops at the same point: please wait while windows configures NeoEE installer....
do you have any other ideas?

Re: Problems installing the NeoEE patch
Posted: Mon Apr 08, 2019 4:47 pm
by Bogdan_xD
try to run the neoEE patch as the adminstrator
right click on it -> "Run as Administrator"
maybe you have your PC rights in some strange way set.
Re: Problems installing the NeoEE patch
Posted: Wed Apr 10, 2019 3:30 pm
by Neotje
I once had the problem that there was an old version of the installer in C:\Users\<username>\AppData\Local\Temp and it somehow tried to save that. Removing old installation files from there might fix it? I got an error saying something like "Installer(3) can not be found" although I was actually executing Installer(2). Renaming the thing I ran to "Installer(3)" also helped a bit, but was weird.