Ask Your Question
0

Installation of 6.1.0 in Win10 fails "The system cannot open the device or file specified."

asked 2018-09-04 12:47:56 +0200

MikeYates gravatar image

updated 2018-09-11 10:29:41 +0200

There are various "Internal errors" which follow, usually 2755 110 I have tried running from Admin Cmd. I have tried swiching Defender Controlled folders. I have verbose logging but it's still unclear what's happening. I had 6.0.5 installed and was hoping to update. I uninstalled and now the old 6.0.5 MSI fails likewise!

Since found due to particular security setting.

edit retag flag offensive close merge delete

Comments

look here: https://support.microsoft.com/en-us/h...

Otherwise, try turning your virus protection off.

ebot gravatar imageebot ( 2018-09-04 12:51:24 +0200 )edit

Most of these bugs are known in this forum. Enter in the search bar, e.g. "Error". You will be given many answers.

ebot gravatar imageebot ( 2018-09-04 13:40:45 +0200 )edit

Sorry, ebot, it was neither antivirus nor "smartscreen" download protection. Neither of those would have reached the "device or file" error, after offering the desktop icon.

Perhaps LibreOffice should (at least try to) translate windows errors like 2755 ?

MikeYates gravatar imageMikeYates ( 2018-09-08 10:08:38 +0200 )edit

It is not up to LibreOffice to translate or interpret OS error messages. LibreOffice would have to handle many OS types and versions. The USER has a decision-making power what he wants to use and also a responsibility. There is no 100% perfect technique.

ebot gravatar imageebot ( 2018-09-08 10:20:07 +0200 )edit

Well, then, perhaps a warning to move the MSI from Downloads to Windows (requires a permission) if using Win10-1803. That is if I'm right - I haven't fully researched it. Perhaps a tweak to the MSI would not require a folder with SYSTEM rights? Who does the Win10 installation build? Can you put me in conact with them? He'll have Win10-1809 to deal with soon!

MikeYates gravatar imageMikeYates ( 2018-09-08 11:50:57 +0200 )edit

You always need rights to access your computer. These are different. To install programs you need higher rights than a normal user. Access and action rights on the computer are assigned by the OS. It is best to buy a manual for your OS and study how to set up rights.

ebot gravatar imageebot ( 2018-09-08 14:00:57 +0200 )edit

In case you'd forgotten, I stated that the rights have changed from Win10-1709 to Win10-1803 in such a way that the ordinary user is no longer able to install LibreOffice easily at all. I just hope the humans in the forum read all this!

MikeYates gravatar imageMikeYates ( 2018-09-08 20:49:22 +0200 )edit

4 Answers

Sort by » oldest newest most voted
1

answered 2018-09-06 10:05:43 +0200

MikeYates gravatar image

updated 2018-09-10 14:46:21 +0200

I got it installed at last!

Since writing the below, I have discovered that MOST 1803 installations have SYSTEM in all the User-area folders. I think I must have done something to remove it on both systems I tried, perhaps a security measure included in something.

I had to add SYSTEM with full control to the Downloads folder with the MSI This is a fairly new Win10 installation so it seems the defaults have changed in 1803. Am I wrong?

Another MSI app has failed since, on another Win10 1803, with more verbose information. Perhaps LibreOffice should change to EXE?

Or (at least try to) translate windows errors like 2755 ?

edit flag offensive delete link more

Comments

Have you tried "unblocking" the MSI?

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-06 10:20:04 +0200 )edit

That releases the "smartscreen" block. My MSI had started and been through two forms.

MikeYates gravatar imageMikeYates ( 2018-09-08 11:39:28 +0200 )edit

That doesn't mean anything. The block is a special "mark" (in a form of alternative file stream) of "untrusted" zone which was the source of the file. MSI installation works in two phases: impersonated (when msiexec is run under launching user's account), and privileged (when it's run from system account as a service). In the second phase (which is started after "two forms") it checks different security settings, and might refuse to run what passed first stage. Hence my question.

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-08 12:09:38 +0200 )edit

Well, my MSI has no "Unblock" tickbox. I just tried to use it again from a folder without SYSTEM and it failed just the same, though this time asking for escalation after the desktop icon. BTW does "ebot" ever give up? (see above) Can you connect me to the MSI developers?

MikeYates gravatar imageMikeYates ( 2018-09-08 22:52:25 +0200 )edit

I was using it to modify this time, just remove a language.

MikeYates gravatar imageMikeYates ( 2018-09-08 22:55:46 +0200 )edit

Thank you for the effort to discover the possible source of the problem. Unfortunately, I wasn't able to reproduce using a new virtual machine with a fresh Win 10 1803 installation. Downloads grant SYSTEM full access by default there. Maybe you've moved it somewhere?

Can you connect me to the MSI developers?

I am one of them (from your comment to ebot above, I take "MSI developers" as those who develop LibreOffice install package for Win, not MS developers creating the OS service).

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-09 09:31:50 +0200 )edit

