Posted February 12, 2009
In short this is the fault of GOG, not Microsoft. Installers and other applications needing access elevation are supposed to incorporate metadata to tell Windows that they need administrative intervention (this can be implemented in a variety of ways, but the outcome is the same). Vista and 7 can detect this need in a fair percentage of non-compliant software via heuristic analysis, but this doesn't work for the GOG installer format. This change is immediately visible; software that incorporates the appropriate metadata or is heuristically detected will display a UAC shield in the corner of the icon. If the shield isn't there, UAC will kick in later on or sometimes not at all.
Because GOG isn't supplying this information and Windows can't detect it the installation process is disrupted, which you are seeing in the form of two integrity checks. If you force the installer to need access elevation (most easily achieved by right-clicking and choosing "Run as administrator") you will receive a UAC prompt immediately, and the integrity check should only happen once.
Because GOG isn't supplying this information and Windows can't detect it the installation process is disrupted, which you are seeing in the form of two integrity checks. If you force the installer to need access elevation (most easily achieved by right-clicking and choosing "Run as administrator") you will receive a UAC prompt immediately, and the integrity check should only happen once.