carl123

As a local reporter announces the release of Affinity Publisher for the iPad a deluded Affinity user can be heard screaming, in the background....
"it's not supposed to be here until the Summer of 2023."
Fortunately, his mum was there to drag him back to reality
 

As a local reporter announces the release of Affinity Publisher for the iPad a deluded Affinity user can be heard screaming, in the background....
"it's not supposed to be here until the Summer of 2023."
Fortunately, his mum was there to drag him back to reality
 

As a local reporter announces the release of Affinity Publisher for the iPad a deluded Affinity user can be heard screaming, in the background....
"it's not supposed to be here until the Summer of 2023."
Fortunately, his mum was there to drag him back to reality
 

To Eat Humble Pie:
"make a humble apology and accept humiliation."
 

To Eat Humble Pie:
"make a humble apology and accept humiliation."
 

To Eat Humble Pie:
"make a humble apology and accept humiliation."
 

To Eat Humble Pie:
"make a humble apology and accept humiliation."
 

He's holding a lamp

He's holding a lamp

SOLVED
Thanks carl123 that solved my issue by removing the update KB5017271.
Will removing this update affect how my windows 11 does it's job?

Thanks, all good/working. it is working fine now!! much appreciate your prompt replies. 

It's been 4 days since you were advised to remove that update. Please first check your Update History for any additional updates since you last checked
If you find any please advise what they are.
If none are found you can try uninstalling KB5017389 and running the .NET repair tool as advised in the post below.
Unfortunately, the OP in that thread did not report back whether that resolved their problem or not. Please report back your findings as it can help others experiencing this issue
 
 

Do you use or have previously used a second screen?
If so, the File > New screen may be opening on that

Nope, nothing to worry about at the moment if all of your other (non-Affinity) apps are working correctly
It will likely be replaced by another Windows update in the future anyway

@Timespider @bk12345
In both your screenshots KB5017271 has been reported before as causing problems
Can you uninstall that update and see if you still get the "font crashing" problem and report back here

Use the Node Tool to make a Marquee selection of the Curve (i.e. all the nodes)
Click the Break Curve button in Context toolbar
Switch to Move Tool and make Marquee selection of the "curve" 
This will give you the total number of objects selected at bottom-left of screen
This should also be the node count for closed curves    (?)
For open curves you should add one to this count   (?)
Can't fire up Designer to test the above but it works in my head
 
 

In Publisher select the Fill Tool and change the 2nd dropdown box in the Context Toolbar from Text to Frame, then change the colour.
In Designer you can try a recolour adjustment if your text is pure white, (black and other colours can be problematic)

A quickly recovered file is attached. 
Had to delete picture frame on page 238 no other checks of document done
 
TekscopesE02.15-recovered.afpub

I just looked up the Affinity Mac shortcuts online...
and "paste" is CMD+V
"Move back one" is CMD+[
So, if it worked as Windows does, I would expect you to type...
CMD+V+[            (Don't release the CMD key after typing V)
But not having a Mac I don't know anything about how that CMD key works
 
Or are you saying you can't get that shortcut ( CMD+[ ) to do anything on your Mac?

Try....
CTRL+V+[                  (Don't release the CTRL key after typing V)
Which does a paste then a Layer > Arrange > Move Back One command

(Above is for Windows, Macs may be different)
 

Have you tried selecting all layers in the Layers panel then right-clicking and selecting Expand Selection?

@ErikG
Recovered file is attached.
But the Barbarian is looking a little green. You may need to replace that image
 
Do regular backups. Not all corrupt filles are recoverable 
Barbarian Character Front-recovered.afphoto

Select all the child layers in the Layers panel, right-click and select Release

If images are linked in a document and the links to those images are broken then you will see a low-resolution placeholder image instead
First, have a look in Document > Resource Manager and check the "Status" field for any that say "Missing"
If they report missing then you can investigate further why that is

Indeed.
Why would any company add new features to V1 when the entire marketing/revenue aim is to get you to upgrade to V2 to get the new features
Critical (new) bug fixes for V1 - Yes
Minor bug fixes for V1 - Maybe (but very unlikely)