Aspire SW5-173 (and other) "plugged-in, not charging 0%", solved. Win 10 updates, not solved.

jaro
jaro Member Posts: 5 New User
edited November 2023 in 2018 Archives
Hi,

for weeks, I was fighting with this problem and perhaps the solution will be of use for some of you.
For the notebooks who do not have the possibility to reset the battery (build in, no reset switch) like this model,
I have seen a lot of "solutions", but none works, inluding the reinstallation of power management drivers.
My suspicion always was it has to do with Win 10 upgrade, and, against all nonsense said, it is really and obviously often the case.
The proof of evidence: simply go to Bios setup (F2 during the boot), and let the notebook idle with power plugged in for some hours.
After that, boot again, reconnect the power plugin, and normally you should see the battery state in the normal status.
Also if not, you can run your notebook for hours without power plugged in, which means that the battery is charged, just the indication is wrong.
This is not valid for charging under win 10, it stays at real 0% there (unplug the power and the notebook is out).

For Acer support
1) So please, dear Acer, be so kind and give us the right battery drivers which work under win 10.
It is not acceptable when you leave your customers with not chargeable, which means not usable, notebooks.

2) Another big problem with this Acer notebook (and perhaps other ones) are the unsuccesful function updates to win 10 V 1803 (quality updates are ok) because of too small 100 MB EFI partition. I spent days looking for a solution, but there is none.
For a normal user, it is practically impossible to make the partition changes on SW5.
Again, It is not acceptable when you leave your customers with old unsecure win 10 versions.
I am sure you know about this problem.
 
Be so kind and react.

All the best
Jaromir


Answers

  • JackE
    JackE ACE Posts: 45,202 Trailblazer
    What was the original factory installed Windows version on your SW5? Jack E/NJ

    Jack E/NJ

  • jaro
    jaro Member Posts: 5 New User
    Windows 10 home, for sure, one and half year ago, but I did not noticed the build. Some months ago i have seen the system functional updates going suddenly wrong from 1703 to 1803, made some research, finding a lot of users suffering this problem, but no partitioning tool could help me.
    Best regards Jaromir
  • JackE
    JackE ACE Posts: 45,202 Trailblazer
    Is your system protection enabled so that Win10updates created restore points that you can go back to and test ? Jack E/NJ

    Jack E/NJ

  • jaro
    jaro Member Posts: 5 New User
    Not months back. But what meaning has the question? The last succesful update was 1703.
    The reason is the EFI partition to be to small.
    Sure I can destroy everything, repartition the SSD, install win 10 again, and all my work environment.
    And go through all the problems I had with this acer again (wifi drivers, usb drivers etc.). 3 days work, at least. 
    Then it is better to scrap it and buy Lenovo or similar.
    Jaromir
  • JackE
    JackE ACE Posts: 45,202 Trailblazer
    >>>The reason is the EFI partition to be to[o] small.>>>

    What do you mean by too small? Did you get an error message indicating it was too small. It should only be about 100MB as the trusted files are quite small. Jack E/NJ


    Jack E/NJ

  • JackE
    JackE ACE Posts: 45,202 Trailblazer
    The update failure is more likely due to a driver or firmware incompatibility than an insufficient partition size. At the moment, I suggest that you NOT keep trying to force an update due to fears about some as yet unspecified system insecurities.  Part of these issues are due to Microsoft's new and unimproved lifecycle policies with rapid-fire heavy-handed major releases that are almost like entirely new versions of Windows coming out every 12-18 months. This is creating driver & firmware havoc in relatively new machines from many mfrs shipping with earlier major Win10 releases. https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet  I expect that Microsoft will have to moderate these new policies failry soon if they hope to keep Win10 as the de facto standard in PC GUIs.  Jack E/NJ

    Jack E/NJ

  • jaro
    jaro Member Posts: 5 New User
    I am sorry to say that, but I suppose that ACER as the vendor is responsible for the firmware and drivers of its products,
    not Microsoft. I am waiting for months now, hoping MS and Acer announce a solution.
    This is a typical vendor game, leaving the customer helpless in the middle.
    The statement is valid for both problems defined in my first post. At the end, no help to be awaited. Frustrating.
    Luckily, there are alternatives.
    Jaromir
  • JackE
    JackE ACE Posts: 45,202 Trailblazer
    >>>Luckily, there are alternatives.>>>

    Agreed. That's why all my Win10 machines are now running Mint-flavored Ubuntu with the familiar look, feel, & freedom from trouble as my old Win7 machines still deliver. :) Jack E/NJ

    Jack E/NJ