Wine stopped using msi, question for order:?

Question

linux

Good day to all,
I will immediately warn you that I am not a very confident Linux user, and therefore the story I described below may have a very simple solution.
I haven’t used wine for a long time, and when I used it, everything worked with a bang, or at least with half a kick everything started up and installed
, it was enough just to google a little and the solution came by itself, but recently I decided to create a fresh prefix and install everything
that necessary for the normal operation of the unit (dotnet, deex9 and other nonsense), but then I ran into an incomprehensible force majeure.
Namely, when I tried to install, I received a warning that windows installer was not installed, I did not find it in the winetricks list (maybe I was looking badly)
oh well, it means that I climbed onto the site of small software and downloaded, just in case, 2 versions 3.1 and 4.5 under winexpi and some kind of 1 under win7
, I installed 4.5 and registered msi in wincfg. Well, I think now everything will work, but what was my surprise when I launched

WINEARCH=win32 WINEPREFIX=~/wine/unity winetricks winxp dotnet20

an hour later, I watched the same picture of preparation for installation as when starting it.
console output during startup is something like this:

Executing w_do_call winxp
Executing load_winxp
Setting Windows version to winxp
Executing winetricks_early_wine regedit C:\windows\Temp\_winxp\set-winver.reg
Executing w_do_call dotnet20
Executing load_dotnet20
Executing w_do_call remove_mono
Executing load_remove_mono
------------------------------------------------------
Mono does not appear to be installed.
------------------------------------------------------
Executing w_do_call fontfix
Executing load_fontfix
Setting Windows version to win2k
Executing winetricks_early_wine regedit C:\windows\Temp\_dotnet20\set-winver.reg
Current wine does not have wine bug 30845, so not applying workaround
Executing wine dotnetfx.exe
fixme:advapi:DecryptFileA ("C:\\users\\pavel\\Temp\\IXP010.TMP\\", 00000000): stub
err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail
fixme:advapi:LsaOpenPolicy ((null),0x33f2e4,0x00000001,0x33f2d0) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:sfc:SFC_3 0

and then as the infinitely running preparation progresses, about once a minute, a line appears:

err:ole:CoGetClassObject no class object {000c101c-0000-0000-c000-000000000046} could be created for context 0x4

and, of course, there were no such freezes on the floor of the console buffer in an hour, of course,
both the installer and the console itself, but the installation is not progressing as such - which surprised me terribly
, especially when I noticed that the console was not particularly informative on this matter - I was depressed, Googling this time did not give anything and the whole day, lost in an empty
place, brought the realization of helplessness, but that's not all, because I decided not to give up and add difficulties to myself so that it would not be so boring.
A few minutes later I decided to do everything as recommended in Google and demolished (through purge of course) Wine 1.6 i386 by installing wine 1.4 i386 - and the result was not long in coming
because after a couple of minutes, the same thing happened again, depressed, I also tried to rearrange wine 1.7 i386, but from the repository of wine itself, but nothing helped.
By the way, the same situation, or in other words, it was about the same with msxml6.
You can also add what I noticed from all this that when installing the windows installer, it formally exits and the window closes, but if there was a launch in the console, then there is no transition to interactive mode,
which tells me that the process continues to work if outside the console to run it through psit is clear that it continues to work for some reason.
Well, that's not the point, when I try to force the prefix by
WINEARCH=win32 WINEPREFIX=~/wine/unity wineboot -u
updating it, but if I previously installed
say msxml6 and then aborted - then it starts the eternal installation again.
Without specifying the prefix (in the default .wine), I also tried the same result and what I concluded that something was wrong with wine or not healthy, although it’s strange that
Google didn’t give much, maybe I’m doing something wrong, what used to go "with a bang" and now changed.
Used lubuntu 14.10 (generic kernel) swapped: wine1.4:i386 wine1.6:i386 wine1.7:i386
I hope for your hints and help.

Answer 1

I don't know how you can, but
Says it cannot create an MsiServer object. How to fix this, I don’t know for the first time I see such an error in wine

Answer 2

BUT! Got it, topic closed. But it's still strange that the packages were made so ugly.