Jump to content
Corsair Community

Heads up with Corsair Link and latest Windows 10 Insider build 16275


sean8102
 Share

Recommended Posts

Hey everyone. Just thought I'd share a heads up that it appears the newest Windows 10 insider build breaks a lot of functionality with Corsair link 4. As well as MSI After burner, and RTSS.

 

After upgrading to this build this is all I can get Corsair Link to display.

 

http://i.imgur.com/DXHDal4.png

 

And this is all I can get out of MSI Afterburner even when running the latest beta version.

 

http://i.imgur.com/vMQr8Wl.png

 

 

I found a thread on Guru3D of other users experiencing the same thing. Seems to be something on Microsofts end that they need to fix.

https://forums.guru3d.com/threads/windows-10-build-16273-broke-ab-and-rtss.416463/

 

Here some feedback someone already submited to Microsoft Feedback hub that you can upvote if you ware using a insider build as well. Hopefully they can fix this before it is released to the general public.

 

https://aka.ms/Ci31vw

 

Hope this helps anyone else that runs into this problem. Thankfully I can still set the fan speed on my h100iV2 based on its coolant temp so functionality is not to impacted for me.

 

This is a explanation from someone on what appears to the problem. "Win32 API CreateService function seem to be broken in builds 16273 and 16275 for 32-bit processes, which try to install 64-bit kernel drivers. So all 32-bit applications working with hardware directly won't work, you'll need to wait for fix from Microsoft side."

Link to comment
Share on other sites

This is a explanation from someone on what appears to the problem. "Win32 API CreateService function seem to be broken in builds 16273 and 16275 for 32-bit processes, which try to install 64-bit kernel drivers. So all 32-bit applications working with hardware directly won't work, you'll need to wait for fix from Microsoft side."

 

This does not make sense as SIV32X works on both builds 16273 and 16275, well it does on my systems. Does it work on your system?

 

Make sure you ONLY run the 32-bit SIV32X and the 64-bit SIV64X is not active.

 

CL4 also fails on the same system that SIV32X works on, see http://forum.corsair.com/forums/showthread.php?p=917576

 

I have just worked it out! If I delete the SIV Driver service SIV32X still works, but SIV32L fails so I expect CreateServiceA() is broken and CreateServiceW() works. If the code is changed to use CreateServiceW() I suspect all will be OK.

 

attachment.php?attachmentid=30834&stc=1&d=1503820817

RCK.thumb.png.9247fd0ee3e50398d326333f7183a701.png

Edited by red-ray
Add link - CreateServiceA() is broken
Link to comment
Share on other sites

This does not make sense as SIV32X works on both builds 16273 and 16275, well it does on my systems. Does it work on your system?

 

Make sure you ONLY run the 32-bit SIV32X and the 64-bit SIV64X is not active.

 

CL4 also fails on the same system that SIV32X works on, see http://forum.corsair.com/forums/showthread.php?p=917576

 

I have just worked it out! If I delete the SIV Driver service SIV32X still works, but SIV32L fails so I expect CreateServiceA() is broken and CreateServiceW() works. If the code is changed to use CreateServiceW() I suspect all will be OK.

 

Yeah the 32 bit version of the app you linked works. Corsair link is not a big deal to me since I can still set my fan curve based on colleant temp, which is all I use it for. I mainly miss the perf overlay info of afterburner. Hopefully the devs of that get it working or MS dose something to let it work again.

 

http://i.imgur.com/tghCUnF.png

Link to comment
Share on other sites

Yeah the 32 bit version of the app you linked works. Corsair link is not a big deal to me since I can still set my fan curve based on colleant temp, which is all I use it for. I mainly miss the perf overlay info of afterburner. Hopefully the devs of that get it working or MS dose something to let it work again.

 

Thank you, this is what I expected. It just occurred to me if you start CPUZ x64 then start CL4 this should work around the issue as CPUZ x64 should create and start the CPUZ143 service :idea:.

 

CreateServiceA() is basically a wrapper that calls CreateServiceW() and I guess M$ messed up. It's only an issue on RS3 x64 and RS3 x32 works. I would love to know what really happened, but suspect I never will.

 

I suspect it would take maybe 5 minutes to build an ASCII SIV32L that worked, but as both the Unicode SIV64X + SIV32X work see no point in doing this.

 

I would hope developers of 32-bit only ASCII only apps would just work around the M$ bug in their code.

 

attachment.php?attachmentid=30836&stc=1&d=1503846642

RCK.thumb.png.c3f042ef7cb8290edd92a74dfb34ec97.png

Edited by red-ray
Link to comment
Share on other sites

Thank you, this is what I expected. It just occurred to me if you start CPUZ x64 then start CL4 this should work around the issue as CPUZ x64 should create and start the CPUZ143 service :idea:.

 

CreateServiceA() is basically a wrapper that calls CreateServiceW() and I guess M$ messed up. It's only an issue on RS3 x64 and RS3 x32 works. I would love to know what really happened, but suspect I never will.

 

I suspect it would take maybe 5 minutes to build an ASCII SIV32L that worked, but as both the Unicode SIV64X + SIV32X work see no point in doing this.

 

I would hope developers of 32-bit only ASCII only apps would just work around the M$ bug in their code.

 

It looks like someone did something to get MSI Afterburner and Rivatuner working with this Windows 10 build already. Just downloaded it and tested it and its working fine.

 

http://i.imgur.com/pCU2dBn.png

 

This is the link to the post of the person that said they made some kind of fix. https://forums.guru3d.com/threads/windows-10-build-16273-broke-ab-and-rtss.416463/#post-5466942

Link to comment
Share on other sites

It looks like someone did something to get MSI Afterburner and Rivatuner working with this Windows 10 build already. Just downloaded it and tested it and its working fine.

 

This is the link to the post of the person that said they made some kind of fix. https://forums.guru3d.com/threads/windows-10-build-16273-broke-ab-and-rtss.416463/#post-5466942

 

He changed the code to use CreateServiceW() which is what I expected would circumvent the M$ bug.

Link to comment
Share on other sites

  • 2 weeks later...
 Share

×
×
  • Create New...