Re: Win11 22H2 and CoInstallers

[Paul Durrant <xadimgnik@xxxxxxxxx>]

On 28/06/2023 15:33, Owen Smith wrote:
> Looks like the HLK tests for Win11 22H2 fail if you specify a coinstaller.
> I've not dug through the full implications of this yet, but looks like 
> the coinstallers will need removing going forwards.
Have Microsoft come up with an alternative (after a decade of not doing 
so)? The co-installers were introduced for a good reason, and while we 
managed to move *most* of the stuff they used to do into the driver, we 
didn't manage to do everything.
I thought we still had a coinstaller in XENVIF and XENVBD too. I'd have 
to check though.

  Paul

> (snippet of DF - InfVerif INF Verification logs)
>    <Warn File="" Line="-1" UserText="Code 1324, 
> C:\Windows\System32\DriverStore\FileRepository\xenbus.inf_amd64_17e41dd0114cba4e\xenbus.inf line 32: [Version] section should specify PnpLockdown=1 to prevent external apps from modifying installed driver files." CA="156088" LA="157185">
>      <Data>
>        <WexTraceInfo ThreadId="508" ProcessId="8128" 
> TimeStamp="8686668616" LogSessionId="1" SessionTraceCount="89" />
>      </Data>
>      <rti id="795664978" />
>      <ctx id="815116702" />
>    </Warn>
>    <Error File="" Line="-1" ErrCode="0x0" ErrType="" ErrorText="Error 
> 0x00000000" UserText="Code 1303, 
> C:\Windows\System32\DriverStore\FileRepository\xenbus.inf_amd64_17e41dd0114cba4e\xenbus.inf line 154: Found legacy AddReg operation defining co-installers (CoInstallers32)." CA="158863" LA="159423">
>      <Data>
>        <WexTraceInfo ThreadId="508" ProcessId="8128" 
> TimeStamp="8686670389" LogSessionId="1" SessionTraceCount="90" />
>      </Data>
>      <rti id="795664978" />
>      <ctx id="815116702" />
>    </Error>
>
> Owen