All .dll files have an error

[NighthawkAquila]

So I went to load FSX today and all of a sudden everything stopped working, I get this message saying FSX encountered an issue with VRS_TacPack.dll, Milviz_Weapons.dll, and FSUIPC.dll so none of my add-ons work. this is obviously an issue with the game not the add-ons as they all stopped working at the same time. I hadn't changed any files in the last week, and it just stopped working. Please help, I've also put a thread on the TacPack forums if you want to see the errors.
https://forums.vrsimulations.com/forums/phpBB3/viewtopic.php?f=82&t=19476&p=127280#p127280

[NighthawkAquila]

Originally posted by Erazer:

Have you verified the integrity of your FSX game files recently?

Maybe run sfc /scannow to check out your OS?

Yeah I did and it said some thousand files needed to be verified, did that, tried running it and still have the same issue.

[NighthawkAquila]

Originally posted by Erazer:

Originally posted by Nighthawk -Aquila Squadron-:

Yeah I did and it said some thousand files needed to be verified, did that, tried running it and still have the same issue.

One thousand missing files is way too excessive...

Never heard of such a large discrepancy before now.

I would suggest that you need to re-install to get a good result as you don't have a drive image to restore with. [Keep copies of essential configuration files, etc.

E.G. Copy the entire X:\Users\YOU\AppData\Roaming\Microsoft\FSX folder and the entire Flight Simulator X folder in your Documents folder. This folder has a 'Controls' sub folder with Standard.XML which has all of your custom keyboard and controller mappings.]

https://steamcommunity.com/app/314160/discussions/0/1813170373221711244/

Last time I ran a verification on my installation it checked out with no files missing so I made an up to the minute drive image. By far, the fastest way to recover both OS and FSX

You running FSX on its own partition?

[/quote]

I had a large amount of scenery that I deleted about a month ago so I'm sure that was part of it, and alright I'll try that, appreciate it man.

[NighthawkAquila]

Originally posted by Erazer:

Originally posted by Nighthawk -Aquila Squadron-:

I had a large amount of scenery that I deleted about a month ago so I'm sure that was part of it, and alright I'll try that, appreciate it man.

Did you get all of the scenery registry keys cleaned out?

I generally use CCleaner but have had occasion to use RegistryFinder 2.3.1 to remove more than 27,000 registry keys from a P3D installation. Just need to be very careful to:

1. Have a good backup.
2. Identify the keys correctly before batch deleting.

I did not, probably why it needed verification.

[NighthawkAquila]

Originally posted by Erazer:

It is just when you say that you "deleted" the scenery rather than uninstalled it that I suspect all manner of reg keys left behind.

Verification will not remove reg keys - IF - that is the case here.

Do you use CCleaner or another registry cleaner?

Nope, I'll have to take a look at one of them, as of right now I'm reinstalling FSX, I made copies all of my important stuff though, and yeah that's the case. I had meant if it left them behind it would probably detect that it would detect them as files needing verification right?

[NighthawkAquila]

Originally posted by Erazer:

Originally posted by Nighthawk -Aquila Squadron-:

[Nope, I'll have to take a look at one of them, as of right now I'm reinstalling FSX, I made copies all of my important stuff though, and yeah that's the case.

I had meant if it left them behind it would probably detect that it would detect them as files needing verification right?

Only if the scenery was downloaded from Steam.

If it was 3rd party scenery, then no.

Ah okay, it was FSX Global 2010 and a couple others so that could have contributed to it

[NighthawkAquila]

Originally posted by Erazer:

Originally posted by Nighthawk -Aquila Squadron-:

[Nope, I'll have to take a look at one of them, as of right now I'm reinstalling FSX, I made copies all of my important stuff though, and yeah that's the case.

I had meant if it left them behind it would probably detect that it would detect them as files needing verification right?

Only if the scenery was downloaded from Steam.

If it was 3rd party scenery, then no.

Well f**k I deleted and reinstalled *everything* flat out, and then attempted to install TacPack and the SAME THING HAPPENED

[Erazer]

Originally posted by Nighthawk -Aquila Squadron-:

Well d**n I deleted and reinstalled *everything* flat out, and then attempted to install TacPack and the SAME THING HAPPENED.

Bad vibes...

Not trying to be 'clever', but that is precisely why I make drive images...

When the initial installation was installed and verified to be 100% intact and correct when thoroughly tested I would have made a preliminary drive image labelled FSX SE INITIAL INSTALLATION so that, if any subsequent installation of add-ons went wrong, I could restore the base installation, and maybe find out why, before trying again.

Yes I know, all very well to be 'wise' in retrospect and come over as a clever ♥♥♥♥, it is just that past and sometimes bitter experience has taught me that it is better to err on the side of caution and be certain of any installation before proceeding with third party add-ons.

It would be a totally different scenario if MS had continued to develop FSX and supply extension packs with new and better missions, scenery, and new up to date aircraft.

P3D v4.4 or try again?

Have to be really meticulous and not rush things, taking it one step at a time IMO.

This is all that I can offer:

https://steamcommunity.com/app/314160/discussions/0/1813170373221711244/

I keep the drive images on 2 x 1TB WD external USB drives which are disconnected when not in use for safety.

[NighthawkAquila]

Originally posted by Erazer:

Originally posted by Nighthawk -Aquila Squadron-:

Well d**n I deleted and reinstalled *everything* flat out, and then attempted to install TacPack and the SAME THING HAPPENED.

Bad vibes...

Not trying to be 'clever', but that is precisely why I make drive images...

When the initial installation was installed and verified to be 100% intact and correct when thoroughly tested I would have made a preliminary drive image labelled FSX SE INITIAL INSTALLATION so that, if any subsequent installation of add-ons went wrong, I could restore the base installation, and maybe find out why, before trying again.

Yes I know, all very well to be 'wise' in retrospect and come over as a clever ♥♥♥♥, it is just that past and sometimes bitter experience has taught me that it is better to err on the side of caution and be certain of any installation before proceeding with third party add-ons.

It would be a totally different scenario if MS had continued to develop FSX and supply extension packs with new and better missions, scenery, and new up to date aircraft.

P3D v4.4 or try again?

Have to be really meticulous and not rush things, taking it one step at a time IMO.

This is all that I can offer:

https://steamcommunity.com/app/314160/discussions/0/1813170373221711244/

I keep the drive images on 2 x 1TB WD external USB drives which are disconnected when not in use for safety.

Yeah, I can see where that would have been a good idea, plan to do so in the future, I really appreciate your help man. Thank you for your patience.

[Erazer]

No problem.

Let us all know what you plan to do, if you will.