Powershell Commands Not Parsing on Some Non-English Systems about whynotwin11 HOT 21 CLOSED

@rcmaehl just solved same issue for myself - issue was in incorrect powershell.exe 0Kb binary in C:\Windows\System32\powershell.exe (found by cmd.exe -> where powershell.exe)
And, most likely, its why powershell in your example above for user did fail too.
Found discussion https://stackoverflow.com/questions/34912830/windows-8-1-cant-start-powershell-from-a-cmd-or-powershell-prompt-this-app-c
I believe you can firstly just try to call powershell.exe without parameters and if it fails then call it by absolute path C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

from whynotwin11.

We've moved away from powershell completely. So this can be resolved as a result.

from whynotwin11.

Me too, secure boot status detection is inaccurate

from whynotwin11.

I'm going to assume this is some issue with Localization.

Can you all try Get-Partition -DriveLetter C | Get-Disk | Select-Object -Property PartitionStyle as well?

from whynotwin11.

I'm going to assume this is some issue with Localization.

Can you all try Get-Partition -DriveLetter C | Get-Disk | Select-Object -Property PartitionStyle as well?

For your proposal.

from whynotwin11.

Needs to be ran as one command

from whynotwin11.

Needs to be ran as one command

Obviously it's still gpt.

from whynotwin11.

Odd

from whynotwin11.

I have this problem too, I have a GTP system drive and two other MBRs.

from whynotwin11.

I'll need to install a few locales and language packs to try to reproduce this. It seems to mainly occur on Non-English Systems.

from whynotwin11.

May be failures to read the temp file.

from whynotwin11.

May be failures to read the temp file.

Good point. Boot Method is failing as well. Odd

from whynotwin11.

The dxdiag file seems to be working, the obvious difference being the way it's defined.
Maybe try:
$hFile = _TempFile(@TempDir, "wnw11")
@ WhyNotWin11.au3 line 176

from whynotwin11.

@maksimus256 @MisakaSakura

Can you all run the file in the attached zip?
Test.zip

from whynotwin11.

@maksimus256 @MisakaSakura

Can you all run the file in the attached zip?
Test.zip

What does that mean?

from whynotwin11.

I'll need to install a few locales and language packs to try to reproduce this. It seems to mainly occur on Non-English Systems.

Maybe not necessarily this problem, because your software is very useful in coolapk, a Chinese community, like me, which is actually in the minority.

from whynotwin11.

@maksimus256 @MisakaSakura
Can you all run the file in the attached zip?
Test.zip

What does that mean?

Means powershell output is failing 😞 , Doesn't even create an output file.

from whynotwin11.

Same issue here. System Locale is "German (Germany)".

from whynotwin11.

@maksimus256 @MisakaSakura

Can you all run the file in the attached zip?
Test.zip

my localization is russia

from whynotwin11.

@rcmaehl
Two thoughts:

• It may be good to define encodeing in Powershell and AutoIt to avoid encoding bugs.
• It may be good to use -Force in Powershell for overwrite read-only files.
• With (command).Property you get the value insted the table. Ex: (Get-Partition -DriveLetter C: | Get-Disk | Select-Object -Property PartitionStyle).PartitionStyle
• You sould add -ExecutionPolicy Bypass to all Powershell commands.

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/out-file?view=powershell-5.1#parameters

from whynotwin11.

@rcmaehl just solved same issue for myself - issue was in incorrect powershell.exe 0Kb binary in C:\Windows\System32\powershell.exe (found by cmd.exe -> where powershell.exe)
And, most likely, its why powershell in your example above for user did fail too.
Found discussion https://stackoverflow.com/questions/34912830/windows-8-1-cant-start-powershell-from-a-cmd-or-powershell-prompt-this-app-c
I believe you can firstly just try to call powershell.exe without parameters and if it fails then call it by absolute path C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

If this fixes it, I swear

from whynotwin11.