Tech Support Forum banner

Powershell left on desktop after reboot.

SOLVED 
5K views 45 replies 5 participants last post by  kdugan 
#1 ·
When I reboot, Powershell is left on the desktop and I have to close that manually. This is fairly recent. Hasn't been an issue in years before. What can I do about this?

Also, I think this may be interfering with updates, since the update starts but most often, does not complete. The spinning circle (on a greenish screen) has gone on for hours. I have to pull the plug and power my PC back on before the update will complete. No gamer, just a stock PC That's been running for years. I always take the current updates. Think I should be getting rid of Powershell?
Any other ideas?
 
#3 ·
Hi, well no I would not be getting rid of powershell, it is the most current cmd module and very useful for example:-

Press the win + x keys select Powershell(admin) from the options, copy the below cmd and right click anywhere in the PS window the cmd will append to the prompt, press enter.

Get-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | Format-List | out-file $homepath\start.txt
start notepad $homepath\start.txt

Please copy paste the notepad output here this will show your startup items. This may also be a policy setting, lets look at startups first.
 
#4 ·
Hopefully you weren't thinking I meant to delete Powershell. Only if it was in the Task Manager>Startup so it wouldn't appear the way you were describing.
 
#6 ·
PS C:\WINDOWS\system32> Get-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | Format-List | out-file $homepath\start.txt
PS C:\WINDOWS\system32> start notepad $homepath\start.txtGet-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | Format-List | out-file $homepath\start.txt
Start-Process : A positional parameter cannot be found that accepts argument 'Win32_StartupCommand'.
At line:1 char:1
+ start notepad $homepath\start.txtGet-CimInstance Win32_StartupCommand ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: :)) [Start-Process], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.StartProcessCommand
 
#7 ·
Hi, well that cmd works on all machines it has been used on, including this test machine, make sure you copy it properly (exactly as you see it, and make sure you have selected powershell (admin) from the options to ensure PS is running as admin).

The cmdlet is on two lines exactly as I posted it.
 
#8 ·
Don't know why I didn't get this before.
Everything looks normal, except I've never seen that PC Dispatch thing before.

Name : CCleaner Smart Cleaning
command : "C:\Program Files\CCleaner\CCleaner64.exe" /MONITOR
Location : HKU\S-1-5-18\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : NT AUTHORITY\SYSTEM

Name : OneDriveSetup
command : C:\Windows\SysWOW64\OneDriveSetup.exe /thfirstsetup
Location : HKU\S-1-5-19\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : NT AUTHORITY\LOCAL SERVICE

Name : OneDriveSetup
command : C:\Windows\SysWOW64\OneDriveSetup.exe /thfirstsetup
Location : HKU\S-1-5-20\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : NT AUTHORITY\NETWORK SERVICE

Name : OneNote 2010 Screen Clipper and Launcher
command : OneNote 2010 Screen Clipper and Launcher.lnk
Location : Startup
User : KENT-PC\Owner

Name : updater
command : updater.lnk
Location : Startup
User : KENT-PC\Owner

Name : Adobe Acrobat Synchronizer
command : "C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\AdobeCollabSync.exe"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : OneDrive
command : "C:\Users\Owner\AppData\Local\Microsoft\OneDrive\OneDrive.exe" /background
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : Uploader
command : C:\Program Files (x86)\Seagate\Seagate Dashboard 2.0\Seagate.Dashboard.Uploader.exe
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : Google Update
command : "C:\Users\Owner\AppData\Local\Google\Update\1.3.35.452\GoogleUpdateCore.exe"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : Dashlane
command : "C:\Users\Owner\AppData\Roaming\Dashlane\Dashlane.exe" autoLaunchAtStartup
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : DashlanePlugin
command : "C:\Users\Owner\AppData\Roaming\Dashlane\DashlanePlugin.exe" ws
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : StartMenuX
command : "C:\Program Files\Start Menu X\StartMenuX.exe"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : Amazon Music
command : "C:\Users\Owner\AppData\Local\Amazon Music\Amazon Music Helper.exe"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : CS Dispatch
command : C:\Users\Owner\AppData\Roaming\j5\Wormhole1463\FunctModules\{92EEDB7D-755A-4a90-A79D-C0BD0ACF1A7F}\Wormhole3
.exe -GN:RunFromRegistry -GS:HWID:VID_0711&PID_7500 -GS:AppLoaderExeName:Wormhole.exe
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : BDAB3CD44D7D45EEC58DB422F61BD03E74CADA2F._service_run
command : "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=service /prefetch:8
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : AppEx Accelerator UI
command : C:\Program Files\AMD Quick Stream\AMDQuickStream.exe -h
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : EPLTarget\P0000000000000005
command : C:\WINDOWS\system32\spool\DRIVERS\x64\3\E_YATIMUE.EXE /EPT "EPLTarget\P0000000000000005" /M "ET-4500 Series"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : Fences
command : c:\program files (x86)\stardock\fences\Fences.exe /startup
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : EPLTarget\P0000000000000004
command : C:\WINDOWS\system32\spool\DRIVERS\x64\3\E_YATIKEE.EXE /EPT "EPLTarget\P0000000000000004" /M "WF-3620 Series"
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : CCleaner Smart Cleaning
command : "C:\Program Files\CCleaner\CCleaner64.exe" /MONITOR
Location : HKU\S-1-5-21-3949324938-3469728382-1233942007-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : KENT-PC\Owner

