No luck, just had the problem again....
So many firmware updates but they do not fix the problem that needs fixing... Amazing.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I've had my MS Pro 4 for a few days now. Updates are installed and it's working fine. I hear a crackling or arcing sound every once in a while. It even happens when in sleep mode. Should I be concerned or is there an explanation for this?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
No luck, just had the problem again....
So many firmware updates but they do not fix the problem that needs fixing... Amazing.
The crackling noise occurred again this morning. As my previous post, I immediately checked the Event Viewer. It was perfectly timed with the following event:
INFORMATION: 9/1/2018 11:09:06 AM
Event ID: 1
Source: SpeechRuntime
Audio Orchestrator Power Event: Battery Saver Is Not Enabled, Voice Activation Ready
No other event occurred at that time. So clearly, the crackling is related to this Windows function.
Something I forgot to mention in my previous post. I have a Microsoft Surface laptop and both my kids (in college) have Microsoft Surface Pro 4 laptops. The crackling sound occurs in all three of our devices, so it is virtually impossible that it's "bad hardware." This has something to do with the Windows SpeechRuntime service interacting with the Surface firmware.
Microsoft -- Can you please post whether this is being actively addressed by the development team?
This happens on both my Surface Pro 4's from day 1 regardless of updates. I won't be getting another Surface product ever.
I had the same issue with my surface pro4.Since trading it in for a surface pro at BestBuy I no longer have this problem.This must be a issue with an older generation surface.
While that might be true, cleffty, my surface did not have this problem from day one on. So it still seems to be a software problem that should be solvable. Well, at least if somebody would care...