TTW Installer isn't detecting my legitimate FO3

[generalmx]

I bought FO3 back when it was first released, before the GOTY editions existed, so all my DLC is either from Steam or GFWL. However what's odd is that not only does the installer not detect the DLC (despite being in the proper place), it doesn't detect my Steam-based FO3 installation at ALL. I of course verified the files through Steam and even deleted and re-downloaded them. My FO3 Steam appid is 22300 and I'd be happy to provide the MD5, CRC, or whatever validation hashes you may use. My only thought on why this may be occurring is that I have SteamLibaries on multiple HDDs and overall Steam is not installed under "Program Files (x86)" like it defaults to. Thanks for any help in advance. Below is the log entry from the installer:

 

[collapsed title=TTW Installer Log][10/19/2016 1:56:45 PM]    Version 2.7.5.0

[10/19/2016 1:56:45 PM]    64-bit architecture found.

[10/19/2016 1:56:45 PM]    Looking for Fallout3.exe

[10/19/2016 1:56:45 PM]        Fallout 3 not found, prompting user.

[10/19/2016 1:56:51 PM]    User selected: H:\Games\SteamLibrary\SteamApps\common\Fallout 3

[10/19/2016 1:56:51 PM]    Looking for FalloutNV.exe

[10/19/2016 1:56:51 PM]        Fallout New Vegas not found, prompting user.

[10/19/2016 1:57:04 PM]    User selected: C:\Games\Steam\steamapps\common\Fallout New Vegas

[10/19/2016 1:57:04 PM]    Looking for Tale of Two Wastelands

[10/19/2016 1:57:04 PM]        Default path found.

[10/19/2016 1:57:07 PM]    Checking for required files...

[10/19/2016 1:57:07 PM]    Fallout3.esm could not be found.

[10/19/2016 1:57:07 PM]    Anchorage.esm could not be found.

[10/19/2016 1:57:07 PM]    ThePitt.esm could not be found.

[10/19/2016 1:57:07 PM]    BrokenSteel.esm could not be found.

[10/19/2016 1:57:07 PM]    PointLookout.esm could not be found.

[10/19/2016 1:57:07 PM]    Zeta.esm could not be found.

[10/19/2016 1:57:07 PM]    Fallout - Meshes.bsa could not be found.

[10/19/2016 1:57:07 PM]    Fallout - Misc.bsa could not be found.

[10/19/2016 1:57:07 PM]    Fallout - Textures.bsa could not be found.

[10/19/2016 1:57:07 PM]    Fallout - MenuVoices.bsa could not be found.

[10/19/2016 1:57:07 PM]    Fallout - Sound.bsa could not be found.

[10/19/2016 1:57:07 PM]    Fallout - Voices.bsa could not be found.

[10/19/2016 1:57:07 PM]    Anchorage - Main.bsa could not be found.

[10/19/2016 1:57:07 PM]    Anchorage - Sounds.bsa could not be found.

[10/19/2016 1:57:07 PM]    ThePitt - Main.bsa could not be found.

[10/19/2016 1:57:07 PM]    ThePitt - Sounds.bsa could not be found.

[10/19/2016 1:57:07 PM]    BrokenSteel - Main.bsa could not be found.

[10/19/2016 1:57:07 PM]    BrokenSteel - Sounds.bsa could not be found.

[10/19/2016 1:57:07 PM]    PointLookout - Main.bsa could not be found.

[10/19/2016 1:57:07 PM]    PointLookout - Sounds.bsa could not be found.

[10/19/2016 1:57:07 PM]    Zeta - Main.bsa could not be found.

[10/19/2016 1:57:07 PM]    Zeta - Sounds.bsa could not be found.

[10/19/2016 1:57:07 PM]    Missing files detected. Aborting install.

90720F82[/collapsed]

Hash values for Fallout3.exe:

CRC32: 0B3862DB

MD5: 6AC349AB0980C713CD8FFB37199443F3

SHA-1: 7A6D3948B6D0BD7BE97B71769A14D3C084609331

Size: 14.3 MB (15,044,024 bytes)

Digitally signed by Zenimax Media Inc. on ‎Tuesday, ‎June ‎23, ‎2009 1:56:25 PM

 

Edit: Whoops, forgot my OS info! It's Windows 10 Pro 64-bit. The installer is being run as admin. There appear to be no file permission or UAC issues in ProcMon.

 

Edit 2: Well I did a whole bunch of nothing and now it decides to work. Huh. Nevermind? You can delete this thread.

[jlf65]

One issue with running in 64-bit mode is that these old games (or the tools meant to work on them) don't like the registry entries made for them. In order to get them working (xEdit in particular), you need TWO registry entries. This might be your problem. It's particularly true if you use a custom install directory like I did. Here's the registry entries I made for my install of FO3 (GOTY edition). Cut-n-paste this into a file called something like Fallout3.reg and run it in Windows to make the registry entries... after editing the path for where you installed it, of course.

[quote]Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\Bethesda Softworks\Fallout3]

"Installed Path"="C:\\GAMES\\Bethesda Softworks\\Fallout 3\\"



[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bethesda Softworks\Fallout3]

"Installed Path"="C:\\GAMES\\Bethesda Softworks\\Fallout 3\\"



[/quote]

The first entry is a standard 32-bit entry, and the second is a standard 64-bit entry. You need BOTH for things like xEdit to work properly in 64-bit Windows, and xEdit is part of the installer for TTW.

 

[generalmx]

Well I did a whole bunch of nothing and now it decides to work. Huh. Nevermind? You can close or delete this thread. I wonder if it's because this time I was troubleshooting it with ProcMon open--I've had that happen before where just having ProcMon open fixed a bizarre issue.

[jlf65]

Yeah, that's one of the great features of Windows - bizarre problems that are solved by doing things like chanting Emily Dickinson poetry while waxing the north side of the computer.

[Royhr]

Well actually all you really need is a Buddha statue that has Bill Gates' face. Then when you have any issues related to windows you just need to rub the statue's belly and maybe chant Bill Gates' name a few time.... Works for me..