Name : CCleaner Smart Cleaning
command : "C:\Program Files\CCleaner\CCleaner64.exe" /MONITOR
Location : HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : .DEFAULT

Name : SecurityHealth
command : %windir%\system32\SecurityHealthSystray.exe
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : RTHDVCPL
command : "C:\Program Files\Realtek\Audio\HDA\RtkNGUI64.exe" -s
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : RtHDVBg
command : "C:\Program Files\Realtek\Audio\HDA\RAVBg64.exe" /MAXX4
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : iTunesHelper
command : "C:\Program Files\iTunes\iTunesHelper.exe"
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : Fences
command : "C:\Program Files (x86)\Stardock\Fences\Fences.exe" /startup
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : Everything
command : "C:\Program Files\Everything\Everything.exe" -startup
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : Logitech Download Assistant
command : C:\Windows\system32\rundll32.exe C:\Windows\System32\LogiLDA.dll,LogiFetch
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public

Name : EvtMgr6
command : C:\Program Files\Logitech\SetPointP\SetPoint.exe /launchGaming
Location : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
User : Public
 
#12 ·
Corday - e_YATIKEE.EXE and its companion yatimue.exe appear to be Epson monitors, although not finding much on that. Doesn't show up in ccleaner as an installed program, it doesn't seem like I should mess with that. I generally don't run registry cleans, except for missing links. My last clean was about 4 years ago., so guessing that's not my issue.

What brings up PowerShell, or even better, what dismisses it?
 
#13 ·
What brings up PowerShell, or even better, what dismisses it?
Are you able to scroll up in that PowerShell window to see what has been run? Sometimes it's there.

Whatever it is apparently is not issuing the exit command at the end of its run.
 
#14 ·
If I bring up powershell manually, I get:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\Users\Owner>
And I'm OK with that.
But if I restart my PC or get an update, It just leaves a blinking cursor in the upper left corner. Blank blue screen, otherwise. Can't scroll up at all, so I can't see any previous commands.

I can close it, but I'm thinking that when my PC updates, PowerShell may be responsible for never completing. I've left an update with the "working" spinning arrows for over 12 hours, and it hasn't completed. Then if I pull the plug and do a cold boot, it will complete. This started a couple of months ago after a regular update. Couldn't tell you which one. I always do recommended updates.
 
#21 · (Edited)
Right click on the ISO file, choose Mount from the context menu. A File Explorer window will open with the ISO file mounted as a virtual DVD.

There is absolutely no need to burn it to DVD nor to create bootable USB media, either.

https://duckduckgo.com/?q=Windows+mount+ISO
 
#22 ·
I don't have a mount listed in my context menu. I have some custom opens (for Irfanview, Sony Sound Forge, Picasa). No mount at all. Win10 home, right?

Double-clicking brings up Nero. Seems to be the issue. Found the settings for default apps by file type, changed .iso to open with file explorer, and now I have a mount! See, I really wasn't crazy! On my way...
 
#23 ·
When you have an ISO file selected, which you must, and you bring up the context menu, whether by SHIFT+F10 or right click, you do not get what's shown below? If not, then you need to post a screen shot of what you do get.

It doesn't matter what edition of Windows 10 one is using, if an ISO (AKA, disk image) file is selected Mount will be one of the options in the context menu for it.
 

Attachments

#25 ·
Well, the first question I have is: Does this show up if booting into Safe Mode?

If the answer is, "No," then it's virtually certain to be coming from something that's a startup process under Windows. And the way to track that down is by undertaking the Clean Boot process to do the process of elimination to find out what it is.

How to clean boot Windows 10 (and why you might want to)

How to perform a clean boot in Windows

Or select a tutorial that suits you from the search results from https://duckduckgo.com/?q=Windows+Clean+Boot+Process

I doubt you are going to determine the root cause without going through the tedium that is the Clean Boot process, but it's not difficult, it's just time consuming.
 
#26 ·
Hi, odd this thread say's it's solved, however we have not heard back from the OP, so I assume it is not. You could try the traditional way to repair component stores, and file verification:-
Windows comes with two native binaries, DISM and SFC, for repairing Windows via the OS system file backups, kept in %WinDir%\WinSxS.

Go to search and type:- CMD, next press ctrl+shift+enter keys , an elevated cmd prompt will open


DISM should always be run prior to SFC due to the latter being dependent on the data the former is verifying.

The cmds are:-

dism /online /cleanup-image /restorehealth (requires an internet connection)

sfc /scannow. If /restorehealth fails, re-run sfc after: dism /online /cleanup-image /startcomponentcleanup
 
#27 ·
I have no idea how the solved mark has been made, since only the OP or staff can do that, and I have no doubt that staff has not.

If the OP has done a repair install, and all indications are that he/she has, then SFC and DISM will be useless, as they've already been done as part of a repair install.

I only move along to a repair install after SFC and DISM have failed, simply because it does even more than either one of those utilities alone, and I use both frequently.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top