Ok, I checked last updates to Windows Vista x64:

• started from an image with 8 or 9 latest updates missing : Adobe reader package is working in this configuration
• then installed each update, lauched Adobe Reader package again, reboot, then launch Adobe Reader package again.

Adobe reader package stopped working after installation of KB971512 and reboot: Runtime Error! of Microsoft Visual C++ Runtime Library.

I had to install 3 other update before KB971512, I don't know if a combination of update caused this issue or if it's just KB971512:

• KB973923 (security update for Microsoft Visual C++ 2005 SP1) <- I thought it would be this one
• KB960362
• KB972145

Uninstalling the update does not solve the problem sadly ...

Message was edited by: arodulr

Message was edited by: arodulr
I found update KB971513 also breaks Adobe Reader package, but not KB971514.

Well, I don't know if this is ThinApp related in fact: maybe a system installed version of Adobe Reader 9.1.3 also breaks when you install these two updates ?
Unfortunately I don't know how to check that because I don't have the Adobe Reader 9.1 installer anymore as version 9.2 is now available on Adobe web site.

I have to make a new package of Adobe Reader 9.2 to see if it works whereas updates KB971512 abd KB971513 are installed.

Thanks for your answer pbjork.
Does it mean a system-installed Adobe Reader would also break after these system updates ?
How can I know for sure which dependencies fail at runtime on destination computer ?
should I package on Vista 64 to run on Vista 64 for this package ? Our usual practice was to package every App on XP and until now we could also use the package on Vista 64. A common issue is Program Files vs Program Files(x86) on 64 bit systems but we usually install outside Program Files to a unique directory name (8.3 format) such as C:\READER9.

have a nice day
Alban

I agree: multiple packaging platform (OS and arch) gets complicated.

But, going back to Adobe Reader, how can I known which DLL is missing ? I did a log monitor trace but that's not really obvious which DLL is missing as there are many LoadLibrary calls failures and some of them may not mean real errors but just the app checking for capabilities I think.

thanks
Alban

That's a usefull link thanks pbjork! Dependency Walker seems to be the right tool to check broken dependencies.
However I don't think this a missing dll problem in this case, because the package is working if started from the Administrator account! How can libraries path be different from different accounts ?
I built again with latest version of ThinApp (4.0.4) and I still get the same behaviour except with 4.0.4 I get the runtime error almost immediately (ThinApp widget at the corner don't even show completely) whereas loading "seems" almost complete with 4.0.3 before it fails.
I going to test packaging from a Windows Vista x64 VM.
Does anyone ever got a ThinApp package which only work from Administrator account ?

thanks
Alban