Windows 10: closing personalization window in CMD

Task Manager is probably looking further into the process than tasklist does (or taskkill)

 

Hi My1,

Will this command work for you?
Code: powershell "$shell = New-Object -ComObject WScript.Shell; $shell.AppActivate('Personalization'); $shell.SendKeys('%{F4}')"[/quote]

 

takes some time but works.

 

Yes. Starting an instance of PowerShell can be really slow. The slowness is especially noticeable when executing such trivial tasks.


If you're okay with using temp files, calling a VBScript from your batch script will be a much quicker solution than PowerShell.

Code: @echo off REM Open a "Personalization" window control /name Microsoft.Personalization REM One second minimum delay required timeout 2 REM Close the "Personalization" window set temp_vbs="%TEMP%\%~nx0.tmp0.vbs" ( echo Dim objShell echo Set objShell = CreateObject("WScript.Shell"^) echo If objShell.AppActivate("Personalization"^) = True Then echo objShell.SendKeys("%%{F4}"^) echo End If ) > %temp_vbs% cscript %temp_vbs% //B del %temp_vbs% REM[/quote]

Also, My1, I'd like to know where you found taskkill /fi "WINDOWTITLE eq Personalization" on SevenForums? This command only works under very specific conditions. It won't work most of the time.

 

I have no problems with tempfiles.

also I found it here when I wanted to google how to shut this window down in a script, post 3

Is it possible to create a windows batch file to do this? - Windows 7 Help Forums

btw this thing works epic, I have now completed my wanted script, which can save a lot of work when working with themes in W10 9926+.

 

In that SF thread, Duzzy's code suggestion to Neutron's script doesn't actually work there (always yielding the "INFO: No tasks running with the specified criteria." error). Not in Windows 7, not in Windows 10.

Excellent news.

 

it did work for Mystere

also you need admin in the cmd. so I added this little thing at the very beginning:

Code: @echo off :: BatchGotAdmin :------------------------------------- REM --> Check for permissions >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system" REM --> If error flag set, we do not have admin. if '%errorlevel%' NEQ '0' ( echo Requesting administrative privileges... goto UACPrompt ) else ( goto gotAdmin ) :UACPrompt echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs" set params = %*:"="" echo UAC.ShellExecute "cmd.exe", "/c %~s0 %params%", "", "runas", 1 >> "%temp%\getadmin.vbs" "%temp%\getadmin.vbs" del "%temp%\getadmin.vbs" exit /B :gotAdmin pushd "%CD%" CD /D "%~dp0" :--------------------------------------[/quote]

 

Strange. It doesn't work for me. I hope Mystere will jump on here and explain how he opened the Personalization window. How this window is opened is important for the mentioned Taskkill command to work.

And here's the PowerShell alternate: shorter, cleaner and no temp files needed. However, the same drawback of speed applies.
Code: net session >NUL 2>&1|| powershell Start-Process '%0' -Verb RunAs&& exit /b|| exit /b[/quote]

 

well I dont want to wait that long, it maybe shorter, but a temp file that is deleted roughly 2 sec after exec is sth. I dont care about...

if they could speed up Powershell it would be nice tho...

 

I opened it by right clicking on the desktop and choosing Personalize. Then Opened a command prompt elevated and typed the taskkill command, which worked perfectly.

 

Agreed: speed up the PowerShell initialization time. PowerShell is fast. It's its environment which takes time to setup that is the cause for all the slowness.

What would be nice would be to see some way of being able trigger VBScript script directly within batch files; without the need of external temp files.

I'm puzzled. I tested the same procedure on both Windows Professional x64 and Windows Ultimate x86, and both raise the "INFO: No tasks running with the specified criteria." error.

Oh well. Best not to think too hard about it... *Huh

 

true I mean we have woking ways both short/clean and fast (I prefer the latter one, I mean the temp file does get deleted afaik)