- pagination is different with different browsers and font sizes. and I'm not sure that all xx% and not charging reports have the same root cause.
- https://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/surface-wont-turn-on-battery-wont-charge - battery not detected steps:

Battery not detected
What you see
- The battery icon has a power plug and a red X.
- Your Surface turns off when you unplug it.
This battery icon means that Windows can’t detect the battery. If you see this, try these solutions.
Solution 1: Install and confirm updates
| Step 1: |
Go to Start , and select<br>Settings > Update & security > Windows Update. |
| Step 2: |
Select Check for updates. If updates are available, they will download and install automatically. |
| Step 3: |
If your Surface doesn’t restart automatically, restart it manually. Go to Start<br> , and select<br>Power > Restart. |
| Step 4: |
Repeat these steps until you see Your device is up to date after you select<br>Check for updates in Step 2. |
After you install all the available updates, confirm that you have the latest Surface firmware update. Here’s how:
| Step 1: |
Go to Surface update history and choose your Surface model. |
| Step 2: |
Find the name of the most recent “System Firmware Update” available for your Surface. |
| Step 3: |
Go to Start , and select<br>Settings > Update & security > Windows Update. |
| Step 4: |
Select Advanced options > View your update history and make sure that the latest firmware update installed successfully on your Surface. |
If the firmware update failed, see Trouble installing Surface or Windows updates?
If updating your Surface doesn’t fix the problem, try Solution 2.
Solution 2: Restart your Surface
Restart (not shut down) your Surface to try to fix the problem.
| Step 1: |
Make sure the power supply is connected and the power connector light is on. |
| Step 2: |
Go to Start , and select<br>Power > Restart. |
| Step 3: |
After your Surface restarts and you've signed in, check the battery status again in the desktop notification area on the taskbar. |
If restarting your Surface doesn’t fix the problem, try Solution 3.
Solution 3: Shut down and charge your Surface
Shut down (not restart) your Surface and charge it for a while.
| Step 1: |
Make sure the power supply is connected and the power connector light is on. |
| Step 2: |
Go to Start , and select<br>Power > Shut down. |
| Step 3: |
Let your Surface charge for at least 30 minutes. |
| Step 4: |
Press and release the power button to turn your Surface on. |
If your Surface still doesn’t detect the battery, go to Solution 4.
Solution 4: Two-button shutdown (Surface Pro models and Surface Book only)
Important
Don’t use this process on Surface RT, Surface 2, or Surface 3.
Use this two-button shutdown process to ensure that your Surface is turned off completely. Here’s how:
| Step 1: |
Press and hold the power button on your Surface for 30 seconds and then release it. |
| Step 2: |
Press and hold the volume-up button and the power button at the same time for at least 15 seconds and then release both.<br> <br><br>The screen may flash the Surface logo, but continue holding the buttons down for at least 15 seconds. |
| Step 3: |
After you release the buttons, wait 10 seconds. |
| Step 4: |
Press and release the power button to turn your Surface back on. |
If two-button shutdown doesn’t help, contact us.
- Community Moderators/MVPs are unpaid volunteers, I am doing what I can to help. I can't help everyone. MS should have dealt with this issue much earlier. I did my best to report the Simplo issue as early as March 2016.
- I think it is unlikely that MS will change the 40% requirement or provide a registry tweak. Your best option is to contact support or go to an official Microsoft Store.
- have you seen a post with the following instructions for battery issues:
1)
Boot into Windows however you can (doing a 2-button reset as other users in the forum have done, and letting it charge for a bit before trying to boot into Windows should work.)
2)
In Device Manager find the Embedded Controller firmware. It will show with yellow bang. Open the properties of this firmware and verify the error code – it should say “Code 10”. If it’s not Code 10, don’t go any further,
but post to let us know what you see in Device Manager.
3)
Assuming it was listed with a Code 10 error, tell Device Manager to uninstall the firmware. It will give you choice to remove/delete the files. Check the box to remove the files and uninstall.
4)
Reboot the system and then come back into Device Manager. Check to ensure it’s running the older Embedded Controller firmware. (38.9.50)
5)
Once the older EC is on the system, stop and make sure that the system is showing “100%” charge on the battery. Once that’s true, go ahead and apply the update again. This should prompt you to restart once the update is
done, but don’t choose to restart right away. Instead, close everything out and tell Windows to shut down (not restart) manually.
6)
Boot on AC power again as you did before. You should get the splash screen as it tries to apply the firmware update again. Let us know the results.
- Repeating, I do what I can, but I can't fix everyone. Sorry
Check Page 123 for the latest victim MehdiSeyedain. Your reply to MehdiSeyedain is in that page too. My problem with installing the firmware is exactly the same as MehdiSeyedain now.
Initially my battery status was showing 85% not charging back in July 26th.
Then I reset to 8.1 and upgraded to 10 and it was still showing 80% not charging (I don't remember the exact percentage, but it was higher than 50% for sure).
Another boot few days later and the battery could not be detected and the firmware won't install.
That is why Barb, MS should allow to run the msi without putting a restriction of minimum 40% battery charge.
I would in the meantime like MS to remove the restriction of minimum 40% battery charge for update. Give me a registry tweak for that please.
An update can create a restore point, so if the update fails due to sudden loss of power, the user can revert to the restore point. This should address MS's concern about a device's power status during long updates.