It seems something prevented him from running the service, i suspect another tool He added UsoSvc into Windows Update Blocker v1.1 and disabled and enabled and he's problem is fixed For mine i never prevent the user i only prevent the system so user can have control
so i tried to diable with Windows Update Blocker v1.1 and than to disable with StopWinUpdates v2.2 and reeneble only with StopWinUpdates v2.2 and i can see the windows update so this was not the tool that blocked the UsoSvc service
could be a registry setting or a registry hack that prevented the usosvc service from working correctly
@BALTAGY Looks like defender update task only create itself in current account, later created new accounts don't have defender update task. this can be fixed i guess.
First post updated to v2.3 Windows Defender task will be created in Microsoft location so the task can still exist when creating a new user
I tested it in an insider build last month and it was working, waiting RTM to be released since my quota not helping in downloading many insider builds
I'm just waiting the business edition, i think it takes a few days after RTM It seems business edition and LTSC wont take days, waiting the links to download them and test