Windows 10: PowerShell parser problems

I have been struggling with a PowerShell script for days. Older versions from a year ago are fine. New versions, some with only minor changes, raise syntax errors. The lines flagged are fine. Very similar lines are not flagged. For days I assumed something wrong earlier was the problem, like unbalanced quotes, parentheses, or curly braces. But I found nothing. Finally, I copied a version from a year ago that still raises no errors. I modified some comments and revised variables for copyright and report filename, all at the top. Even with these minor changes the script raises errors hundreds of

:)

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast:

 

Windows 11 parser error 0x80004005 won't let me UNINSTALL app

Please create a new machine.config file. See the solution in this article:

PowerShell Closes Immediately When Launched; Machine.Config Parser Error

(Ignore the article's title.)

If that doesn't help, please contact the program's support team, as Derrick [MSFT] suggests.

 

MSXML 4.0 SP3 Parser problem

Hi, received an email from MS Community asking if I had resolved this issue. As I have had no response to my last reply the answer is no. I am still left with the quandry outlined above. Is it safe to uninstall MSMXL 4 SP3 parser ? Is there a potential security
risk in having version 4.30.2100 and if there is how can I prevent any vulnerability by either downloading version 4.30.2117 or uninstalling MSXMX 4 SP3 parser altogether as suggested on the Secunia forum ?

I contacted MS support via 'chat' but it was not a very productive experience and although the adviser trotted out the

advice against uninstalling only confused me further with additional information and I am not sure grasped what I was on about.

Again any further help appreciated as I am stuck.