KB4034674 now KB4038788 disables Steelseries/Ideazone Merc Keyboard

[Dirtydeedz]

Solution(with clarification):

You will need 20-40 minutes to complete this process. Plus, additional time to update your Windows 10 installation.

1. Install Windows Driver Kit (Ignore a number of warnings during the install. Click "OK" through them... you're not developing a driver)

2. **NOTE.. Requires reboot. Disable Signed Driver Enforcement (step-by-step instructions)
Skip steps 1-3.5 by holding down "Shift"+[Click]Restart while continuing to hold "Shift"

3.Locate your ZEngine Directory: e.g. C:\Program Files (x86)\Ideazon\ZEngine
a. Copy & Paste "Kernel2k" directory/folder to a different folder, e.g. Documents, to preserve the original untampered version.

4. In the Kernel2K dir/folder, e.g. C:\Program Files (x86)\Ideazon\ZEngine\Kernel2K, rename every file that starts with Alpham or alpham to something else. (ex. Alpham1.sys => Merc1.sys). I changed mine to Alpham1KB.sys

5. Open the renamed *.inf file in a text editor (Notepad++ C:\Windows\System32\notepad.exe) and do a similar find and replace(Ctrl+H) on "Alpham" replacing with "Merc" (or whatever you used), replace all. NOTE**You may need to take control of the *.inf file. Click for Instructions

6. Locate and Delete *.cat file(the security catalog file) e.g. C:\Program Files (x86)\Ideazon\ZEngine\Kernel2K\Merc12.cat

7. Follow the steps below to add "inf2cat.exe" installation directory to the Environment Variables - PATH:
a. In the search/Cortana box, type "Path", then select "Edit environment variables for your account" or press "Enter"
b. In the "Environment Variables" window, in the top box > "Variable" column > select the row "Path"
c. Click edit.
d. Click "New" in the "Edit environment variable" window.
e. Click "Browse" and add the directory of your inf2cat.exe file & press "Enter". Mine was in C:\Program Files (x86)\Windows Kits\10\bin\x86.
f. Select "OK" on all open windows.

8. Follow the steps below to generate a new .cat file
a. Know the PATH to the new *.inf file. e.g. C:\Program Files (x86)\Ideazon\ZEngine\Kernel2K
b. In the search/Cortana box, type "Command", then select "Command Prompt" or press "Enter"
1. for Windows 10 x64 type: inf2cat /driver:"PATH" /os:10_X64
2. for Windows 10 x86(32bit) type: inf2cat /driver:"PATH" /os:10_X86
**NOTE The "quotation marks" ARE included. And, PATH = the directory/folder where the *.inf file is located. (8.a.)
e.g. inf2cat /driver:"C:\Program Files (x86)\Ideazon\ZEngine\Kernel2k" /os:10_X64

9. Locate the entries "Ideazon Merc MM USB Human Interface Device" and "Ideazon Merc USB Human Interface Device"
a. In Device Manager (to open Device Manager >> [Right click] Windows Button>>[Select] Device Manager)
b. Locate & Select "Human Interface Devices" (or they may be under "Keyboards")
c. Right click > update driver > browse computer > Let me pick > Have Disk > Browse > manually select your newly renamed *.inf file.
d. Acknowledge any unsigned driver warnings(Click OK).
**NOTE..You must do this for BOTH entries.

10. At this point my ZEngine icon, in the task bar, was green again. However, I was prompted to restart my PC; which, I did.

11. Unhide the horrible KB4034674 now KB4038788 and resume Windows 10 updates.

Enjoy a working zMerc again!

All the credit to @zathrath03


No Support: Steelseries refuses to update the driver. No surprise, it took them forever to release the half-baked x64 driver (Win 7 x64 signed) that we users currently work with. And, I doubt MS is going to do anything because the user base of this product is the size of a flea on a elephants ass...

Reality: Which doesn't change the fact that hundreds of users are without the full function of their keyboards(Merc Stealth) or Gamepad(Ideazone Fang). So, I come here to Toms Hardware seeking the sages/gurus help.

The problem lies in a driver file Alpham164.sys which after the KB4034674 release, is now deemed unstable. Cough.. Bull! It has worked for ~10 years, that is the apex of "STABLE".

The Workaround: Currently, we users that are in the know, are uninstalling the update. However, it's cumulative and this is going to become more difficult over time.

What we need is a way to tell Windows that this file is safe, or, a way to stop Windows from screening the file. I'm pretty sure disabling driver signature enforcement, side-loading, and developer mode, disable Smartscreen have all been attempted, to no avail.

Any ideas or suggestions would be greatly appreciated.

 

[COLGeek]

Not that it solves this specific problem, but have you considered changing keyboards and avoiding this mess altogether?

Do you have the Z-Series engine installed?

https://downloads.steelseriescdn.com/drivers/keyboards/zengine/ZE_25030_NA_64.exe

 

[Dirtydeedz]

Well I have 2. That's 2 keyboards and 2 gamepads to replace 2 working keyboards out of commission from an update.

Obviously, I have the software. That's what's not functioning.

 

[COLGeek]

I had to ask the obvious questions. You would be surprised.

I really see no good option for you. In tech terms you have obsolete hardware. There is no reasonable expectation that vendors will support products indefinitely.

 

[zathrath03]

1) In your D:\Program Files\Ideazon\ZEngine copy the Kernel2k directory to preserve an original untampered version.
2) In the Kernel2K dir, rename every file that starts with Alpham or alpham to something else (ex. Alpham1.sys => Merc1.sys).
3) Open the renamed .inf file in a text editor (Notepad++, etc) and do a similar find and replace on "Alpham" replacing with "Merc" (or whatever you used), replace all.
4) Delete merc12.cat (the security catalog file)
5) Install Windows Driver Kit ( it's going to give you a number of warnings during install that you won't be able to develop drivers since you don't have an IDE installed. Just OK through them... you're not developing a driver)
6) Add the inf2cat.exe installation directory to your PATH variables (Type path in search and select "Edit environment variables for your account" then select Path in the top window and click edit. Click new then add the directory of your inf2cat.exe file. Mine was in D:\Program Files (x86)\Windows Kits\10\bin\x86. Hit enter, then OK all open windows.)
7) Generate a new .cat file (open a Command Prompt and type: inf2cat /driver:"path" /os:10_X64,10_X86 where "path" is the directory of merc.inf. So, for me it was inf2cat /driver:"D:\Program Files\Ideazon\ZEngine\Kernel2k" /os:10_X64,10_X86)
8) Disable Signed Driver Enforcement (step-by-step instructions)
9) In Device Manager locate the entries "Ideazon Merc MM USB Human Interface Device" and "Ideazon Merc USB Human Interface Device" (they could be under Keyboards or Human Interface Devices)
10) Right click > update driver > browse computer > Let me pick > Have Disk > Browse > manually select your newly renamed merc.inf. Acknowledge any unsigned driver warnings.
11) Enjoy a working zMerc again!

 

