I cant run DISM and sfc from Win PE.

@bug locker, I am trying to find out the cause of "Active code page: 65001" being shown in the LOG file.
Please run the following script and upload both "Tuneup.log" and "T.txt" from your desktop.

Matthew Wai said:

@bug locker, I am trying to find out the cause of "Active code page: 65001" being shown in the LOG file.
Please run the following script and upload both "Tuneup.log" and "T.txt" from your desktop.

@bug locker, please run the following command via Command Prompt and post the output:

WMIC pagefile list /format:list

It takes just a couple of seconds.

Matthew Wai said:

@bug locker, please run the following command via Command Prompt and post the output:

WMIC pagefile list /format:list

It takes just a couple of seconds.

I have to give up trying to find out the cause of "Active code page: 65001" being shown in the "Tuneup.log" file attached to your post #72.

Code:

        [WMIC PageFile list]

Active code page: 65001
ECHO is off.
AllocatedBaseSize=2432
CurrentUsage=10
Description=C:\pagefile.sys
InstallDate=20210127175401.488940+120
Name=C:\pagefile.sys
PeakUsage=11
Status=
TempPageFile=FALSE

@bug locker, could you please run the script attached below and post the output?

The OP runs Greek Windows, which has "Active code page: 65001", about which I know nothing.
The OP's Windows may behave differently from English Windows.

Matthew Wai said:

The OP runs Greek Windows, which has "Active code page: 65001", about which I know nothing.
The OP's Windows may behave differently from English Windows.

Notes: 1) In the meantime I have changed the name of the Desktop folder from "επιφάνεια εργασίας" to "Desktop". So maybe we need to run the batch files that have a problem , I do not remember which.
2) The default code page for Command proccessor is in Greek Windows 737. Because with it the Greek characters that are in batch files appear corrupted I have changed it to 65001 which are displayed correctly. Example :

3) I have spoken with Microsoft Phone Support and we have confirmed that this bug does not affect my computer but any computer running Windows 10.

@bug locker, please run the script attached below and see whether "Testing.txt" will be created on your desktop.