Sanctuary Device Control 4.x.
Autorun fails because...
We have implemented a shadowing filter to reduce the amount of useless read shadowing (mainly coming from just browsing folders through Windows Explorer), that's why Sanctuary intercepts a couple of functions (one being GetFileVersionInfoSize) and issue an access check to know if read is enabled for shadowing (filename or full shadowing). In case shadowing is enabled, we proceed to return 0 to the calling application as if the file queried didn't have version info. So setup.exe (which is the executable that autorun starts) does not work when read shadowing is enabled (filename or full shadowing).