[SOLVED] PowerShell error, can't run sfc /scannow to resolve

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

leo.schumacher37

Prominent
Sep 18, 2019
40
0
540
Hiya,
I'm trying to run an application, but it tells me it cannot access PowerShell, and thus cannot start. Indeed, PowerShell crashes immediately on startup. The internet suggests running sfc /scannow, chkdsk and dsim commands. dsim doesn't resolve the issue, chkdsk gets stuck at 100% and sfc /scannow cannot run due to 'corrupted files'.
Any help would be greatly appreciated
Leo
 
Solution
Going back to your original post:

"I'm trying to run an application, but it tells me it cannot access PowerShell, and thus cannot start. Indeed, PowerShell crashes immediately on startup. "

That, along with the blue screen Powershell failure and the reference therein to some PublicKeyToken, makes me believe that there is some issue with Waves Central.

Very strange.

Unfortunately that does not explain why you are unable to image/reinstall Windows.

And as for your library of audio plugins - are they all backed up and saved?

[Question: What is necessary to install/reinstall the plug-ins? I would not expect that doing so would take several days. Some reactivation process?]

You might be able to save the plugins in some...
Waves Central - this software?

https://www.waves.com/downloads/central

System Requirements link:

https://www.waves.com/support/tech-specs/system-requirements

No references noted regarding a requirement for Powershell.

= = = =

The recorded crash window references a PublicKeyToken

Could be a licensing or activation issue.

Waves Central User Guide:

https://www.waves.com/1lib/pdf/central/waves-central.pdf

Pages 5 - 9 address licensing, activation, and installation.

Your Waves Central installation may be corrupted in some manner.

You may need to contact Waves Central Support.
 
Waves Central - this software?

https://www.waves.com/downloads/central

System Requirements link:

https://www.waves.com/support/tech-specs/system-requirements

No references noted regarding a requirement for Powershell.

= = = =

The recorded crash window references a PublicKeyToken

Could be a licensing or activation issue.

Waves Central User Guide:

https://www.waves.com/1lib/pdf/central/waves-central.pdf

Pages 5 - 9 address licensing, activation, and installation.

Your Waves Central installation may be corrupted in some manner.

You may need to contact Waves Central Support.
Yeah, that's the software. Have reached out to Waves support, awaiting a reply. Have reinstalled the software and same issue. The fact Windows PowerShell crashes immediately on startup leads me to believe it's not (solely) WC's fault. I'll update with what support says but I'm not expecting much from them
 
The error message suggests that Waves Central is looking for Version 3.0

At the Command Prompt (before launching Waves Central) try

PowerShell.exe -Version 2

Version 2.0 may or may not be applicable. Microsoft/Windows has made changes.

Reference:

https://docs.microsoft.com/en-us/po...ows-powershell-2.0-engine?view=powershell-7.1

Leave Powershell open and running in the background. Test Waves Central.

However, full disclosure, I have no way to test Powershell 2.0's applicable to either Waves Central or the situation in general.

Recommend that you do some additional googling but revise the search criteria as necessary.

Do ensure that all important data is backed up and that you are otherwise prepared to recover the system.
 
The error message suggests that Waves Central is looking for Version 3.0

At the Command Prompt (before launching Waves Central) try

PowerShell.exe -Version 2

Version 2.0 may or may not be applicable. Microsoft/Windows has made changes.

Reference:

https://docs.microsoft.com/en-us/po...ows-powershell-2.0-engine?view=powershell-7.1

Leave Powershell open and running in the background. Test Waves Central.

However, full disclosure, I have no way to test Powershell 2.0's applicable to either Waves Central or the situation in general.

Recommend that you do some additional googling but revise the search criteria as necessary.

Do ensure that all important data is backed up and that you are otherwise prepared to recover the system.
Same error pops up. Will consult google some more. Hoping Waves support might be able to shed some light but I think system restore's gonna have to be the way to go. Unfortunately, Windows won't let me create a disk image as it believes there's 'unwanted software' hidden somewhere. Would be nice if it told me where/what that was lol. Will update thread with support's response.
 
Format and reinstall windows 10 clean.

https://www.microsoft.com/en-us/software-download/windows10startfresh

