SPF Record Generator
Use this tool to generate your SPF record.

“All liveries look the same nowadays” is a common lament amongst the world’s avgeeks. You may have noticed that most commercial aircraft feature predominantly white liveries with small areas of color, typically around the tail. It’s one of the reasons why special liveried aircraft are often amongst the most tracked on Flightradar24.
Why are aircraft predominantly white?

There are several reasons white is the preferred color for commercial aircraft. Let’s take a look at them. //

Breaking the mould completely, some operators have elected for a whole colour approach. Perhaps one of the most notable examples is Southwest Airlines (WN). The US low-cost carrier’s livery perhaps contains some of the lowest amount of white in the skies, showcasing the company’s blue, yellow and red brand colors across the entire fuselage.

In Europe, Icelandic carrier PLAY Airlines (OG) sports an all red/pink livery. Does this count as more white than Southwest? We’ll leave it to you to decide.

It is interesting to note that these liveries are more common amongst low-cost carriers, suggesting the value of showcasing a bold brand can outweigh the cost of more paint.

The DNS-01 challenge is more difficult to automate than HTTP-01, requiring that your DNS provider supply an API for managing your DNS records. //

there are several circumstances where you might choose DNS-01 over HTTP-01:

• If your domain has more that one web server, you will not have to manage challenge files on multiple servers.
• DNS-01 can be used even if port 80 is blocked on your web server.

I did the same (ntfsresize + fdisk) while installing linux, and ran into the same problem. Eventually, this seems to work, from the Windows recovery prompt:

 fixboot /scanos

it found c:\windows, then I ran:

 bcdboot c:\windows

I also ran chkdsk c:, fixboot /mbr and bcdedit /set {default} recoveryenabled no before that, but I do not think they are related to the problem.

As far as I understand, the bcdboot command above, added the option of booting to the new c:\windows for bootmgfw.efi. Indeed, after rebooting I had two options:

1. the new "windows 10, on partition 3", which worked, and

2. "windows 10", which did not (as before).

Once booted, I removed the non-working option from the configuration manager (search "configuration manager", tab "boot").