[kaelor]

Can you please maybe make a youtube video about this solution? Some of us don't know what to do in and after "7. Add "inf2cat.exe" installation directory to the Environment Variables - PATH:"

 

[bnichols0253]

1) In your D:\Program Files\Ideazon\ZEngine copy the Kernel2k directory to preserve an original untampered version.
2) In the Kernel2K dir, rename every file that starts with Alpham or alpham to something else (ex. Alpham1.sys => Merc1.sys).
3) Open the renamed .inf file in a text editor (Notepad++, etc) and do a similar find and replace on "Alpham" replacing with "Merc" (or whatever you used), replace all.
4) Delete merc12.cat (the security catalog file)
5) Install Windows Driver Kit ( it's going to give you a number of warnings during install that you won't be able to develop drivers since you don't have an IDE installed. Just OK through them... you're not developing a driver)
6) Add the inf2cat.exe installation directory to your PATH variables (Type path in search and select "Edit environment variables for your account" then select Path in the top window and click edit. Click new then add the directory of your inf2cat.exe file. Mine was in D:\Program Files (x86)\Windows Kits\10\bin\x86. Hit enter, then OK all open windows.)
7) Generate a new .cat file (open a Command Prompt and type: inf2cat /driver:"path" /os:10_X64, 10_X86 where "path" is the directory of merc.inf. So, for me it was inf2cat /driver:"D:\Program Files\Ideazon\ZEngine\Kernel2k" /os:10_X64, 10_X86)
8) Disable Signed Driver Enforcement (step-by-step instructions)
9) In Device Manager locate the entries "Ideazon Merc MM USB Human Interface Device" and "Ideazon Merc USB Human Interface Device" (they could be under Keyboards or Human Interface Devices)
10) Right click > update driver > browse computer > Let me pick > Have Disk > Browse > manually select your newly renamed merc.inf. Acknowledge any unsigned driver warnings.
11) Enjoy a working zMerc again!

 

[bnichols0253]

Dude it works great thank you

 

[Dirtydeedz]

Can you please maybe make a youtube video about this solution? Some of us don't know what to do in and after "7. Add "inf2cat.exe" installation directory to the Environment Variables - PATH:"

I will try to edit the directions. Hope that helps. I don't have any plans to make a YouTube video.

 

