FALE Posted September 17, 2017 Share Posted September 17, 2017 We're aware of this. I actually just found out about this issue (I've only been PM for Link for a couple of months) and flagged the bug as top priority. To be honest, most of us just disable UAC on our systems. The problem could be as simple as all the power nerds at Corsair just never thinking to check with UAC enabled, and it's possible the bug was previously listed as low priority. THAT has been corrected and it's on the engineering team's radar as something that needs to be fixed ASAP. I get the random USB noise while gaming as well. The whole LNP died for like 3 reboots at one point then came back before I could tear down my computer to figure it out. Same behavior as the poster. Win 10x64 PRO standard not fast ring or anything. Standard consumer version. Link version 4.8.2.1 does the new version fix this? UAC is on and will stay on. THx Link to comment Share on other sites More sharing options...
Corsair Employees Greybeard Posted September 18, 2017 Corsair Employees Share Posted September 18, 2017 I get the random USB noise while gaming as well. The whole LNP died for like 3 reboots at one point then came back before I could tear down my computer to figure it out. Same behavior as the poster. Win 10x64 PRO standard not fast ring or anything. Standard consumer version. Link version 4.8.2.1 does the new version fix this? UAC is on and will stay on. THx The most recent version of C Link is version 4.8.3.8. I'd try that first and see if that will address your LNP issue. Link to comment Share on other sites More sharing options...
FALE Posted September 20, 2017 Share Posted September 20, 2017 The most recent version of C Link is version 4.8.3.8. I'd try that first and see if that will address your LNP issue. Issue stopped happening. Haven't installed the new version yet but it's fine for now. Tech support doesn't get credit for when stuff works so thx dudes. Link to comment Share on other sites More sharing options...
Corsair Employees Greybeard Posted September 20, 2017 Corsair Employees Share Posted September 20, 2017 Cool good to hear. I'd keep monitoring it and see if you run into any unusual behavior. If you see any, let us know. Link to comment Share on other sites More sharing options...
Astral85 Posted September 21, 2017 Author Share Posted September 21, 2017 We're aware of this. I actually just found out about this issue (I've only been PM for Link for a couple of months) and flagged the bug as top priority. To be honest, most of us just disable UAC on our systems. The problem could be as simple as all the power nerds at Corsair just never thinking to check with UAC enabled, and it's possible the bug was previously listed as low priority. THAT has been corrected and it's on the engineering team's radar as something that needs to be fixed ASAP. Hi Dustin, I am getting a regular .NET Runtime error in Event Viewer and it may offer some clues as to why Link is not starting with Windows from a standard account. Key words - Unauthorized access and Task Scheduler. Event 1026 Application: CorsairLink4.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.UnauthorizedAccessException at Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.RegisterTaskDefinition(System.String, Microsoft.Win32.TaskScheduler.V2Interop.ITaskDefinition, Int32, System.Object, System.Object, Microsoft.Win32.TaskScheduler.TaskLogonType, System.Object) at Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(System.String, Microsoft.Win32.TaskScheduler.TaskDefinition, Microsoft.Win32.TaskScheduler.TaskCreation, System.String, System.String, Microsoft.Win32.TaskScheduler.TaskLogonType, System.String) at CorsairLink4.Win7.Services.UtilService.SetupApplicationRunAtStartup(Boolean) at CorsairLink4.Win7.App..ctor(Boolean) at CorsairLink4.Win7.App.Main(System.String[]) Link to comment Share on other sites More sharing options...
Corsair Employees Corsair Dustin Posted September 21, 2017 Corsair Employees Share Posted September 21, 2017 The standard account problem is a known issue, something we've reproduced internally, and a fix is on the way. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.