I’ve got a fresh-out-of-the-box Dell Optiplex running Win10. I’m trying to install Visio and SharePoint Designer 2010 on it. But every time I run the installer for either one, it will extract the files and then display an error message: “The installation package is in a language not supported by your system.”
I have a strong feeling that what is meant by “language” is not “human” language, but rather “computer” language. eg. trying to install Python instead of C
Hadn’t thought about it from that angle. Regardless, it’s preventing me from installing software that the developers need in order to do their job. Any idea on how I can remedy it?
We are running 64-bit Windows and the SPD is 32-bit with SP1. Did not know Office had to be installed, first, for Visio. I’ll see if I can get Office on there (didn’t even try with the problems I’ve been having, so far.)
Agreed. I can understand there being problems trying to install an app for one OS on a different OS. But a Windows app on a Windows OS should be mostly painless as long as the right installer is used.
Searching for that error message brings up this which looks related - and does indeed have to do with “human” language.
The only thing that I can think of is that I believe the Win10 comes with a trial version of Office 2016, and the installers are for 2010. But I’ve gone into Windows settings and uninstalled the Office 2016 apps (English, French, and Spanish.) Still getting the message.
Could also be read as: Error reading file… so I stopped.
I think you can solve this.
It could be as simple as a permission denied due to a corrupt file or its meta info in the package or a target directory or even a setup fault like trying to overwrite a system file. A quick run-through:
When the installer stops to show the message, it hasn’t yet deleted the installation files. So if you let the installer stay put showing the error message, and not abort or finish the process, you can try find out the real reason why it stopped.
The Windows installer’s first step should be to unpack all the files to a setup directory in current user’s temp folder(s). It then reads the INI file(s) to follow the setup instructions. If there is a log file (it should be one or the installer writes its own elsewhere), you might be able to see in what stage the installer failed. You should be able to read it in Notepad.
Next level is to read the ini-files to check what the installer was ment to do and find out what failed. A hex editor can show the setup instructions between the nul bytes.
Please mind I have no experience of Windows 10. I’m in deep water here, but I guess its installer is much the same.
I managed to install sharepoint designer on my win10 (64bit) laptop. I think i had to install the 32bit version. I’m not sure i have much that can help but the version i have is SPD 2007 SP3 MSO(12.0.6785.5000). Don’t know if that is any help at all.
I am rather glad though that i didn’t need to use it in the end as i transfered department. I couldn’t stand trying to do anything on sharepoint.