[oliver.mayoj2]

Please can someone help me, I am trying to use the command prompt to generate a new .cat file, but it keeps giving me the error:

unable to create the catalog
Signability test failed

This windows problem is driving me nuts.

 

[klindsay36]

Please can someone help me, I am trying to use the command prompt to generate a new .cat file, but it keeps giving me the error:

unable to create the catalog
Signability test failed

This windows problem is driving me nuts.

That happened to me as well. I continued with the instructions and everything worked as stated.

 

[klindsay36]

@zathrath03:

This worked a TREAT! I'm so happy because I haven't been able to find anything I like as much as my ZBoard. You. Are. The Best.

 

[gzuscriest]

Please can someone help me, I am trying to use the command prompt to generate a new .cat file, but it keeps giving me the error:

unable to create the catalog
Signability test failed

This windows problem is driving me nuts.

I had the same problem, the solution is simple though
1 Download Windows Driver Kit (WDK), you can get it here:
https://go.microsoft.com/fwlink/p/?LinkId=845980

It may be handy to print outsteps 2-1 to 2-9, or type the below address in the browser of your mobile phone/tablet
http://packard-bell-uk.custhelp.com/app/answers/detail/a_id/38288
It's easier during the restart process when you can follow what's happening and what you should do (for instance: the 1st time I missed step 2-9)

2-1 Click the Start Start menu and select Settings.
2-2 Click Update and Security.
2-3 lick on Recovery.
2-4 Click Restart now under Advanced Startup.
2-5 Click Troubleshoot.
2-6 Click Advanced options.
2-7 Click Startup Settings.
2-8 Click on Restart.
2-9 The following step takes place during the restart where you will be presented with a list of options to choose from, just press 7 to disable driver signature enforcement (maayybe F7 but I doubt my Win10 is that much different from yours).
AFTER correctly finishing the above instructions and PC restart, you can proceed to step 3

3) Open the renamed .inf file in a text editor (Notepad++, etc) and do a similar find and replace on "Alpham" replacing with "Merc" (or whatever you used), replace all.

4) Delete merc12.cat (the security catalog file)

5) Install Windows Driver Kit ( it's going to give you a number of warnings during install that you won't be able to develop drivers since you don't have an IDE installed. Just OK through them... you're not developing a driver)

6) Add the inf2cat.exe installation directory to your PATH variables (Type path in search and select "Edit environment variables for your account" then select Path in the top window and click edit. Click new then add the directory of your inf2cat.exe file. Mine was in D:\Program Files (x86)\Windows Kits\10\bin\x86. Hit enter, then OK all open windows.)

7) Generate a new .cat file (open a Command Prompt and type: inf2cat /driver:"path" /os:10_X64,10_X86 where "path" is the directory of merc.inf. So, for me it was inf2cat /driver:"D:\Program Files\Ideazon\ZEngine\Kernel2k" /os:10_X64,10_X86)

8) Disable Signed Driver Enforcement (step-by-step instructions)

9) In Device Manager locate the entries "Ideazon Merc MM USB Human Interface Device" and "Ideazon Merc USB Human Interface Device" (they could be under Keyboards or Human Interface Devices)

10) Right click > update driver > browse computer > Let me pick > Have Disk > Browse > manually select your newly renamed merc.inf. Acknowledge any unsigned driver warnings.

11) Enjoy a working zMerc again!

CAUTION!! If you restart your computer again BEFORE completing the entire process from 1 to 11, the driver signature enforcement will be re-enabled again and you will have to start all over again, well, you could skip step 1 and start at step 2 because installing WDK should not have been a problem
Just follow the instructions exactly as described and you can't go wrong

I am 100% sure the solution works as described, if it doesn't work for you, accept that you most likely have done something wrong
Just give it another try, it will work

All the credit to @zathrath03

 

[jimgust]

I don't have Ideazon ZEngine installed and I can't find it to download. I don't remap keys so I don't need the engine. I guess my question is what is in the Ideazon\ZEngine folder? Is it just alpham12.PNF, Alpham12.cat, Alpham164.sys, Alpham12.inf, and Alpham264.sys? If so then I have those files in my System32\DriverStore\FileRepository\alpham12.inf_amd64_932fbe5113b0010d folder.

 

[jimgust]

I don't have Ideazon ZEngine installed and I can't find it to download. I don't remap keys so I don't need the engine. I guess my question is what is in the Ideazon\ZEngine folder? Is it just alpham12.PNF, Alpham12.cat, Alpham164.sys, Alpham12.inf, and Alpham264.sys? If so then I have those files in my System32\DriverStore\FileRepository\alpham12.inf_amd64_932fbe5113b0010d folder.

