Installation error: ni-metauninstaller (22.0.0.49152-0+f0)

[EuanM]

The issue persists.

[WesW · Accepted solution]

EuanM - thanks for posting the MSI level debug log - as that's where the problem is occurring. This ni-metauninstaller is common across all products and versions, and is also often first to install, so that's why you're seeing it in all cases. 

Looking carefully at the log, there is this failure:
SHGetFolderPath(CSIDL_COMMON_DOCUMENTS) failed with error 2147942402

The log doesn't have all of the details, but what looks to be happening is that the MSI tries to lookup the Windows location for Common Documents, but it fails because this location doesn't exist, which causes the MSI itself to fail when it can't resolve all directories.

This article give one possibility for Common Documents being broken. As such, my suggestion is to open a Windows command prompt, and try the following:
echo %public%
dir %public%
dir %public%\documents

Share the output of those commands, but if either of the latter two return something like "file not found", then the solution could be adjusting the value of the PUBLIC property as that article describes (or making what directory PUBLIC points to available, such as if it's a network location).

[WesW]

To add, looks like there was a similar issue reported in 2020 here.

As such, also check that the following registry key value points to a folder that exists and is accessible by this user:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders, Common Documents

[EuanM]

Hello all.

This was the problem, it was not able to find the common documents. Once access was restored, the installation proceed smoothly.

[heel]

I am facing the same issue on Win10. How/where will this logfile be located?

Edit -

Ok found it: C:\Users\<user name>\AppData\Local\National Instruments\NI Package Manager\Logs\

Edit-Edit:

Running Ni Package manger as admin removes the error related to ni-metauninstaller. But despite no error: TDM importer for MS Excel still does not work