New
#10
Hello Mike @mta3006,
You have a local account, but you had chosen to sign in to all apps with your Microsoft account like below at one point when signing in to an app.
Thanks @Brink,
On my last clean install, when 1809 re-re-re-released, I decided to go easy on the app cleanup, as I finally got tired of CCleaner's unsolicited activities, and left the Microsoft Store up as well, so I could get updates on apps. And, boy, how those apps update... then I found the control in the Store to hold off the tidal wave of updates (I have limited data at home).
I decided to select the 'Stop signing in to all apps automatically' option, and all went back to the normal local account behavior. I am still able to access the Store, though. Do you have any links to a "Microsoft Accounts and Windows 10 for Idiots" tutorial?
Thanks again for all the work you put in here!
You're most welcome.
We do indeed have a lot of Microsoft Account tutorials listed under M in the tutorial index.
I tried this today and for some reason I got the error message -
Get-LocalUser : The term 'Get-LocalUser' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Get-LocalUser | Select-Object Name,PrincipalSource
+ ~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-LocalUser:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Any ideas how to solve this issue?
Blessings
Thanks Brink,
Actually that was part of the problem - I was trying to run it in AutoIT. That was where I got the error message. When I tried the identical line in Powershell it worked. I had been doing another powershell command in Auto IT and that worked ...
The run first line produced a blank box, not like when run in Powershell, the second line produced the same info as run in Powershell?
Any ideas welcome. Blessings
- - - Updated - - -
I really don't like how the minute I ask a question I see the answer!
I was going to test it again in Powershell and saw that there is a Powershell (x86) so I tried it in that and it failed. It gave the same error messages as in Auto IT whereas the Get-WinEvent gave the correct response. So the question is now, how can I use Get-LocalUser with a 32 bit processor?
Blessings
@MusiqueGraeme,
You could see if either command below may work in AutoIt if it will use standard command prompt commands.
powershell "Get-LocalUser | Select-Object Name,PrincipalSource"
OR
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe "Get-LocalUser | Select-Object Name,PrincipalSource"
Thanks @Brink.
If I run the command in the 32 bit Powershell and it gives the error, doesn't that imply that this will always fail on a 32 bit machine? Do I not need another command to run to access, if possible, the same information?
Sorry I don't know how to put your name in blue..
Blessings
The command is valid on both 32-bit and 64-bit Windows 10.
How are you opening PowerShell?
Open Windows PowerShell in Windows 10