I found an old driver on the techspot website. It turned out there were more files. After installing the v2.5.0.30 driver and following the instructions provided in this thread I can say it all worked.

SteelSeries Merc Stealth Keyboard Driver 2.5.0.30 for Windows 64-bit
https://www.techspot.com/drivers/driver/file/information/15572/

 

[crchavarria82]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

 

[sotted]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

After I reinstalled the ZEngine and replaced the altered directory, I repeated all the steps and my Merc is working again.

 

[crchavarria82]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

After I reinstalled the ZEngine and replaced the altered directory, I repeated all the steps and my Merc is working again.

That's so odd... 🙁 I uninstalled and reinstalled the ZEngine, then replaced the Kernel directory with the altered one (I'd copied it elsewhere before reinstalling)... did all the "Update Driver" steps and it made the ZEngine GREEN again, but I cannot remap keys on the "gaming section" on the left (like changing (R) to (=) for WoW), a the numpad doesn't work. *sigh*

 

[sotted]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

After I reinstalled the ZEngine and replaced the altered directory, I repeated all the steps and my Merc is working again.

That's so odd... 🙁 I uninstalled and reinstalled the ZEngine, then replaced the Kernel directory with the altered one (I'd copied it elsewhere before reinstalling)... did all the "Update Driver" steps and it made the ZEngine GREEN again, but I cannot remap keys on the "gaming section" on the left (like changing (R) to (=) for WoW), a the numpad doesn't work. *sigh*

I repeated all the steps from the beginning. There is some steps you can skip but I just followed the instructions like I had not done it before this time. I deleted the security file and did the step in the command prompt. That is what made it finally work for me.

 

[wyveryx]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

After I reinstalled the ZEngine and replaced the altered directory, I repeated all the steps and my Merc is working again.

That's so odd... 🙁 I uninstalled and reinstalled the ZEngine, then replaced the Kernel directory with the altered one (I'd copied it elsewhere before reinstalling)... did all the "Update Driver" steps and it made the ZEngine GREEN again, but I cannot remap keys on the "gaming section" on the left (like changing (R) to (=) for WoW), a the numpad doesn't work. *sigh*

I repeated all the steps from the beginning. There is some steps you can skip but I just followed the instructions like I had not done it before this time. I deleted the security file and did the step in the command prompt. That is what made it finally work for me.

I'm currently at a loss here. I've done this multiple times after Fall Creators...I can use my board, but can't remap keys, and my numpad is all borked. I've used ZE_25030_NA_64, and my windows is version 1709 Build 16299.192.
I can't seem to find any more current and relevant information on this, save for this site with the most recent comments from last month, everything else is months behind.
I can see both instances of Ideazon in my Device Manager, so I'm curious, are you using the same software build for Steelseries? I figure, all I can do now is to wait for a solution at hand, or I could try the 32 bit 25030.

 

[ittaboo]

It appears the latest update for Windows (Fall Creator's?) has once-again killed the keyboard. I had it working with this fix for a few months, but now it is dead again. I went into Device Manager to once again install the workaround as the drivers, but though I can find the Merc Stealth listed under Human Interface Devices, [strike]there is only ONE entry (Ideazon Merc USB Human Interface Device, not the MM USB one) [/strike]and no entries under keyboards. I can re-update the "driver" and have the icon turn green, but the keybinds still won't function.

Is there a fix for the fix? 🙁

*UPDATE* I reinstalled the regular ZEngine x64 driver and then replaced the Kernel2k with the altered one (I'd copied it elsewhere beforehand). Both devices now show in the Device Manager, and I re-did the process of pointing to the new driver... but it still doesn't register the keybind profiles. What happened??

After I reinstalled the ZEngine and replaced the altered directory, I repeated all the steps and my Merc is working again.

That's so odd... 🙁 I uninstalled and reinstalled the ZEngine, then replaced the Kernel directory with the altered one (I'd copied it elsewhere before reinstalling)... did all the "Update Driver" steps and it made the ZEngine GREEN again, but I cannot remap keys on the "gaming section" on the left (like changing (R) to (=) for WoW), a the numpad doesn't work. *sigh*

I repeated all the steps from the beginning. There is some steps you can skip but I just followed the instructions like I had not done it before this time. I deleted the security file and did the step in the command prompt. That is what made it finally work for me.

But is your NUMPAD working?

 

[1ezidea]

I got to the "reboot" in step 8 and after reboot it worked, (20 minutes my ass, it took 4 hours) so I didn't even screw with drivers or the last 2 steps... hopefully after the next Win10 update it keeps working.