Born into nepotism, Harry arrogantly thought he could reshape the royal norms to surprise Meghan, but ended up a beggar

Prince Harry was “infuriated” after King Charles refused to put Meghan Markle on the royal family payroll, a new book claims.

The monarch reportedly broke the news to the “spare” prince in 2016, 

just moments after Harry revealed he planned on marrying the American actress, royal correspondent Robert Jobson wrote in his new book, “Our King.”

“Are you sure, Harold?” Prince William asked his younger brother.

Then-Prince Charles delivered the second blow — rather than congratulating Harry, the future king said he couldn’t afford to pay Meghan as a member of the royal family 

because he was already bankrolling Camilla and William’s growing family, Jobson states in an excerpt obtained by the Daily Mail.

“This infuriated Harry,” wrote Jobson, who also authored two books on Princess Diana alongside her former bodyguard Ken Wharfe.

The “bombshell” led to one of the initial falling-outs between father and son.

Charles stopped taking Harry’s calls after his son swore at him and repeatedly asked for funds.

“When the Queen asked Charles why he hadn’t given in, he told her that he wasn’t a bank,” Jobson wrote.

Jobson theorizes that all the incidents Harry and Meghan have publicly whined about — such as the spat between Kate Middleton and Meghan in the leadup to her wedding, when the actress said the then-pregnant Duchess must have been suffering from “baby brain” — were made bigger in their minds because of King Charles’ initial refusal to accept Meghan as a working, patrolled royal.

Harry had a strong inkling that William disapproved of Meghan and considered their romance a “whirlwind affair,” the book claims.

Meghan felt Kate was “stand-offish” from their initial meeting, forming an uncomfortable relationship that continued through their years as in-laws.

Even Queen Elizabeth became turned off by the couple’s antics, particularly after their 2021 interview with Oprah in which they heavily criticized the monarchy and accused the family of not accepting Meghan out of racist ideals.

The late Queen described the Sussexes’ behavior as “quite mad,” Jobson wrote, and later came to believe that Harry was “so consumed” by his love for his wife that it was “clouding his judgment.”

 Follow us to see more useful information, as well as to give us more motivation to update more useful information for you.

Source: Los Angeles Times

Related Posts

Prince Harry’s Christmas Heist: Royal Ornaments ‘Stolen’ for Fiery-Haired Duke’s Staff Only Moments Before Bombshell ‘Megxit’ Announcement

In what has become one of the most talked-about and controversial moments in recent royal history,  Prince Harry’s Christmas 2019 has now gained notoriety for a rather…

Meghan Markle and Prince Harry Urged to Secure Another Contract With Netflix After ‘POLO’ Flopped

Meghan Markle and Prince Harry, the Duke and Duchess of Sussex, have consistently made headlines since stepping away from their royal duties in 2020.  Their transition to…

Meghan Markle’s Christmas ‘ultimatum’ for Prince Harry as couple plunged into ‘panic’

Meghan Markle has been at the center of intense media scrutiny over the past few years, and her personal life with Prince Harry continues to spark interest…

Meghan Markle opens up on spending Christmas with Firm and vows to ‘never return’

Meghan Markle recently opened up about her experiences surrounding the royal family and her decision to step back from her role as a senior member of the…

King Charles III thanks medics for his, Princess Kate’s cancer care in Christmas speech

In his annual Christmas speech,  King Charles III took a moment to express his heartfelt gratitude to the medical professionals who played a significant role in the…

Meghan Markle’s ‘ultimatum’ to Prince Harry amid ‘panic mode’ ahead of Christmas: ‘fix things’

In the lead-up to Christmas, Meghan Markle reportedly found herself in a state of heightened concern, pushing Prince Harry to take decisive action in their relationship.  Sources…

error: Content is protected !!