/build/static/layout/Breadcrumb_cap_w.png
11/24/2018 191 views

Hi all, 

i am new to application packaging , i have an package which has pre requisite it is Microsoft .NET framework 4.7.1

i deployed that package in SCCM with dependency microsoft .NET Framework, actually while installing the application from software center it has to restart to complete the installation, 

the issue is that now it downloads , installs and restart correctly through software center  in windows 7 64 bit , but in windows 10 it fails in restarting the machine.

the error is  when i click on restart in software center then it pop ups an error 

" SOFTWARE CENTER CANNOT BE LOADED.THERE IS A PROBLEM LOADING THE REQUIRED COMPONENTS FOR SOFTWARE CENTER. YOU CAN TRY LAUNCHING SOFTWARE CENTER AT A LATER TIME. IF THE PROBLEM CONTINUES, YOU CAN CONTACT YOUR HELPDESK."


But if i manually test the package it works fine in the same windows 10 machine.

0 Comments   [ + ] Show comments

Comments


All Answers

0

Most likely the case, ConfigMgr client uses .Net 4, its upset cos you pulled the rug out from underneath it by updating it.

What versions of .Net are you updating updating from for each o/s?


Work out which package is messing up Software Center by testing the package separately through Software Center.
At times, the new application can mess up the client (as it interacts with one of its components), ive had it happen about half a dozen times in the last five years  - a very uncommon problem.


Also check the AppEnfore/AppDiscovery logs, to see what the client thinks is going on too. 

Answered 11/25/2018 by: rileyz
Red Belt

0

When using web fora, it's become a bit of a standard to make the topic 'Subject' text accurately reflect the content of the post. Your text implies that your question is about Application Packaging in general whereas it's very specifically about one issue.

Next time, try going with the text 'PC restart via Software Center fails after installing .Net Framework'.

Answered 11/28/2018 by: VBScab
Red Belt

  • Good call VBSCab - I've updated the title to your suggestion.