"plugged in not charging.." - driver deletion issue!!

np, and yea this just redirects me to Microsoft Windows Update an img on how to do windows updates lol :P

okay, yea my computer seems to be charging so i will probably leave it alone. as far as repair install goes, ill use that if the problem occurs again, tysm both of you, you were both extraordinary!

aww ok thanks night guys

Might be a little too late, forgive me, but I have the same exact problem here. Can someone help me with this?

you can also check if there is an unknown drivers under other drivers. uninstall it and reboot computer. the battery logo should be back again

Massivez said:

any more help would be great..

My Toshiba notebook started having battery issues the other day and like most I have read up on the various solutions posted all over the net but to no avail. Embarrassing for me as I fix PC's for a living and i can't seem to get this one sorted yet.
Battery charges normally when Windows is not on. When Windows is on Windows doesn't recognize that the AC adapter is plugged in, therefore not charging. Bit irritating to say the least. Hardware checks done and alternative Adapter and battery tested = same result.
The issue regarding locating drivers for the ACPI battery method driver is a bit weird as you should have a folder in your system32 directory called drivers and driverstore.
When you uninstalled the ACPI and try to reinstall the driver files are automatically loaded from the drivers folder. Not much cop if the drivers are corrupted in some manner. In the driverstore folder there is another folder called FileRepository inside this look for a folder called "battery.inf_amd64_neutral_cb8fa151a7b7cb80".
A fresh back up of the relevant ACPI drivers are in here. However you can't just copy them over the originals without altering permissions which should be easier than it is. The driver files concerned are basically - battc.sys and cmbatt.sys and according to my version of Windows 7 (64it) file version is - 6.1.7600.16385
I managed to solve the problem (or so I thought) albeit temporarily by running System file checker from a command prompt. Type cmd in run box and ensure you have administrator privileges. Once DOS window has opened, type in sfc /scannow and press enter. It takes a while to scan your PC but it fixed it for me at first but because I am a tinkerer, the problem returned.
So my thoughts turn towards either a virus hmmm probably not or more likely some erroneous windows update that the PC probably didn't need in the first place.
Still digging at this and will post if I find solution