Hey guys,

I posted this over on the Knife Edge forums but figured I would try here as well.

Recently bought RF8 and can't seem to get it installed. Trying to install results in KEError 16114 followed by KEError 16118. I searched and found a couple threads discussing these exact errors but a concrete solution wasn't presented.

I have a Lenovo Thinkpad E580 running Windows 10. I have tried re-downloading the RF8 installer as well as attempting to install the simulator via a different admin account (someone posted that RF8 doesn't like spaces in account names). Neither of these two methods worked.

So if anyone out there has figured out a different workaround to successfully install RF8 I am all ears!

Thanks,

Neil

Have you received my PM and or email?

Originally Posted by acerc

Have you received my PM and or email?

Yes - and I replied to your email....

But on my error, it states … "KEError: 16114: Failed loading C:\Users\Tim\DirectX\dsetup.dll"

Which is totally wrong, since the pathname should have been "C:\Users\Tim Green\DirectX\dsetup.dll"

I don't have a directory named "Tim" anywhere on my system - so where did the installer get that path from.

The message appears first thing after the installation is started.

Originally Posted by Neil4

Hey guys,

I posted this over on the Knife Edge forums but figured I would try here as well.

Recently bought RF8 and can't seem to get it installed. Trying to install results in KEError 16114 followed by KEError 16118. I searched and found a couple threads discussing these exact errors but a concrete solution wasn't presented.

I have a Lenovo Thinkpad E580 running Windows 10. I have tried re-downloading the RF8 installer as well as attempting to install the simulator via a different admin account (someone posted that RF8 doesn't like spaces in account names). Neither of these two methods worked.

So if anyone out there has figured out a different workaround to successfully install RF8 I am all ears!

Thanks,

Neil

Originally Posted by Tim Green

But on my error, it states … "KEError: 16114: Failed loading C:\Users\Tim\DirectX\dsetup.dll"

Which is totally wrong, since the pathname should have been "C:\Users\Tim Green\DirectX\dsetup.dll"

I don't have a directory named "Tim" anywhere on my system - so where did the installer get that path from.

The message appears first thing after the installation is started.

Sorry to hear that Tim - I still haven't got RF8 downloaded on my laptop....

i didnt have any issues when i installed it. did you uninstall on the first profile using windows file manager?
i would scrub the registry for rf8 entries and try again

Originally Posted by Neil4

Hey guys,

I posted this over on the Knife Edge forums but figured I would try here as well.

Recently bought RF8 and can't seem to get it installed. Trying to install results in KEError 16114 followed by KEError 16118. I searched and found a couple threads discussing these exact errors but a concrete solution wasn't presented.

I have a Lenovo Thinkpad E580 running Windows 10. I have tried re-downloading the RF8 installer as well as attempting to install the simulator via a different admin account (someone posted that RF8 doesn't like spaces in account names). Neither of these two methods worked.

So if anyone out there has figured out a different workaround to successfully install RF8 I am all ears!

Thanks,

Neil

First please note that I got mine working by creating a new admin user account called "test" (no spaces in the user name IOW). And that the downloaded RF8 installation program installed into "test" just fine.

I've since removed the user account "test", and run RF8 from my normal user account named "Tim Green". It also updated fine from my "Tim Green" account.

I have DX12 installed, of course, since that is what Win10 is running these days.

Two questions ...
1) What was the text of the message included with the first error - the KEError 16114?
2) When you tried creating another admin account with only one word for the username - did the installation fail in the same place and the same way (same errors) with the same text messages? Or did it fail differently?