Windows 10 - Function Discovery Provider Host Issues. After a system restart it say's its running but needs a restart in order for the PC to show up on the network

So I'll start by saying I don't really have a clue what I'm talking about.

PC Details below:

Device name DESKTOP-Q171OF3

Processor Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz

Installed RAM 8.00 GB (7.83 GB usable)

Device ID A58F993D-6180-49F2-B1ED-F49FC275918F

Product ID 00325-81229-61254-AAOEM

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 10 Home

Version 21H1

Installed on ‎11/‎11/‎2020

OS build 19043.1320

Experience Windows Feature Experience Pack 120.2212.3920.0

The software and drivers are fully up to date.

The issue I have is that after a Powerdown of my PC where the power is turned off either by shutting down or restarting I have to manually restart the Function Discovery Provider Host via services.msc' even though it says its running already!

Without restarting it manually my PC isn't discoverable on our network.

Function Discovery Provider Host has the startup type set to Automatic (Delayed Start) as many other posts say it should be.

I've tried with the SMBv1 turned on and off and it makes no difference either way.

I've made sure network discovery is turned on, I've also checked that all associated processes are running in services and the correct Startup type is applied.

Interestingly after a system power down and Restart when I check the processes in PowerShell it shows the FDPHOST as running but the processes after that as stopped.

Then below after I have restarted the FDPHOST you can see they are all running:

So it appears that the FDPHOST is running after a power down but the others aren't, even though they are set to Automatic start (in some cases Delayed).

The strange thing is this is exactly the same issue I'm having on another brand new HP machine. I'm hoping by updating the new machine to Windows 11 it will fix the problem on that machine but I still need to find a fix for this machine as its where our accounts data is held.

Can someone please help? (in as basic terms as possible would be appreciated).

Cheers

Miles