Does Powersgell have a cache that needs to be cleared?

kayal24 · 2020-12-01T00:44:32.000Z

I worked with several scripts during the day without making any changes. At the end of the day, a script was not working properly. I did a restart of the Powershell and still not functional. I restarted my computer and everything is back to normal. Any solution for this?

I was wondering if i use this following command is a good solution to clear the cache?

Remove-Variable * -ErrorAction SilentlyContinue; Remove-Module *; $error.Clear();

Robert762 · 2020-12-01T11:15:45.000Z

Ak2595:

I worked with several scripts during the day without making any changes. At the end of the day, a script was not working properly. I did a restart of the Powershell and still not functional. I restarted my computer and everything is back to normal. Any solution for this?

I was wondering if i use this following command is a good solution to clear the cache?

Remove-Variable * -ErrorAction SilentlyContinue; Remove-Module *; $error.Clear();

Neally · 2020-12-01T13:14:47.000Z

No, there is no cache.

However it depends what you were doing.

The PowerShell ISE is known for odd behavior, or you might have overwritten variables by accident.

Feel free to share the code and will have a look

If you post code, please use the ‘Insert Code’ button. Please and thank you!

PLEASE READ BEFORE POSTING! Read if you're new to the PowerShell forum! Programming & Development

Hi, and welcome to the PowerShell forum! Don’t apologize for being a “noob” or “newbie” or “n00b.” There’s just no need – nobody will think you’re stupid, and the forums are all about asking questions. Just ask! Use a descriptive subject. Don't say "Need help" or "PowerShell Help", actually summarize what the problem is. It helps the rest of us keep track of which problem is which. Don’t post massive scripts. We’re all volunteers and we don’t have time to read all that, nor will we copy, past…

kayal24 · 2020-12-01T14:13:00.000Z

Definitely noticed with the ISE (PowerShell 5.1) that it seems to hold onto scripts in memory. Closing it and reopening it corrects that. Moving the PowerShell 7 is a goal. Well thanks

Neally · 2020-12-01T16:21:53.000Z

The ISE is that, an ISE (integrated scripting environment), you can r un powershell 7 on the ISE as well, but VS Code is definitely nicer

You can also use 5.1 and 7 in VS Code.

jimlong3 · 2020-12-01T16:24:31.000Z

I think you’re on to something here. I thought I had/have a virus!

As I’ve tried to enhance my PowerShell skills, I have noticed that a lot of what I expect (“It Just Works”, “re-running the same code should produce the same results”, etc.) just doesn’t happen in PowerShell. Sometimes. Or they do, depending on something I can’t see.

This is not about the oddball characters used in WWWeb pages like quotes, dashes, etc. This is about a working script that “just” stops working, until you restart PS, reboot, contemplate your navel, eat Hootersville rutabagas, or something else & they go back to working again. Or not.

More annoying to me is how, when a script starts failing (after working), I copy & paste the contents of the script .PS1 file to the ISE or the PowerShell prompt to test & fix it, only now it works, but when I take what works in ISE/prompt & replace the contents of the .PS1 file with the code that works, then execute the .PS1, now it fails. The only difference is “in a .PS1” vs. “NOT in a .PS1”.

ATM, I suspect something in the param() block handling, but I’m still investigating. Does your script use param()?

I don’t think it’s the ISE, per se, since when I test this, I do test in both places. “Same results”?? HA! I’ve given up any hope of that!!! But the behavior is similar enough I don’t think it’s the ISE’s fault.

The hardest part is, I can watch a known-good script fail, and then when I try to show someone the failure, that time it will work! Or not.
.
.

Sorry to hijack your thread. This pisses me off more than SW would allow me to say in public & I got “triggered”.

Neally · 2020-12-01T16:32:14.000Z

How does it fail? Did you add logging and debug so you see where it fails?

PowerShell is just stringing all the things together. it’s (usually) not Powershell’s fault that the powershell is intermittent but the stuff is involved that has a hickup at times.

If a script works today, then stops working, but works again after a reboot, it’s very unlikely it’s powershell’s fault, but whatever it is accessing or doing, that might have issues.

kayal24 · 2020-12-01T17:03:26.000Z

Oh this is something that’s infrequent, couldn’t tell you, not sure if its worth investigating. And if it was something in the script, it wouldn’t work multiple times throughout the day…

PatrickFarrell · 2020-12-02T02:46:55.000Z

FYI, Powershell ISE also is a single pane when it comes to variables and your tabs. You could have 3 files open in different tabs, but if you have $Computer set by something in tab A, and you use that variable in tab B without initializing it first, then it will have a value there too.

Get the the habit of initializing your variables at the start of you code.