Windows Server 2025 - wmic Error

[mildblue]

An error occurs even though the 'wmic' service is working properly in Windows Server 2025.
Isn't there a solution?

I downloaded "hfs-windows-x64-0.53.0-rc20" and tried it, but the same error occurs.

[rejetto]

i don't have windows 2025.
Maybe it doesn't have "chcp" command?
please copy and paste the command, the whole line, including chcp and wmic, on a command prompt, and see the result.

[mildblue]

저는 2025년 윈도우가 없습니다. "chcp" 명령어가 없는 것은 아닐까요? 명령 프롬프트에 chcp, wmic을 포함한 전체 행인 명령을 복사하여 붙여넣고 결과를 확인하십시오.

It's the same when you run it in administrator mode.

Windows Server 2025 RTM.zip

[rejetto]

the error 44210 seems to be specific of wmic, i guess chcp has nothing to do with it.
try running as administrator, to see if that solves.

[rejetto]

hey, thanks but i cannot install Windows 2025 to make the test :)
thanks for the "administrator" test.
when i said the whole command, i meant "wmic service get ProcessId", not just "wmic". Let me know if you can try this, i'm interested in the result.
Also, i have a possible fix for your problem, it's included in this version:
https://github.com/user-attachments/files/16142024/hfs-windows-x64-0.53.0-rc21.1.zip
please let me know if it works.
it's just a workaround, in case the command fails, because it's not a critical problem: that command is necessary only for HFS to know if it is running as a service, because as a service it shouldn't attempt to auto-update. I repeat, it's not critical.

[mildblue]

Thank you, I run it with this version and it works fine.

[rejetto]

thank you for your feedback!
that output is quite weird, something's wrong with it, as any system has services running, yours too, but it refuses to provide the list

but it's not even an empty list, because it doesn't include the first line, the one with "ProcessId", so i guess the command just failed, as it does when called by HFS.
I guess we'll live with that for now, but i have more attempts to do in future versions.

[mildblue]

Microsoft has recently made wmic.exe obsolete in Windows versions. Instead, we recommend using PowerShell. Therefore, it is likely that wmic.exe will be completely removed in future versions.
Here are some PowerShell commands you can use instead of wmic.exe:

Service Information Inquiry:

powershellCopyGet-CimInstance -ClassName Win32_Service | Select-Object Name, ProcessId

Inquire process information:

powershellCopyGet-Process | Select-Object Name, Id

Look up disk information:

powershellCopyGet-CimInstance -ClassName Win32_LogicalDisk

System Information Inquiry:

powershellCopyGet-CimInstance -ClassName Win32_ComputerSystem
These PowerShell commands can replace most of the features that wmic.exe provided.

^^;

[mildblue]

const { exec } = require('child_process');

const powershellCommand = 'Get-Process | Select-Object Name, Id | ConvertTo-Json';

exec(powershell -Command "${powershellCommand}", (error, stdout, stderr) => {
if (error) {
console.error(Error executing PowerShell command: ${error});
return;
}
if (stderr) {
console.error(PowerShell command stderr: ${stderr});
return;
}

try {
const processes = JSON.parse(stdout);
processes.forEach(process => {
console.log(Name: ${process.Name}, ID: ${process.Id});
});
} catch (parseError) {
console.error(Error parsing PowerShell output: ${parseError});
}
});