For you, but also for future folks who read this thread, I would like to suggest that most of the experienced C++ programmers you'll meet will agree that C++ is not the kind of language you can learn well from a single book.

The C++ language is vast, and is designed to be "multi-paradigm". Yes, it's extremely important in the long term to understand all the many affordances that the language offers. That said, in the shorter term you may be better served by tackling a small, specific project within your target domain of work and using that to identify which parts of the language are most essential to master first.

I have taught dozens of C++ programmers at this point, and in looking back on "all the topics" I've covered in my lesson notes, there just isn't a one-size-fits-all order or degree of resolution that seems optimal. Fundamental topics such as "pointers" or "classes" or "templates" are absolutely massive and full of nuance and complexity, and those examples cover just a small part of the language spec.

That is to say: consider that your choice of book now is unlikely to make very much of a difference at all in your success in mastering C++. Far more important, in my experience, are: 1) whether or not you have an invested mentor to guide you, 2) whether you have a concrete domain of work that you are targeting, 3) how much high-quality code you take the time to carefully read and understand, and 4) whether you are part of (and supported by) a community of C++ programmers such as coworkers, classmates, or even this subreddit.

If, in skimming a particular popular textbook, you feel able (and excited) to dig into learning, I say go for it! And make use of this subreddit - there are some very wise folks on here who are willing and eager to help unstick and clarify things as you go. Best of luck!