The attached pop-up occurs mosr times I shut thé system down. It disappears before I can read it and shut down occurs OK.
Any ideas? Powershell has not been used in ages.
Last edited by Ex_Brit; 25 Sep 2023 at 09:07.
This tutorial lists the permitted file types and sizes.
How to Upload and Post Screenshots and Files at Ten Forums
History:
- when did this start?
- what happened shortly before that?
Pic now added to post at top.
History: It started a few weeks ago and is intermittent
I was reading posts on Neosmart Forums before it happened.
It doesn't seem to be affecting anything.
1. Try a clean boot and then see if it still occurs. If not, then work backwards to determine the cause.
2. Examine your Reliability History and see if there's anything related to it. Noting the time can help.
However it may be too quick for a report to be logged.
3. Check your event log around the time this happens.
There may be a clue in this similar report, but it's not specific enough to give a solution as such.
[SOLVED] - Powershell error popup dialogue box during shutdown | Tom's Hardware Forum
Powershell.exe is in use many times a day to automate system processes, mainly for the collection of diagnostic data.
Are there any relevant entries in Event Viewer's (eventvwr.msc) Application log? (Event Viewer > Windows Logs > Application)
Probably the easiest way is to query the last 20 entries:
1. Right-click on Start then choose Windows PowerShell (Admin) from the context menu.
2. When the PowerShell console opens, copy/paste/type the following then press ENTER/RETURN:
If you want to redirect this output, say to a text file on your desktop, use the following instead:Code:Get-EventLog -LogName Application -Newest 20 | Format-Table -AutoSize
This will create a text file called last_20_applogs.txt.Code:Get-EventLog -LogName Application -Newest 20 | ft -AutoSize > (join-path ([environment]::GetFolderPath('Desktop')) "last_20_applogs.txt")
Hope this helps...
Newest 20 or even 40 does not open last evening's items, is there a way of specifying the date?
Sorry I'm not familiar with Event Viewer or Powershell commands.
The EV shows only some errors for Shell Experience or words to that effect.
That suggests you have lots of Application events being written the the Application log, in which case limiting the results to a single date may not actually help you work out what's going on with your system.
Instead of removing the -Newest parameter completely, try changing the parameter to 100, 200 or even more until it encompasses yesterday.
Oh... and answer @dalchina's query, particularly about 'Reliabililty History'.
Hope this helps...
Quote
