Two .net dependent apps will not install

New Dell XPS desktop running 24H2 out of the box. I've confirmed that .net 4.8 and 3.5 are installed (in "turn windows features on and off"). I have the following issue with two apps:

• PlayOn - The app will not install. It starts the installation process and then backs out. The log is of no help to me or to PlayOn support (they can't figure out the issue).
• Brother iPrint & Scan app. I was able to install the app when I first set up the computer three weeks ago. All good. There is now an update available. When I try to install the update it first uninstalls the prior version of the app and then tries to install itself. The uninstall works, but it does not complete the installation, and in the end I have no iprint & scan app installed.

A couple of notes:

• Both apps seem to require .net 6.0.25 and I can confirm that they do install it (web server hosting, asp, runtime). I've compared with another computer running the same apps (successfully) and the .net apps are correct and the same on both systems.
• Tech support for both Brother & PlayOn cannot figure out what the problem is.
• Yes, the fact that iprint & scan installed 3 weeks ago but won't now is a question mark.
• I do have a day old Macrium image that I've used, so iPrint & scan works (with the "old" version of the app), and for now I've disabled "check for updates" in that app.
• I've tried uninstalling all v. 6 .net apps and reinstalling manually as well as uninstalling them and allowing the apps to install .net. No joy.

I'm open to any ideas. Thanks in advance.

I just checked my computer and it has the latest as shown available on
Looks like .NET Framework 4.8 is the latest.

.NET seems to be something else, haven't experienced it yet.

Try downloading and installing the .NET 6.0 SDK from here:


It includes all of the runtimes you need for that version of .NET. One of them may be a dependency for your programs. It's worth a shot anyway. I realize that you tried installing .NET 6.0, but you may not have all of the runtimes that you need. The SDK will install all of them.

EDIT

I should note that .NET is very strange at times. .NET 4 is not the same as 4.8, which is not the same as 6.XX or 7.0 (which is deprecated), or even 8.XX.

The different versions are there to support different versions of the C# runtime and language version, and you must have the specific one that supports the language version that your app was written in. If you don't have it, you get problems like you are having right now.

After some thought, I have another set of suggestions that may help now and in the future:

1. Make sure .NET 3.5 is working on your computer (Use the System window > Add or remove Windows features > tick the box beside .NET 3.5)
2. Install .NET versions 4.X, 4.8, 6.X, 8.X, and 9.X where X is the subversion number. Make sure to install the SDKs for all of them rather than just the runtimes.
3. Check the Microsoft .NET pages for any clues to troubleshooting this problem. .NET troubleshooting
4. Report back with the exact error messages you get. Screen shots are helpful here.

I have every .NET SDK installed in my system as I do a lot of development work. I never have an issue with installing a .NET program. You don't have to go that crazy. Just install the ones I listed and see how it goes.

I'll give it a shot tomorrow and report back Catnip. Thanks.

allan said:

• I'm open to any ideas. Thanks in advance.ntimes Available - v

Click to expand...

May I suggst that you run this - Updated Visual C++ Redistributable Runtimes Available - v 0.85.0

​

IanMosley said:

May I suggst that you run this - Updated Visual C++ Redistributable Runtimes Available - v 0.85.0

​

Click to expand...

Just be aware that Visual C++ does not use .NET. They are totally different technologies and operating environments. .NET is more focused on Windows UI apps and database integration and insulates the programmer/user from a lot of the minutiae that is under the hood in Windows.

And while you do and can write Windows programs in Visual C++, it takes a more bare metal approach by delving more into the intricacies of Windows programming. Use it if you want full control over your hardware. In fact, Windows is written in C++.

Just note that adding the C++ runtimes will not affect a .NET installation or problem. They are not the same.

But while we are here and talking about it, any user should have the latest C++ runtimes installed in their PC, so @IanMosley great idea, but it will not help the OP with this problem in this case.

allan said:

I'll give it a shot tomorrow and report back Catnip. Thanks.

Click to expand...

I am hoping to hear good news tomorrow then.

@allan If you don't have success after the suggestions above, do the ol' VoiceWarmUpX thing for MSI logging. It'll generate a really verbose log for the installation, but it should have some clue in it as to what's wrong.

In HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer, create a string value called Logging, with the data voicewarmupx. When you run setup again, you should get logs in %TEMP% named for the application and with a timestamp, e.g., PlayOn_Home_2024something-something.

After the installation, you'll want to remove this registry entry, as it creates verbose logs every time Windows Installer does something, and it kills performance.

No go. However, I did check the log files for both apps and found the same error in both:

Failed to configure per-machine MSI package.

I tried taking ownership of the temp folder, the folder from which the executables were being run, and the destination folders (where possible). I also insured Windows Installer Service is running (along with its dependent service). I've attached the log generated by PlayOn during the failed install. I'm guessing the problem is similar to iprint & scan.

The error message in that log is the generic (unhelpful) 1603, which is ERROR_INSTALL_FAILURE (thanks, Windows Installer, we know that much).

Did you get the more verbose logs? This one is too short.

Thanks pseymour. Verbose logs attached.

The problem is in this custom action in their installer, whatever it does.


Can you see if C:\Windows\Installer\MSI54DB.tmp- exists and is empty? SFXCA, which is doing the extracting, requires the folder to already exist and be empty.

It did not. I just created it, took ownership of it, and tried again. No joy.

Hmm, this is troubling. I'm able to install it in a fresh VM, so it has to be something like anti-malware interfering or something Dell put on the machine causing a conflict.

While I do have MBAM (pro) installed, it is not resident (on demand only). Last week I uninstalled Bitdefender, rebooted, and tried the install with no luck. I'm one of these guys who doesn't like failure on a computer and will keep trying possible fixes. But as you say, this one is troubling. I'm pretty much out of ideas (which, of course, is why I posted).

Well, if anything else comes to mind please don't hesitate........... Thanks for trying!