honestly I don't know why you are wasting time. clean install and fix it for good. PowerShell should NEVER fail. you must have malware disabling it or interfering from reading your comments above. When infected, FORMAT and REINSTALL.
Yeah, my reluctance springs from the fact it'd take several days to reinstall and reactivate my library of audio plugins, so I'd rather exhaust every other option before going through that tedious process.
 
Going back to your original post:

"I'm trying to run an application, but it tells me it cannot access PowerShell, and thus cannot start. Indeed, PowerShell crashes immediately on startup. "

That, along with the blue screen Powershell failure and the reference therein to some PublicKeyToken, makes me believe that there is some issue with Waves Central.

Very strange.

Unfortunately that does not explain why you are unable to image/reinstall Windows.

And as for your library of audio plugins - are they all backed up and saved?

[Question: What is necessary to install/reinstall the plug-ins? I would not expect that doing so would take several days. Some reactivation process?]

You might be able to save the plugins in some manner that allows restoration without the reactivation requirement. Check your Waves Central documentation and/or raise the question with Waves Central support.

For the most part I believe that the problem is on Waves Central. Be sure to ask them about the apparent Powershell requirement. If Waves Central does not have a requirement for Powershell or a specific release of Powershell then there is indeed something else going on.

That "something" may simply require a Windows reinstall to resolve - all else failing.

At some point if Waves Central does not or cannot help then you will need to reinstall Windows and start over per @Mandark.

Get Windows reinstalled then install Waves Central.

Start planning as necessary. Remember to backup everything you can .
 
Solution
Going back to your original post:

"I'm trying to run an application, but it tells me it cannot access PowerShell, and thus cannot start. Indeed, PowerShell crashes immediately on startup. "

That, along with the blue screen Powershell failure and the reference therein to some PublicKeyToken, makes me believe that there is some issue with Waves Central.

Very strange.

Unfortunately that does not explain why you are unable to image/reinstall Windows.

And as for your library of audio plugins - are they all backed up and saved?

[Question: What is necessary to install/reinstall the plug-ins? I would not expect that doing so would take several days. Some reactivation process?]

You might be able to save the plugins in some manner that allows restoration without the reactivation requirement. Check your Waves Central documentation and/or raise the question with Waves Central support.

For the most part I believe that the problem is on Waves Central. Be sure to ask them about the apparent Powershell requirement. If Waves Central does not have a requirement for Powershell or a specific release of Powershell then there is indeed something else going on.

That "something" may simply require a Windows reinstall to resolve - all else failing.

At some point if Waves Central does not or cannot help then you will need to reinstall Windows and start over per @Mandark.

Get Windows reinstalled then install Waves Central.

Start planning as necessary. Remember to backup everything you can .
I should clarify that the crashing PowerShell window does not appear when running/installing Waves Central. This appears when attempting Windows PowerShell, when searched from the search bar (not PowerShell 7, which opens fine). This is why I'm lead to believe it's a Windows issue. I should note that Spotify had trouble opening a while ago (an error message about a .dll not being where it should be). Didn't bother me much, and resolved itself after a couple of days. Could be related, not sure. If it is, that would, of course, point to Windows.

I've tried in the past to simply back up the plugins folder but it's only returned issues, presumably as so many files are referenced by the actual dlls that I'd need to copy over pretty much everything on my hard drive (which the backup utility didn't want to do). Unfortunately it has taken that long in the past - compiling a list of every plugin I need installed, finding the developers' websites, reinstalling everything, ensuring the paths are exactly the same so they can be used by old projects, license transfer &c. has proven quite the process in the past (Waves only develops a small portion of the plugins I require).

I received the following email back from Waves support:
https://drive.google.com/file/d/11_23KnvAmLoqw-YyaE2HWP1JqKq_PaS4/view?usp=sharing

The paths exist (system32 only with a capital 'S', not lowercase, as in one instance in the email - not sure if directories are case sensitive). Tried creating a new user account - same issue. Windows is up to date. It mentions PowerShell v1.0 in the email.

Coming to terms with the fact I'll have to clean install Windows... quite inconvenient (hence my stubborn urge to exhaust all options I have haha). Very appreciative of all the help though :)