So I figure since even our resident Windows fanboys are throwing out problems here, I might as well too :-)

I'm not quite sure what to make of this particular one, and thankfully the problem will be resolved soon with the user in question getting a new machine soon. But I'm still curious to see if anyone else has seen similar, and what the fix was.

Problem: Windows appears to be ignoring the "Start in" setting of shortcuts. We have a system set up where unapproved versions of our product are synced into a folder, instead of over the existing approved binaries in the root folder of the product. Then a shortcut exists to run the binary from the unapproved folder, and start in is pointed at the product root folder. This works fine for nearly everyone, but on this one system, it complains about not finding DLLs needed to run. The DLL in question is in the root folder, and moving it to the unapproved folder allows it to work. The particular DLL is not a windows DLL, so it's not conflicting in a weird way.

To clarify, here is the setup:

The unapproved binary is here:
c:\Product\unapproved\product.exe

Then DLLs are here:
c:\Product\required.dll

And the shortcut is to C:\Product\unapproved\product.exe, with Start in set to C:\product\.

I've stopped the anti virus to eliminate it from interfering, and the problem persisted. I tried replicating the setup with other executables, by moving one into a different folder, making a shortcut, and ended up with the same behavior where the executable wouldn't run. So it's not specific to our product either.

Any ideas?