index > Application Compatibility for Windows Vista > Network access seems to be locked down until reboot?

Network access seems to be locked down until reboot?

Installing my company's product (which uses an older WISE based installer) it seems that Vista RC1 is marking the path that the programs are installed in as not allowed to do network accesses. (If you run the programs and try to do socket or HTTP calls, they fail with host not found type errors (e.g. 12007 from WinInet).) But if you copy the installed files to a different path, they work fine, or if you reboot then they work fine. That seems wrong...either they should never work, or they should work from installation on, without a reboot.

So, what is going on?

William

wbardwel

I haven't seen this behavior before.

What is the name of your application? What build of Vista is this?

Thank you!

Microsoft AppCompat

MaartenB

This was with the RC1, our product is the Curl RTE at www.curl.com

William

William

wbardwel

So, when I use Standard User Analyzer, before rebooting (I.E. when the socket calls are failing) it says:

Privs: Requested SeLoadDriverPrivilege (the "Load and unload device drivers" privilege) with RtlAdjustPrivilege successfully

vfluapriv2!NS_LuaPriv::AuditPrivilege+154
vfluapriv2!NS_LuaPriv::VfHookRtlAdjustPrivilege+6e
mswsock!StartWsdpService+726
mswsock!WSPStartup+15b5
mswsock!+7517281d
WS2_32!WSASocketW+9d
WS2_32!socket+62

And S.U.A says that this is an Error 'Requested a security-relevant privilege.'

So what is the problem exactly? I am making a socket, not loading

a device driver, and it says that the permission check was successful.

William

wbardwel

Hello William,

I have been testing with your app and I have found that if I right click on surge.exe and tell it to run in Windows XP SP2 compat mode then everything works correctly. I have tested this from the "Program Files" folder and when installing the application into an alternate folder.

LouSha

> I have been testing with your app and I have found that if I right click on surge.exe and tell it to run in
> Windows XP SP2 compat mode then everything works correctly. I have tested this from the
> "Program Files" folder and when installing the application into an alternate folder.

wbardwel

So...after some experimentation, it looks like renaming our executables, and then renaming them back fixes the problem. That is clearly some sort of bizzaro bug in Vista RC1 5600 and 5728.

William

wbardwel

Hello William

LouSha

I only have the one test machine right now. On that machine with build 5728, the compatibility flag has no effect. However, renaming the executable and then renaming
it back fixes the problem. Rebooting fixes the problem. Even opening the executable for writing (with the exclusive lock that that implies) fixes the problem.

I saw the video, and doing similar things has no effect for me. However when I reinstall on this machine the binary is often already marked with the compatibility flag, so that is different...

William

wbardwel

reply 9