[Bug 53046] New: upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

Bug ID: 53046
           Summary: upgrading from WINE 5.0.3 to 7.0, winecfg throws
                    several missing components errors
           Product: Wine
           Version: 7.0
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 72438
  --> https://bugs.winehq.org/attachment.cgi?id=72438
A capture of the error messages about missing DLL components

I attempted to upgrade the WINE from 5.0.3 to WINEHQ Stable 7.0. When I ran
"winecfg" after the upgrade, it complained about missing DLL components. This
same situation occurred after installing WINEHQ development version 7.9.
Regressing to version 5.0.3 eliminated the missing DLL errors.

During the installation of HQ stable, I copied the missing DLLs to WINE.
"winecfg" stopped sending errors about missing DLL and complained about not
being able to run "wineboot.exe"

I regressed WINE to 5.0.3 for now.

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #1 from Gijs Vermeulen  ---
Did you use a new prefix after switching or was this when running inside an
existing prefix?

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #2 from [e-mail] ---
Running within the existing default prefix.

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #3 from Gijs Vermeulen  ---
(In reply to tkocou from comment #2)
> Running within the existing default prefix.

You don't want to do that. AFAIK upgrading existing prefixes two years worth of
versions forward is not going to work. Can you reproduce the issue with a
clean/new prefix?

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #4 from Rafał Mużyło  ---
> You don't want to do that. AFAIK upgrading existing prefixes two years worth of versions forward is not going to work.

I'm not 100% sure, but I feel you're wrong here. Those messages look more like
an *improper* update.

Would OP elaborate on how exactly they've updated wine ? Was it by using their
distro package ? Did they *fully* uninstall the old version, so that wineboot
couldn't get confused by old lib versions ? For the most part, if rerunning
'wineboot -u' alone doesn't help, manually cleaning prefix' system/system32
dirs and 'wineboot -u' should (in most cases).

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #5 from [e-mail] ---
At first, I installed 7.0 on top of the existing 5.0.3. Errors of course. I
purged 100% of the WINE installation via the synaptic manager to include
deleting the .wine directory. I installed the 7.0. and made sure that the
winecfg pointed to the 7.0 version. Still the same errors about missing DLLs
when I invoked winecfg. So I repeated purging 7.0 and installed 7.9 dev
version. Same errors again. So I purged the WINE installation, installed the
older 5.0.3 (via synaptic) and overwrote the .wine directory from a known good
backup. winecfg is working now.

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #6 from [e-mail] ---
Additional info, I added the WINE HQ packages to Synaptic Manager via the
instructions on WINE HQ for Linux Mint 20

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

Olivier F. R. Dierick  changed:

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

--- Comment #7 from Olivier F. R. Dierick  ---
Hello,

(In reply to tkocou from comment #5)
> purged 100% of the WINE installation via the synaptic manager to include
> deleting the .wine directory. I installed the 7.0. and made sure that the

The wineprefixes (including the default ~/.wine) are not part of the package
and are not deleted when the package is purged. You have to manually delete it
if you want to clean it. But you can also make fresh wineprefix by giving it a
different name with the environment variable WINEPREFIX.

You can do this with something like:

WINEPREFIX=~/whatever.wine wineboot -u

Then you could copy-paste+overwrite the contents of
~/.wine/drive_c/windows/system32 and ~/.wine/drive_c/windows/syswow64 with
those of the same directory in ~/whatever.wine and try wineboot -u on the old
prefix again.

Regards.

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #8 from [e-mail] ---
I purged the WINE 5.0.3 and installed WINE 7.0 stable from Synaptic Manager.
Then I followed your suggestion of creating a new WINEPREFIX and then copying
over the contents of the new WINEPREFIX to the default .wine directory -
basically overwriting the default.

When I tried the winecfg, all works now. Where exactly are the WINEPREFIX
stored in Linux? I'd like to clear out all the messed up prefixes.

[Bug 53046] upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors

[WineHQ Bugzilla]

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

--- Comment #9 from Olivier F. R. Dierick  ---
(In reply to tkocou from comment #8)
> I purged the WINE 5.0.3 and installed WINE 7.0 stable from Synaptic Manager.
> Then I followed your suggestion of creating a new WINEPREFIX and then
> copying over the contents of the new WINEPREFIX to the default .wine
> directory - basically overwriting the default.
>
> When I tried the winecfg, all works now. Where exactly are the WINEPREFIX
> stored in Linux? I'd like to clear out all the messed up prefixes.

Hello,

Unless you manually set a path with WINEPREFIX, Wine only use the default path
~/.wine .

Third party apps that use wine/forks (steam proton, lutris, etc.) puts the
wineprefixes in their own places.

You may find all wineprefixes with a command such as:

find ~/ -type d -wholename "*/drive_c/windows"

Regards.