builtbybel / builtbybel/CleanmgrPlus
Windows Shadow Copies.csc script preview command Echo stops processing of futher scripts until the therefore opened command line window is manually closed.
- Dominant language
- GSC
- Stars
- 757
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Forget about everything at the end. I now see the real problem. I read through #Rules.txt and came to this conclusion that everything at the end is bullshit. I just wondered why running the preview, leaves a command line window open. Couldn't it be change like this:
When preview is run, the preview executes each `TaskX=Echo|blabla` command with `cmd /k` and therefore leaves the command line window open so one can read the output, but this interrupts the whole process of running all previews one after another until the command line window is closed. couldn't this be done like `Exec` with an optional `SHOWCLI` at the end? So the command could be normally `cmd /k command line here` but if it's `TaskX=Echo|command line here|SHOWCLI`, it's executed with `cmd /c` and the output is redirected and printed in the preview window of clearmgr+? So one get's the command line output, but the process continues?
#########################
**Old Title: I have a problem with Windows Shadow Copies.csc on Windows 11 and the search lead me to #18.**
The current file seems updated and says
```
[Files]
Task1=Echo|%WinDir%\SysNative\vssadmin list shadows
Task2=Exec|%WinDir%\SysNative\vssadmin delete shadows /all|SHOWCLI
```
I searched a bit and starting Windows Vista x64 the folder C:\Windows\SysNative was introduced as a link to C:\Windows\System32. System32 contained all 64-bit files, while SysWOW64 contained the 32-bit files and 32-bit programs where redirected there. A bit unreasonable to me, but okay...

In case a 32-bit program wanted access to a 64-bit file, it could use the redirect via C:\Windows\SysNative
But on Windows 11 x64:
```powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Installieren Sie die neueste PowerShell für neue Funktionen und Verbesserungen! https://aka.ms/PSWindows
PS C:\Users\ladik> $env:PROCESSOR_ARCHITECTURE
AMD64
PS C:\Users\ladik> C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
Windows PowerShell
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Installieren Sie die neueste PowerShell für neue Funktionen und Verbesserungen! https://aka.ms/PSWindows
PS C:\Users\ladik> $env:PROCESSOR_ARCHITECTURE
x86
PS C:\Users\ladik> cmd
Microsoft Windows [Version 10.0.22000.258]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\ladik>dir /AD %WINDIR%\System*
Datenträger in Laufwerk C: ist SYSTEM
Volumeseriennummer: 1089-3CDD
Verzeichnis von C:\Windows
05.06.2021 14:10 System
14.10.2021 15:42 System32
05.06.2021 20:00 SystemApps
12.10.2021 22:52 SystemResources
14.10.2021 09:44 SystemTemp
0 Datei(en), 0 Bytes
5 Verzeichnis(se), 301.610.512.384 Bytes frei
```
It seems like this redirect mechanism doesn't exist anymore in Windows 11. No idea how to handle this for all OS version. other than changing it by hand wont work for me atm.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Windows Shadow Copies.csc and the command-preview handling described in the issue, and read #Rules.txt for the Echo and Exec syntax. Reproduce a preview containing multiple tasks, then trace how cmd /k is launched; done means Echo output is visible in the preview while subsequent scripts continue without manually closing a command window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100