search

ramensoftware / windhawk

The customization marketplace for Windows programs: https://windhawk.net/
https://windhawk.net
GNU General Public License v3.0
2.19k stars 70 forks source link

Unable to open Touch Keyboard after update #126

Closed clover-yan closed 1 year ago

clover-yan commented 1 year ago

Unable to open Touch Keyboard after update. I just updated Windhawk and I cannot turn Touch Keyboard on. By using Safe Mode I can use Touch Keyboard.

No help to disable all mods. Seems like issue of Windhawk.

clover-yan commented 1 year ago

Some Experience Pack features also became unusable, e.g. Snipping Tool.

InspiringOwl44 commented 1 year ago

Neither the Search shortcut (Win+S) works. Already tested with both 1.3.1 and 1.4. Only the latest has this problem. Downgraded to 1.3.1 until this is fixed.

m417z commented 1 year ago

I wasn't able to reproduce the issue. Perhaps those tools either crash or are being killed, for example by an antivirus. Are you using an antivirus? Can you check Event Viewer for crashes? You can use this guide: https://www.cyberlink.com/support/faq-content.do?id=10449

Aleksanderis commented 1 year ago

I wasn't able to reproduce the issue. Perhaps those tools either crash or are being killed, for example by an antivirus. Are you using an antivirus? Can you check Event Viewer for crashes? You can use this guide: https://www.cyberlink.com/support/faq-content.do?id=10449

Not sure about which tools you are speaking and how it's related to CyberLink. Your link also redirects me to CyberLink support center (https://www.cyberlink.com/support-center/home). However I checked Event Viewer and see following errors there, which are repeated several times and which seems relevant.

The one logged when trying to search for something in Start menu (after click "Win" key):

Faulting application name: SearchHost.exe, version: 623.22800.10.0, time stamp: 0x6514fd71 Faulting module name: windhawk.dll, version: 1.4.0.0, time stamp: 0x6546cb8d Exception code: 0xc0000409 Fault offset: 0x000000000003c689 Faulting process id: 0x0x40DC Faulting application start time: 0x0x1DA118C05742EE5 Faulting application path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\SearchHost.exe Faulting module path: C:\Progs\Windhawk\Engine\1.4\64\windhawk.dll Report Id: b69a6946-a938-432b-977b-10705510ba3e Faulting package full name: MicrosoftWindows.Client.CBS_1000.22674.1000.0_x64__cw5n1h2txyewy Faulting package-relative application ID: CortanaUI

The one when trying to use emoji dialog (win+.):

Faulting application name: TextInputHost.exe, version: 623.22301.0.0, time stamp: 0x64d66ad7 Faulting module name: windhawk.dll, version: 1.4.0.0, time stamp: 0x6546cb8d Exception code: 0xc0000409 Fault offset: 0x000000000003c689 Faulting process id: 0x0x2294 Faulting application start time: 0x0x1DA118CC52A2DF5 Faulting application path: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\TextInputHost.exe Faulting module path: C:\Progs\Windhawk\Engine\1.4\64\windhawk.dll Report Id: e99f3a78-4615-4757-961c-4ee660d8eb36 Faulting package full name: MicrosoftWindows.Client.CBS_1000.22674.1000.0_x64__cw5n1h2txyewy Faulting package-relative application ID: InputApp

m417z commented 1 year ago

Your link also redirects me to CyberLink support center

Yeah, looks like they removed that page, here's an archived copy: https://web.archive.org/web/20230525052835/https://www.cyberlink.com/support/faq-content.do?id=10449

However I checked Event Viewer and see following errors there, which are repeated several times and which seems relevant.

Indeed likely to be relevant. Can you capture a crash dump? You should be able to get it with the following steps:

Aleksanderis commented 1 year ago

I didn't need to do any changes in the registry, crash dumps were already being created. So I've got a crash dump, but they are ~600Mb each.. Uploaded two of them to Google Drive, but I don't want to share them with everyone. How could I share it with you privately?

m417z commented 1 year ago

I think that I figured out what's the problem, I'm working on a fix. It only affects the portable version. If I see that your dump will help I'll let you know.

clover-yan commented 1 year ago

Before we can get it fixed, can we convert the portable version to installed version? If so, how to?

m417z commented 1 year ago

Fixed in Windhawk v1.4.1.

Aleksanderis commented 1 year ago

Tested it and eventually it worked. But just a note for others - don't be scared if it doesn't work at first, like it was for me. :)

I installed an updated portable version, started it - "start menu" was working, but things like "win+." (emoji dialog, TextInputHost.exe) - wasn't working. Then I looked for logs in Event Viewer and noticed there were crashes logged, which were saying Windhawk 1.4.0 (not 1.4.1). I'm not sure if 1.4.1 reveals itself as 1.4.1 or 1.4.0 (since it's a minor version change), but it gave a hint anyway, that old module could be still injected somewhere. So I Restarted explorer.exe, etc - and it started to work.

Great work, @m417z! 🚀

InspiringOwl44 commented 1 year ago

For me, the start menu search now works. I'm really grateful for the fix. Thank you so much @m417z for your hard work :)