Battery not charging after macOS Monterey 12.7.1 update

Laptop: MacBook Pro, Retina (mid 2015) currently running macOS Monterey 12.7.1

Literally after updating to Monterey 12.7.1, battery drained, placed on power adapter (85W MagSafe 2). After more than 6 six hours, amber light sensor remained lit. Removed adapter from laptop thinking the connection was poorly seated in the port and reattached to the MagSafe 2 power port. However, the battery menu bar across the top indicated a declining battery percentage with a power source as the power adapter and the battery not charging.

Next, opened system preferences, clicked battery in bottom row, clicked battery (2nd option on left column) and there is no information regarding battery health whatsoever. The information displayed on the right panel is as follows with the option to select/change at will…

-Turn display off after: 1 min 15 min 1 hr 3 hrs Never

-Slightly dim the display while on battery power

-Enable Power Nap while on battery power

-Automatic graphics switching

-Show battery status in menu bar

The only remaining options in this panel located down in bottom right corner: Restore Defaults button which is grayed out along with a round ? Mark button.

There is nothing in this panel pertaining to battery condition, maximum capacity, or battery longevity.

For the record, while I am not a tech-savvy individual, I can following written instruction. Next, per research on this topic, did the following in order shown per instructions listed in articles researched: shutdown laptop, restarted, reset PRAM and NVRAM, shutdown/restarted again with no change in battery status, shutdown/restarted again this time resetting SMC, and still no change in battery status detected.

Logging out as current user to then view settings under “Standard” user does not change anything reported above. Never before has there been ANY issue with the battery, power adapter, maintaining charge for significant time-periods, rapid charge times…nothing, no issues at all. Laptop purchased around the end of 2015-early 2016.

Any assistance on this would be greatly appreciated…Will downgrading to a previous macOS resolve this issue?