• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Dell Command Update not copying forward prerequisites

Started by DylanF, January 27, 2026, 02:32:28 PM

Previous topic - Next topic

DylanF

Hello,

I am running into an issue with Patch My PC cloud where when a new version of Dell command update gets published it does not copy forward the .net runtime prerequisite. This is causing installs to fail and each time the entire app must be republished. Am I missing something here?

Michiel (Patch My PC)

Hi @DylanF, did you specify the .NET Runtime prerequisite as a dependency in the Cloud portal?

steadybird

Quote from: Michiel (Patch My PC) on February 26, 2026, 10:00:53 AMHi @DylanF, did you specify the .NET Runtime prerequisite as a dependency in the Cloud portal?

I am encountering the same problem.
When DCU started needing .NET as a prerequisite I saw PMPC posts at the time suggesting using .NET 8 as a dependency. I did this via the Intune portal on the app and it worked for the currently deployed app and update packages.

However, all future APPS and UPDATES from PMPC failed to bring forward the dependency that I had set.

Initially I deployed "Dell Command Update for Windows Universal 5.6.0" depending on "Microsoft .NET Desktop Runtime 8 8.0.24.35722 (EXE-x64)".

However, all future APPS and UPDATES such as the following no longer have the dependency.
Dell Command Update for Windows Universal 5.5.0 Rev1
Dell Command Update for Windows Universal 5.5.0 Rev2
Dell Command Update for Windows Universal 5.5.0 Rev3

Michiel (Patch My PC)

Hi @steadybird, you mentioned you created the dependency in the Intune portal. Have you tried specifying it in our Cloud portal instead?

DylanF

Quote from: Michiel (Patch My PC) on February 26, 2026, 10:00:53 AMHi @DylanF, did you specify the .NET Runtime prerequisite as a dependency in the Cloud portal?

Hey Michiel,

I did set the dependency in the PMPC cloud portal and it is specified in as a dependency in the portal when a new app is published. But it seems like it is not setting the dependency in intune which then requires republishing the entire app with the dependency. Next update, it publishes Command Update but not the dependency portion in intune.

steadybird

Quote from: Michiel (Patch My PC) on March 05, 2026, 01:20:15 AMHi @steadybird, you mentioned you created the dependency in the Intune portal. Have you tried specifying it in our Cloud portal instead?
Seems Dylan and I are slightly different though similar.

If I understand them correctly, they are using cloud publisher. My organisation is using the desktop publisher.