[Bug 46448] New: MATLAB Runtime installer wants administrator rights

https://bugs.winehq.org/show_bug.cgi?id=46448

Bug ID: 46448
           Summary: MATLAB Runtime installer wants administrator rights
           Product: Wine
           Version: 4.0-rc5
          Hardware: x86-64
                OS: Mac OS X
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

Created attachment 63231
  --> https://bugs.winehq.org/attachment.cgi?id=63231
Log output

macOS 10.14.2
XQuartz 2.7.11
Wine 4.0-rc5 development + 64 bit support
winetricks stable 20181203, HEAD (installed via Homebrew)
  installed vcrun2012

Download MATLAB Runtime R2017b (for Windows) from
http://ssd.mathworks.com/supportfiles/downloads/R2017b/deployment_files/R201...
(SHA-1: d7387891df664e2fb6fad08a144423669d68ee19)

Launch "Wine Devel". `cd` to the directory containing the installer and run

wine MCR_R2017b_win64_installer.exe

WinZip self-extractor runs successfully, then launches the MCR installer.

The installer launches successfully, but when you click on "Next >", you get a
"Permissions error" alert with "You must have administrator privileges to
install this application. Please contact your system administrator." Clicking
"OK" terminates the installer.

Log output from running "wine MCR_R2017b_win64_installer.exe 2>&1 | tee
MCR_R2017b_win64_installer.log" is attached.

[Bug 46448] MATLAB Runtime installer wants administrator rights

https://bugs.winehq.org/show_bug.cgi?id=46448

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Louis Lenders  ---
Hi Braig,

I cannot confirm this. The installer starts fine here. Also tried in older
wine-version wine-4.0.

Did you try this in a fresh new WINEPREFIX? Could you retry?

If the problem remains for you , it might be a Mac OS specific issue I`d guess

Thanks for reporting back