SBIG 64 bit Driver on ARM64

I've just experienced a related failure with 4.0.5 Win11 Parallels ARM64. The various drivers appear to load by the checker, but the error occurs at the end. The Device Manager is then showing a yellow warning triangle badge, and attempting to connect to the STX16803 yields 'no driver found'. Any thoughts would be wonderful.

 

Here is a screenshot of the error. . .

 

Yes, current generation Mac mini M4 running a Parallels hosted Windows 11 ARM version.

 

Thanks for suggestion Colin, but it would be a little like putting gasoline in a diesel engine. Parallels only supports the ARM64 Windows 11 version on an M4 Mac. Also, my environment includes multiple loaded and working legacy .inf drivers (eg., Gemini Rotator/Focuser, DDW FTDI serial converter, Paramount ME driver, and others). But my apologies for not providing the initial error generated by the installer: "Authenticode(™) signed catalog has not yet been established as trusted". My research indicates the problem nor solution is not complicated. Here is the AI Overview:

AI Overview

Addressing the "Publisher of an Authenticode(™) Signed Catalog Has Not Yet Been Established as Trusted" Error in Parallels Windows 11 ARM64
When attempting to install software or drivers within a Parallels Desktop Windows 11 ARM64 virtual machine, you may encounter the error "The publisher of an Authenticode™ signed catalog has not yet been established as trusted". This message indicates that Windows is preventing the installation of software or drivers because the associated digital signature (Authenticode™) is not recognized as belonging to a trusted publisher. This often occurs when installing drivers or applications from developers that have not undergone Microsoft's rigorous certification process (like WHQL signing) for Windows ARM64.

Understanding the problem

• Authenticode™ and digital signatures: Authenticode™ is a Microsoft technology that uses digital signatures to verify the authenticity and integrity of software and drivers. A signed catalog indicates that the software or driver package has been signed by a trusted authority.
• Trusted publishers and certificates: Windows maintains a list of trusted publishers through a hierarchy of digital certificates. When installing software or drivers, Windows checks the digital signature against these trusted certificates to ensure the authenticity and integrity of the software.
• Stricter policies on Windows ARM64: Windows 11 on ARM64 employs stricter driver signing policies compared to x64 versions of Windows. This means that even if a driver or software is signed with an Authenticode™ certificate recognized on x64 systems, it might not be recognized on ARM64 without further trust establishment. This stricter enforcement is likely related to the tighter security requirements for ARM64 devices.