I honestly think the best way to get this issue solved is to trade in the device for a new machine. I walked into a MS store in NYC, told them about the problem, told them my machine had all updates installed, and that MS workers had tried remoting onto
my device multiple times. I then said it appeared that there was a hardware issue as people with later models from this year didn't have the problem. The guy then offered to give me one of their "backup devices" which are brand new machines that are not packaged
for retail but rather that the store has for swaps. He assured me it was brand new and would have most updates already installed. I've been using the machine now for 3 days and it's been great, no issues. I implore everyone to TRY taking it to a store as it
seems like there's NO software fix and it may be a very long time until there is one. I feel like I finally have the device I meant to purchase back in November of last year.
Good luck everyone!
That's a refurb. Hopefully it keeps working for you. I had one of those in a plain cardboard box too. The store employees swore up and down it was brand new. I found out from a different MS employee that it was indeed a refurb. It failed within hours...
If it's software, why did I have 3 machines running the same software image off the same thumb drive behave so differently? The lot 15xx machine had serious sleep issues. The "Brand New" plain cardboard box refurb had serious sleep issues within hours. My
lot 1613 machine wakes each and every time, and has for nearly two months now. All with the same image off the same thumb drive. The older two machines clearly had a hardware issue.
Of course MS has a history of software problems as well. The June update prevents my SP4 from hibernating after it enters sleep. If I set my SP4 to to sleep and then hibernate two hours later, it will never hibernate. It will sleep till the battery dies.
The June update also changed the battery life while sleeping. Before my SP4 used about 1/2% per hour while asleep. After the June update it uses 3% to 4% per hour while asleep. When I restore to an image without the update, all is good. With past windows versions
I could have then ignored this update. With craptastic windows 10, Microsoft forces you to accept ALL updates. Considering the June update and Microsoft's history of releasing bad updates, forced updates are about the dumbest thing Microsoft has ever done.
Panay talked about the issue six months ago and then Microsoft claimed, and continues to claim, the issue is fixed. That is arrogance, horrible customer support and pure BS. Microsoft has not fixed the problem and they have not owned the problem. They knew
about the issue when they released the SP4. They refuse to replace flawed units claiming software issues. BS. IT IS HARDWARE.
It is a given that there will be a class action lawsuit against Microsoft. Normally I decry class action lawsuits, but this is the type of case that cry's out for one.