I encountered the same problem.Therefore I added some code to our Install routine to create the necessary translation for English country names, based on https://public.opendatasoft.com/explore/dataset/countries-territories-taxonomy-mvp-ct-taxonomy-with-hxl-tags1/table/Due to the comment size limit I could not add the whole code.   local procedure AddCountryRegionTranslation()
    var
        CountryRegionTranslation: Record "Country/Region Translation";
        EnglishLanguageTok: Label 'ENU', Locked = true;
    begin
        if not CountryRegionTranslation.IsEmpty() then
            exit;

        SetCountryRegionTranslation('AQ', EnglishLanguageTok, 'Antarctica');
        SetCountryRegionTranslation('CO', EnglishLanguageTok, 'Colombia');
        SetCountryRegionTranslation('MQ', EnglishLanguageTok, 'Martinique');
        SetCountryRegionTranslation('NE', EnglishLanguageTok, 'Niger');
[...]
    end;

    local procedure SetCountryRegionTranslation(CountryCode: Code[10]; LanguageCode: Code[10];
CountryName: Text[50])
    var
        CountryRegion: Record "Country/Region";
        CountryRegionTranslation: Record "Country/Region Translation";
    begin
        if not CountryRegion.Get(CountryCode) then
            exit;

        if CountryRegionTranslation.Get(CountryCode, LanguageCode) then
            exit;

        CountryRegionTranslation.Init();
        CountryRegionTranslation.Validate("Country/Region Code", CountryCode);
        CountryRegionTranslation.Validate("Language Code", LanguageCode);
        CountryRegionTranslation.Validate(Name, CountryName);
        CountryRegionTranslation.Insert();
    end;