3777573 - MDK Windows Client Generator Ignores Fourth Digit of AppVersion and Falls Back to 3.0.3.0 - SAP Service and Asset Manager (SSAM)

The MDK Windows client generator consistently outputs a fixed baseline version (for example, 3.0.3.0) for the UWP package, regardless of the custom version configured in MDKProject.json, ClientSettings.json, or BrandedSettings.json.

• The Package.appxmanifest in the generated output shows Version="3.0.3.0" instead of the intended revision.

• The generated MSIX file name defaults to the baseline (for example, mdkWin_3.0.3.0_x64.msix) and does not reflect the configured AppVersion from MDKProject.json.

• Changing the version configuration to a 4-digit sequence (such as 3.0.3.1) has no effect, and the generator forces the final digit back to 0.

SAP Service and Asset Manager (SSAM) Windows

SAM Windows, MDK Windows, create_client.ps1, AppVersion, Package.appxmanifest, msix, UWP, versioning fallback, 3.0.3.0, --revision, Branded Settings, MDKProject.json, mdk windows client, version 3.0.3.0, custom client, branded client, service and asset manager, versioning, mdk windows sdk, ClientSettings.json, BrandedSettings.json, AppPackages, mdkWin, AppxManifest.xml, 4 digits version, fourth fragment, revision number, script parameter, Powershell build script, Windows SDK build tool, application version reset, version mismatch, build override, Microsoft Store policy, app package requirements, sideloading deployment, MDM delivery, Intune deployment, bundle versioning, build automation fallback, version digit dropped, fourth digit ignored, asset manager client build, metadata version mismatch, SAM_BRAND_WIN , KBA , MOB-APP-SAM , SAP Service and Asset Manager , MOB-MDK-MDC-WIN , Mobile Development Kit (MDK) Client SDK for Windows platform , Problem