Yes, I did mean excellent open-source developers like your good self! I have edited my self-solution to show that my problem is not widespread, at least I can't yet identify what changed my folder permissions and it might be a rare security "fix". I can only guess that perhaps the MSI could check for permissions it will need before getting so far? BTW can you suggest documentation of what folder permissions and inheritances there ought to be in a standard Win10-1803 installation?

MikeYates gravatar imageMikeYates ( 2018-09-10 20:09:34 +0200 )edit

it might be a rare security "fix"

Might be. There are some tools for "hardening" this and that... and they might be useful actually, I don't say they are all crap.

perhaps the MSI could check for permissions it will need before getting so far?

Well - we try to use as few non-standard MSI actions as possible. Such a check needs to be non-standard, and I'm sure that it would bring much more failures than avoided problems. Each non-standard action does :-) - I say from experience.

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-10 21:19:55 +0200 )edit

Of course, I understand one's frustration when stumbling across such a problem. But see: tens of millions of installs generate - let's say - hundreds of error reports. That constitutes less than 0.01%. If we introduce a check without taking into account all possible situations, we will (1) need to support the additional code (man-work); and (2) deal with unforeseen consequences.

I assure you that resources like this (with questions+resolutions) deal with this much better.

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-10 21:24:11 +0200 )edit

When some reports start getting frequent, we see that a problem becomes more important. And we try to improve then.

can you suggest documentation of what folder permissions and inheritances there ought to be in a standard Win10-1803 installation?

No - I don't know of such. But I can tell you which settings are on my test system if you need.

Mike Kaganski gravatar imageMike Kaganski ( 2018-09-10 21:25:55 +0200 )edit
1

answered 2019-03-01 07:34:08 +0200

gheorghiy gravatar image

Hi,

When installing LibreOffice 6.2.0 I've just got the same error: The system cannot open the device or file specified.

Follow the instructions 'How to enable Windows Installer logging'. Put into Value data field all options: voicewarmupx.

Run the installer again.

After it fails, go into C:\Users\your_user_name\AppData\Local\Temp directory. Find in it the most recent .LOG file, something similar to MSI5093e.LOG.

The log will give you some clues about what and why the installer couldn't open.

In my case I have C:\e directory mounted as E: drive. The installer or Windows 10, version 1809, I upgraded it on 2/17/2019, incorrectly interpreted E:\ path:

MSI (s) (D0:84) [23:11:07:693]: Error: Wrong Long Path Name: E:\downloads\LibreOffice\LibreOffice_6.2.0_Win_x64.msi

MSI (s) (D0:84) [23:11:07:693]: Error: Wrong Path Name: \\?\C:\e\downloads\LibreOffice\LibreOffice_6.2.0_Win_x64.msi

MSI (s) (D0:84) [23:11:07:693]: Error: This file path is updated, hence failing to create: E:\downloads\LibreOffice\LibreOffice_6.2.0_Win_x64.msi

MSI (s) (D0:84) [23:11:07:693]: Note: 1: 1309 2: 110 3: E:\downloads\LibreOffice\LibreOffice_6.2.0_Win_x64.msi The system cannot open the device or file specified.

It is the first time after the Windows update I am installing LibreOffice. Something got changed. :-( I've been installing LibreOffice from E: drive since version 4.0 without any problems.

This time I had to install it from C: drive.

PS. Don't forget to remove Logging from Registry.

edit flag offensive delete link more

Comments

Just a hint: we have this FAQ, describing a logging method which does not require registry manipulations.

It is the first time after the Windows update I am installing LibreOffice. Something got changed. :-( I've been installing LibreOffice from E: drive since version 4.0 without any problems.

This change must be something in Windows Installer: we didn't change anything related in LibreOffice. The problem seems to be that deferred install phase (i.e., which runs as a system service, not as current logger-in user) cannot find a drive that is mounted for current user only, not system-wide. That it worked previously, only means that the installer was copied to some (temporary?) location prior to the deferred stage, which for some reason (internal to Windows Installer) doesn't happen now - did MS broke own per-user mount point detection?

Mike Kaganski gravatar imageMike Kaganski ( 2019-03-01 07:54:45 +0200 )edit
0

answered 2019-04-03 14:13:48 +0200

Uninstall KB4489899, than everyhting works fine again. We have the same situation here with a simulated disk drive: reg ADD "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices" /v "D:" /t REG_SZ /d "\??\C:[whattever]"

edit flag offensive delete link more
0

answered 2019-04-18 16:22:21 +0200

MPep gravatar image

I just spend some time by trying the solution with permission and moving to C: * drive and *disabling the languages packs. On Win7 this doesn't work. Other programs MSI setups work fine. but I find the solution (Hallelujah). Just convert the MSI to exe with some online utility and it will be fine. The security risk of course. These problems with MSI repeated from time to time. What is the benefit of making MSI installers anyway? That you can use it as auto updates?

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2018-09-04 12:47:56 +0200

Seen: 646 times

Last updated: Apr 18