We have had the 32-bit fixup tool available for a while (to correct issues in App-V 4.6 packages saved out from AVE prior to version 2.2.6), but since the recent events there appeared to be a need to do the opposite as well.
Instead of having two little tools to do basically the same, the old fixup tool has now been superseded by a new tool called SetSftBitness that allows to do manual flagging of package as 32-bit or 64-bit. It’s super-simple to use, just supply path to the SFT as first parameter and either -32 or -64 as a second parameter, depending on which bitness you want to flag your package to.
So, for example, to mark package as 32-bit:
SetSftBitness.exe “c:\packages\Skype 5\Skype 5.sft” -32
Upon processing, the tool will rename old copy of SFT to the same name but with a .bak extension (e.g. “Skype 5.sft.bak”), and new re-flagged SFT will appear, encoded so that its internal version, GUIDs etc. are not updated so you can use it as drop-in replacement for your previous SFT file.
If flagging the package as 32-bit, the tool will also try to detect if it contains some obvious 64-bit originated artifacts – like Wow6432Node in the registry – that likely indicates that you are doing a mistake in re-flagging its bitness, and warn appropriately.