So ive tried to make it work 3 times with upgrades the first time the last two being complete reinstall`s.
Kernal is 6.12.34.1
Manjaro KDE plasma 6.3.5
Manjaro KDE 25.0.3-250526
Hardware: cpu j3455 with 16gib of ram and 500gib of ssd, integrated Intel graphic 500.
When i install the latest wine 10.9 with WoW64.
Wine refuses to work with any of the windows programs i use.
I have noticed by accident one error “failed to load kernal32.dll”
Any ideas on how to fix it
Has it ever worked before (for you)?
There are ways to use one specific wine version for specific programs,
instead of the ever changing wine in a rolling release like Manjaro -
Bottles is one of them.
I’m not a gamer - WoW is a game, no?
I have heard of Proton and Steam.
No Idea about these.
No, in this case, the OP is talking of the new wine, which has native WoW64 support, i.e. wine is now supposed to be able to run old 32-bit Windows applications through a 64-bit wine without having to rely on a separate 32-bit wine as part of the multilib shared libraries of the underlying GNU/Linux (or *BSD) system.
If you require Windows programs you should really use Windows operating system.
wine is a layer which translates windows system calls to Linux - if possible. It is quite possible the application does not work at all.
I suggest you check the compatibility database on winehq.org and use their forum to troubleshoot your issues with the Windows application(s) in question.
With the information provided it is impossible to suggest anything.
EDIT
Another option is to use crossover from codeweavers packaged for Manjaro in the official repo.
Aha - I see, I guess. 
Then this here seems relevant, especially the second bullet point:
Arch Linux - News: Transition to the new WoW64 wine and wine-staging
- Breaking Changes: Existing 32-bit prefixes needs to be recreated
… essentially:
remove ~/.wine or whereever the “old” prefix was
would be my guess
Before we go much further;
kernel is the actual and preferred spelling.
A few questions which may help others to understand your situation;
Did you create a WINEprefix for your Windows applications, or did you simply install WINE, expecting that they should “just work”?
With WINE, one needs to create an environment suitable for the applications to install; basically a Windows installation within a special directory (WINEprefix).
If any of these Windows applications are taken from a previous 32-bit WINEprefix, their paths might need to be edited to conform to the Program Files (x86)\... directory structure.
Naturally, if these applications were new installations, this will not be relevant.
This tends to indicate that your WINEprefix hasn’t been installed and/or configured properley
It seems to be a Windows issue.
Not with the information provided.
A reminder that Windows configuration (albeit within WINE) is outside the scope of the Manjaro forum.
Setting up a multi-boot scenario between Manjaro and Windows might be a wothwhile consideration:
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; 
Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Edit:-
I note several others are also experiencing difficulties with
the new WINE with WoW…
I dare say the changes have caught a few unaware.
Regards.
I use Wine to play an old game (Halo Custom Edition), after the update the game runs like 1 FPS now, I reinstalled the game but still the same…
Do I need to remove ~/.wine ?
Try renaming it to ~/.wine.bak. If this improves things, then you can delete it.
See the link in my post above.
They say:
Potential Issues:
OpenGL Performance: A known limitation of the new WoW64 mode is reduced performance for 32-bit applications that use OpenGL directly
Breaking Changes: Existing 32-bit prefixes needs to be recreatedIf you are facing issues with 32 bit prefixes, please recreate these and reinstall the application.
I don’t know your game (or any game, for that matter …) - it could be worthwhile or even necessary to
move the WINEPREFIX and install the game again into a newly created one.
If you installed it into ~/.wine
(which is the default location when you don’t specify a WINEPREFIX),
then rename that directory and start over.
However you installed that game to begin with - do the same thing(s) again.
Did that but the issue remains but thank you anyway…
I have dual boot with Windows 10 so I can play it there!
In fact, the few articles I’ve read on the topic recommend exactly that for anyone having difficulty with WINE 10.9; to create a new WINEprefix and freshly install all Windows applications.
Makes sense, really - the new WINE is effectively a new Windows system - one usually has to install favourite software from scratch, when setting up a new system.
Exactly.
If this:
means that ~/.wine was removed or renamed,
both of which have the same effect,
then of course the issue isn’t resolved -
because now you have literally nothing left of the “old” installation.
It can’t work without reinstalling the Windows application(s) in a fresh wine prefix.
I’m sorry, Wine 10.9 still broken for me…
I consulted some links you guys provided specially this one:
https://bbs.archlinux.org/viewtopic.php?id=306356
The issue remains so I’m thinking maybe downgrade Wine to version 10.8-2 using
manjaro-downgrade but I know usually it is not recommended to do so…
No one knows what your issue is with (re)moving your wine prefix and reinstalling your application in a fresh one.
No one can advise more than already done here.
Perhaps it would help if you gave one or a few examples?
For the benefit of passers-by; and for the OP (assuming they return to this topic). It doesn’t look like great number of users are affected by the changes in WINE (at least, from the quick research I’ve performed).
An educated guess suggests that many already using a 64-bit WINEprefix may likely continue using their Windows applications as before; a quick example that comes to mind is the mp3tag (64-bit) instance I have installed in a Windows x64 WINEprefix;
it works without issue, as before.
Clearly more information is needed from you if creating a new WINEprefix doesn’t magically fix your problem. However, as previously mentioned;
Otherwise, there’s little that can be added, at this time.
Regards.