Creative Cloud Desktop Error 190 – KANC 7.0.7.25 incorrectly rejects Windows 10 22H2

Title:
Creative Cloud Desktop Error 190 – KANC 7.0.7.25 incorrectly rejects Windows 10 22H2

Description:

I am reporting a reproducible compatibility/deployment problem with Adobe Creative Cloud Desktop on Windows 10 22H2.

System:

• Windows 10 Pro 22H2

• OS build 19045

• Creative Cloud Desktop 6.10.0.252

• Adobe Native Client (KANC) 7.0.7.25

Creative Cloud Desktop repeatedly attempts to install/update KANC 7.0.7.25 and fails with Error 190.

The installation log reports:

“Sanity check for installation failed. Current OS version 10.0.19045 doesn't satisfy OS requirements.”

followed by:

“Error occurred in install product workflow with error code 190.”

I have reproduced the exact same problem in TWO independent environments:

1. My normal Windows 10 PC, with Adobe applications already installed.

2. A completely clean Windows 10 22H2 virtual machine, with no Adobe applications previously installed. I installed Creative Cloud Desktop from scratch and immediately reproduced the same Error 190.

This clean VM reproduction is particularly important because it rules out previous Adobe installations, corrupted Adobe components, Bridge, registry remnants, and other local configuration problems.

The VM installation log also shows that Creative Cloud successfully communicates with Adobe servers before the failure. The failure occurs specifically during the KANC OS requirement check.

Photoshop and Lightroom continue to work correctly on Windows 10.

Please investigate the deployment/OS compatibility requirements for KANC 7.0.7.25. It appears that Creative Cloud Desktop is attempting to deploy a component whose Windows requirement is incompatible with Windows 10 22H2, even though Creative Cloud Desktop itself and several Adobe applications still officially support Windows 10.

I can provide both the original installation log from my main PC and the installation log from the clean Windows 10 VM.

This appears to be an Adobe-side compatibility/deployment issue rather than a problem with my Windows installation.

Thank you.