.NET Framework 4.8 on Windows Server 2019 - installation failes

Question

I have tried the solutions in other questions regarding installation failures of .NET Framework 4.8, but nothing have helped me so far.

The server is fully patched and rebooted. (Note! We use a WSUS but I do not know what updates are allowed or disallowed, maybe something is missing or I simply should ask the responsible person to allow .NET Framework 4.8 in the WSUS?)

As the server cannot reach the Internet, I have downloaded .NET Framework 4.8 offline installer from here:
https://go.microsoft.com/fwlink/?linkid=2088631

This is the error message from the install log (Note! I have tried to run the installation as Administrator):

Wait for Item (x64-Windows10.0-KB4486153-x64.cab) to be available
x64-Windows10.0-KB4486153-x64.cab is now available to install
Creating new Performer for Exe item
Created new ExePerformer for Exe item
Action: Performing Action on Exe at C:\5a9f17874cff9e1d385125\x64-Windows10.0-KB4486153-x64.cab
Launching CreateProcess with command line = dism.exe /quiet /norestart /online /add-package /packagepath:"C:\5a9f17874cff9e1d385125\x64-Windows10.0-KB4486153-x64.cab"
Exe log file(s) :
C:\Windows\logs\cbs\CBS.log
Log File C:\Windows\logs\cbs\CBS.log exists and will be added to the Watson upload list
Exe (C:\5a9f17874cff9e1d385125\x64-Windows10.0-KB4486153-x64.cab) failed with 0x80092004 - Cannot find object or property. .
Exe Log File: CBS.log
PerformOperation on exe returned exit code 2148081668 (translates to HRESULT = 0x80092004)
Action complete
Error 0x80092004 is mapped to Custom Error:
OnFailureBehavior for this item is to Rollback.
Action: Performing actions on all Items
Restart manager will not be used since the current operation is not install.
Action complete
Action complete
Final Result: Installation failed with error code: (0x80092004), "Cannot find object or property. " (Elapsed time: 0 00:02:46).

I have checked the temporary folder (in this case C:\5a9f17874cff9e1d385125) and the cab file is there.
I have tried to install the cab file separately by downloading it from Microsoft Update Catalog (https://www.catalog.update.microsoft.com/Search.aspx?q=4486153). It must be the last file in this case. But the install fails without any information. I guess there is a log somewhere, have not got that far yet.

Does anyone have any clues to what I'm doing wrong here?

Answer 1

I'm not sure how or when .NET Framework 4.8 was installed but now my application recognizes it which means all prerequisites are fulfilled.
Maybe 4.8 was installed from the beginning, it was just the application installer that didn't recognize it until I rebooted the server.

Anyway, thanks for the support! Hopefully this helps anyone else in the future!

Thanks,
Kristofer

Answer 2

Hi, I had the same "Cannot find object or property" error during .NET Framework 4.8 Developer Pack installation on Windows Server 2019.
I manged to find older version 4.8.3761.0 (newest one is 4.8.3928) and it went smoothly:

https://download.visualstudio.microsoft.com/download/pr/7afca223-55d2-470a-8edc-6a1739ae3252/c8c829444416e811be84c5765ede6148/ndp48-devpack-enu.exe

Unfortunately WSUS does not find the new version to update but it works to me so I will leave it with the older version for now.

Best
Dave

Answer 3

I had the same issue.
What worked for me is opening up Visual Studio Installer and installing the 4.8 dev pack from there.

Answer 4

Hmm, seems odd. I can see that some folks had luck installing the older version of .NET 4.8 and then let WSUS update it. Did you try that?

Personally I think you should talk to your admins about enabling it in WSUS. Since your server is managed on-premise anyway it makes sense to only allow installs through that. I have had no issue updating .NET framework versions other than 4.8 on WSUS-enabled servers so I suspect it is just an issue with WSUS and this particular installer.

Answer 5

Hi guys,

I was trying to fix this error during all the day. I needed to install the runtime 4.8, not the developer kit, so provided solution did not work for me.

After looking at a lot of pages and trying different installations, I finally was able to solve it using Microsoft .NET Framework Repair Tool. This tool unregistered and registered the MSI installer/service, and then it asked me for install again .NET. I trying and...magic was done! Installed without any problem.

Hope that will help anyone else,

Dani