Paint3D missing dependencies?

[BadHellie]

Hi, not that I need it but I made a test (W10 22H2)
NTL says that Paint3D depends on Microsoft.UI.Xaml2.0 and VisualC 2015 UWP Runtime Package.
Both components are NOT removed in my setup, but Paint3D doesn't start when opened from Start Menu (silent, no dialogs), and if I select Open With Paint3D menu on a picture, the regular Paint program opens.
I don't feel to include my preset because my point is that, evidently, there are more dependencies than the two listed, which should be detected and updated accordingly. Again, I don't need Paint3D, but I felt to mention this nonetheless. Thx.

 

[garlin]

The last version of Paint3D is Microsoft.MSPaint_2024.2410.13017.0, which has dependencies on:

Microsoft.UI.Xaml.2.0​

Microsoft.VCLibs.140.00​

Without a working preset it's hard to determine if you inadvertently broke another dependency. Each Appx package has an AppxManifest.xml, which lists the minimum version of every dependent package.

 

[BadHellie]

Ok I'll include it. As you can see:
-Microsoft.UI.Xaml.2.0 is NOT removed (NTL shows NO DEPENDENCIES for it)
-Microsoft Visual C++ 2015 UWP Runtime Package is NOT removed (NTL shows NO DEPENDENCIES for it)
yet Paint3D does not start...
Maybe it also needs Microsoft 3D viewer (REMOVED), despite not listed as dependency ?
Again, not so serious since I don't need Paint3D, but I wondered if some dependency was maybe overlooked...

 

[garlin]

Is this preset applied to a live system, or an offline image?

For an offline image, it's missing some required components to finish OOBE.

                <c>cdpsvc 'Connected Devices Platform Service'</c>
                <c>cdpusersvc 'Connected Devices Platform User Service'</c>
                <c>microsoft.windows.cloudexperiencehost 'Out-of-box Experience (OOBE)'</c>

 

[BadHellie]

I am always working offline, never live.
Yes I have eradicated the OOBE because I really don't want to keep unwanted stuff in my ISO, not just disabling it (for fears some unwanted stuff or annoyances might pop up at some point... with Windows one never knows...)
But I still fail to understand why Paint3D should depend on OOBE, given NTL does not list any dependency on OOBE for Paint3D... sorry but certain things really still puzzle me

 

[tistou77]

I also remove OOBE in offline with autounattend file, no problem (and necessary files are protected in the background)
I keep the other 2, for among other things the context menu of the taskbar

I had tested Paint 3D and it worked, so not linked to OOBE (when I had tested) but surely another component

 

[garlin]

I am always working offline, never live.
Yes I have eradicated the OOBE because I really don't want to keep unwanted stuff in my ISO, not just disabling it (for fears some unwanted stuff or annoyances might pop up at some point... with Windows one never knows...)
But I still fail to understand why Paint3D should depend on OOBE, given NTL does not list any dependency on OOBE for Paint3D... sorry but certain things really still puzzle me

Paint3D is not related to OOBE. I'm pointing out you'll experience clean install problems by removing OOBE components.

You can safely remove OOBE on a live system, after your first logon is completed. There are user provisioning steps that OOBE does for your benefit, and skipping them tends to break UWP-based features.

 

[BadHellie]

I know. But I managed to have all "problematic" Windows components, like all Settings panels, Search, Taskbar and Start Menu working even with OOBE removed. Namely, I discovered that it is enough to keep Appx Deployment Service, Runtime Broker and Windows Update Service / Client License Service. This of course applies to my W10 version (19045.5073), your mileage may vary...
Btw, restoring Connected Devices Platform Service and Connected Devices Platform User Service was not enough to have Paint3D working. It has more unknown dependencies it seems, but as I said mine was just an academical point lol, I don't really need it and I won't go mad tracking such dependencies as I did for other vital components

 

[ammylisa]

I’ve had a similar experience, Microsoft Paint 3D wouldn’t launch even though all the obvious dependencies like XAML and VCLibs were intact. Honestly, it feels like some of these UWP apps rely on undocumented components or provisioning steps from OOBE or elsewhere. I don’t use Paint 3D either, but it’s definitely interesting how fragile it can be in a customized setup.

 

[tistou77]

Paint 3D is deprecated and removed from the Store since last year, maybe MS also removed files or other necessary in the CU since

Paint 3D is deprecated and will be removed from the Microsoft Store on November 4, 2024. How can I create an installer for this program I need help.? - Microsoft Q&A

Paint 3D is deprecated and will be removed from the Microsoft Store on November 4, 2024. Existing installations of Paint 3D will continue to work, but the app will no longer be available for download from the Microsoft Store. Users will no longer be able…

learn.microsoft.com

 

[garlin]

Paint3D works fine on a clean 24H2. I used DesktopAppInstaller to open the Appx package in Explorer, and it downloaded a copy of Microsoft.UI.Xaml.2.0, so maybe the older version of UI.Xaml is required for newer Windows releases.

24H2 runs on UI.Xaml 2.8.