Windows 10: plz help Identifiers appended at the end of some items in Service.msc, changed for every...

I am using a non-administrator user account, and some entries in [Service.msc] seem to have identifiers appended at the end, which change every time I log into Windows. I'm curious if this is normal, and if not, I'd like to know the cause and solution. This Windows 10 installation is brand new as of yesterday, so I'm puzzled as to why there would be any issues with the system Could you please help?Sample images showing what is happening. Each of them is for same Service entry but for another time of booting in same day.

:)

 

Odd appended letters in Services

YES it does - thanks. I had much worse worries about them!

 

Odd appended letters in Services

They are 'per user' services spawned from a machine-wide parent service (which has the same name less the random _xxxxx appended.) So, using your example - 'Messaging Service' is the machine-wide service. This spawns a child service like 'Messaging Service_1a2b3c'. The next time a user logs in the child service will be spawned with different randomly appended characters like 'Messaging Service_4d5e6f'. Whilst this is supposed to help resilience, i.e. protecting the parent service, the reality is that it's mostly there to stop people fiddling with services that Microsoft don't want fiddled with... knowing that the child service is going to be randomly named every time it's started. (The same reason that Microsoft now protect an increasing number of services from being disabled or otherwise tampered with, by the addition of a Security sub-key in the registry to protect against changes to the service's Start entry.) Hope this helps...

 

Need help to identify the cause for WINRM Service locking up.

Hi all,

I have a problem with the WINRM service on our Windows Server 2019 VM instance. It's stuck in a "stopping" step. We've tried "taskkill /f /pid <could be any ID>" which usual works but not in this case. This service is used by our Server Monitoring tool

I know if we restart the server it will fix it but that is not a solution as we've done this a few times now we need to find a proper resolution.

- Event logs not specific to any error for this issue

- Curious issue along with this is a Trend agent alert also. Basically trend console cannot communicate with the server.

- I believe these are tied into the same issue but what exactly is that.......WINRM service?

- Also went to check Windows updates History and nothing is displaying even used using "PS commend wmic qfe list" nothing

Any help just to identify the underlying cause would help. Any suggestions