[SOLVED] Unable to install Powershell 5.1 on Windows 7 SP1 x64

[PeterJ]

Uninstall HardDiskSentinel. Its not needed for now.
Try to start Process Monitor again and report the result.

 

[whiteindian]

No change...

But I found that Process Monitor v 3.84 is the latest version that works under Vista/W7
Process Monitor on Windows 7 / Sysinternals system requirements - Microsoft Q&A
Please be patient and I report a result.

 

[whiteindian]

Capture Process Monitor Trace

Logfile.PML CBS.log

OK

 

[PeterJ]

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[whiteindian]

OK.
Fizlog.txt

 

[PeterJ]

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

Download the attachment regfix.reg and extract it.
Open the extracted folder, double-click the file regfix.reg.
When prompted allow to change the registry settings.
Report the result.

Step 2:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[whiteindian]

Step 1:

Cannot import .reg Error accessing the registry
What to do now?

 

[PeterJ]

Try to import this attachment.

 

[whiteindian]

Try to import this attachment.

OK.
This file is much smaller than the first one.
So what to do now.
Step2?

 

[PeterJ]

Great. Yes, perform Step 2 in message #146.

 

[whiteindian]

OK.

 

[PeterJ]

Perform the instructions in message #133 again.

 

[whiteindian]

OK.
Logfile.PML CBS.log

 

[PeterJ]

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

Download the attachment regfix3.reg and extract it.
Open the extracted folder, double-click the file regfix3.reg.
When prompted allow to change the registry settings.
Report the result.


Step 2:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[whiteindian]

Step1
Another type of error

"Not all data was successfully written to the registry. Some keys are open by the system or other processes"

 

[PeterJ]

Proceed with step 2 first.

 

[whiteindian]

OK.

 

[PeterJ]

FRST Scan:

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on English.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[whiteindian]

OK.

 

[PeterJ]

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.