Archive for the ‘Windows’ Category
Posted by jpluimers on 2021/09/14
Since Chrome changes over time, the batch file below from [WayBack] Run chrome in fullscreen mode on Windows – Stack Overflow also changes:
@echo off
echo Countdown to application launch...
timeout /t 10
"C:\Program Files (x86)\chrome-win32\chrome.exe" --chrome --kiosk http://localhost/xxxx --incognito --disable-pinch --no-user-gesture-required --overscroll-history-navigation=0
exit
On most of my systems. Chrome is at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe, so I need to change the path anyway.
–jeroen
Posted in Batch-Files, Chrome, Development, Google, Power User, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2021/09/10
SwiftOnSecurity is a great account to follow.
One tweet was the base of my post [WayBack] On Windows, having an empty password can improve security.
Another tweet the base of this one.
Doug is great!
Swift has some great github resources too:
–jeroen
Posted in Power User, Security, Windows | Leave a Comment »
Posted by jpluimers on 2021/09/09
When you do a choco upgrade all --yes on a system that – during upgrade – becomes low on disk space, you can end up with a lot of empty .nupkg files.
For those package, Chocolatey will not recognise they are installed any more.
The fix is this:
- increase disk space so at least 5 gigabytes is free
- split the choco upgrade process so it checks before each upgrade that this diskspace is indeed free
- list all choco .nupkg files of length zero ordered from oldest to newest
- for each package, delete the .nupkg file if it exists, then force install it with the
--force parameter before the --yes parameter like in
choco install --force --yes chocolatey
- when all packages have been done, then
choco upgrade --all --yes
I wrote a few PowerShell scripts assisting me in cleaning up the mess.
choco-list-installed.bat
:: https://superuser.com/questions/890251/how-to-list-chocolatey-packages-already-installed-and-newer-version-available-fr
choco list --localonly %*
choco-show-installed-package-names.bat
:: `--limit-output` does not show Chocolatey version header and count footer.
:: `--id-oonly` omits the version number, so you only get the package name
choco list --local-only --limit-output --id-only
choco-show-installed-package-names-and-versions.bat
:: `--limit-output` does not show Chocolatey version header and count footer.
choco list --local-only --limit-output %*
choco-reinstall-empty-nupkg-by-names.ps1
- [WayBack] Powershell – Finding 0-byte Files | Another computer blog
- [WayBack] windows – Where is the Chocolatey installation path? – Stack Overflow:
There is an environment variable set on installation, ChocolateyInstall, which is set to C:\Chocolatey by default in versions of Chocolatey less than 0.9.8.27. After that, this defaults to C:\ProgramData\Chocolatey.
NOTE: By default, the C:\ProgramData folder on Windows is hidden. You will either need to enable hidden files and folders through Folder Options | View or you can navigate directly to the path shown above by copy/pasting directly into the Windows Explorer address bar.
In version 0.9.9 of Chocolatey, it actively moves from the old folder location to the new one.
- [WayBack] string – Powershell concatenate an Environment variable with path – Stack Overflow
A convenient way to obtain the string value rather than the dictionary entry (which is technically what Get-ChildItem is accessing) is to just use the variable syntax: $Env:USERPROFILE rather than Get-ChildItem Env:USERPROFILE.
$localpath = "$env:USERPROFILE\some\path"
…
Also, the Join-Path cmdlet is a good way to combine two parts of a path.
$localpath = Join-Path $env:USERPROFILE 'some\path'
<#
https://learningpcs.blogspot.com/2009/12/powershell-finding-0-byte-files.html
Zero length .nupkg files sorted by oldest first.
These are packages that choco will not show and likekly need a forced reinstall.
Choco does remember the version that was installed (so not all the choco config is hosed).
- https://stackoverflow.com/questions/28235388/where-is-the-chocolatey-installation-path/28239451#28239451
- https://stackoverflow.com/questions/41047123/powershell-concatenate-an-environment-variable-with-path/41047343#41047343
/#>
$LibPath = Join-Path $env:ChocolateyInstall 'lib'
$NuPkgExtension = 'nupkg'
$NupkgFilter = "*.$NuPkgExtension"
## Remove the empty .nupkg files for each argument
$args | ForEach-Object {
$PackageName = $_
Write-Output "Deleting any empty $PackageName.$NuPkgExtension under $LibPath :"
Get-ChildItem -Path $LibPath -Recurse -Filter $NupkgFilter | Where-Object {
($_.Length -eq 0) -and ($_.BaseName -eq $PackageName)
} | Sort-Object LastWriteTime | ForEach-Object {
$PackageFullName = $_.FullName
Write-Output "Deleting $PackageFullName"
Remove-Item $PackageFullName
}
}
## Force install the chocolatey package for each argument
$args | ForEach-Object {
$PackageName = $_
Write-Output "Installing $PackageName with Chocolatey:"
choco install --force --yes $PackageName
}
Link lists
Some more links that helped me solve this:
Some links on errors I encountered while recovering from this:
- Checksum errors like[WayBack] (sysinternals) checksum error · Issue #756 · chocolatey-community/chocolatey-coreteampackages · GitHub are often caused by the chocolatey package downloading the most recent installer despite the package version. Two solutions:
- Pass
--ignorechecksum to choco --install (see [WayBack] CommandsInstall · chocolatey/choco Wiki · GitHub)
- First uninstall using the
--force parameter
[Archive.is] Chocolatey Software | Sysinternals 2019.6.29
Sysinternals Suite is going to be installed in ‘C:\ProgramData\chocolatey\lib\sysinternals\tools’
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error – hashes do not match. Actual value was ‘A510C31C2CC591A16F342E7CBA5DC8409EAF08C9B56729CF132C95C69E196787’.
Downloading sysinternals
from ‘https://download.sysinternals.com/files/SysinternalsSuite.zip’
Progress: 100% – Completed download of C:\Users\devCrPhoneDebug\AppData\Local\Temp\2\chocolatey\sysinternals\2018.12.27\SysinternalsSuite.zip (23.51 MB).
Download of SysinternalsSuite.zip (23.51 MB) completed.
Error – hashes do not match. Actual value was ‘A510C31C2CC591A16F342E7CBA5DC8409EAF08C9B56729CF132C95C69E196787’.
ERROR: Checksum for ‘C:\Users\devCrPhoneDebug\AppData\Local\Temp\2\chocolatey\sysinternals\2018.12.27\SysinternalsSuite.zip’ did not meet ‘b14466c6bf3be216ea71610a3f455030e791cd5ad1b42a283886194205d176b0’ for checksum type ‘sha256’. Consider passing the actual checksums through with –checksum –checksum64 once you validate the checksums are appropriate. A less secure option is to pass –ignore-checksums if necessary.
The install of sysinternals was NOT successful.
Error while running ‘C:\ProgramData\chocolatey\lib\sysinternals\tools\chocolateyInstall.ps1’.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
- Packages that cannot be found at all:[WayBack] “imagemagick not installed. The package was not found with the source(s) listed” – Google Search
- This means that Chocolatey cannot find a dependency, but will not tell you which one. It also happens during package testing:[WayBack] imagemagick v7.0.9.7 – Failed – Package Tests Results · GitHub
- Solve this by fixing all other empty
.nupkg files first, which will give you an idea on the potential missing dependencies. Retry by forcing reinstall each dependency.
- Dependencies that cannot be found, which can be caused by more empty
.nupkg files. Example: [WayBack] Unable to resolve dependency · Issue #206 · chocolatey/choco · GitHub
- Solve this by each time a dependency is not found, include on the
choco-reinstall-empty-nupkg-by-names.ps1command, then retry.
–jeroen
Posted in Chocolatey, COBOL, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows, Windows 10 | Leave a Comment »
Posted by jpluimers on 2021/09/09
I knew I could run shell:startup and similar shortcuts from the Explorer address bar or the Windows-R “run” prompt.
First I learned that via [WayBack] tablet – How to set Google Chrome to automatically open up and in full screen – Super User.
Then via [WayBack] “shell:startup” – Google Search, I found [WayBack] Location of the Startup folder in Windows 10.
It took a while before I realised you can also run them from the command-prompt, batch-files or PowerShell scripts prepending them with start:
start shell:startup
That one will open a new explorer window in the user startup folder from either the command-prompt, a batch file or PowerShell script..
The shell: shortcuts can contain spaces. So for instance there is shell:common startup that opens the common startup folder.
Starting it from the command prompt, batch file or PowerShell script is different: because of the spaces you will get the error on the right unless you add double quotes:
start "shell:common statartup"
All shell: commands that you can run in the same way: double quotes work for both the ones requiring spaces and the simple ones nor requiring spaces.
Virtually each new Windows version (even most Windows 10 major builds) gets new shell: commands.
A good source with an up-to-date and historically accurate of shell: commands list is at [WayBack] Shell Commands to Access the Special Folders in Windows 10/8/7/Vista/XP » Winhelponline,
You can get the current list by recursively enumerating the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions registry key, which consists of a list of Explorer folder GUIDs having Name, ParentFolder and RelativePath value names.
–jeroen
Read the rest of this entry »
Posted in Batch-Files, Console (command prompt window), Development, Power User, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2021/09/08
Not sure why, bit if you want to force install a package, answering yes to all prompts, the chocolaty parameter order needs to be --yes --force instead of --force --yes.
This works:
choco install --yes --force git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf /WindowsTerminal"
This fails:
choco install --force --yes git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf /WindowsTerminal"
–jeroen
Posted in Chocolatey, Development, DevOps, Power User, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2021/08/31
This helped me big time finding failed logon attempts: [WayBack] Event Log Hell (finding user logon & logoff) – Ars Technica OpenForum
Alternatively, you can use the XPath query mechanism included in the Windows 7 event viewer. In the event viewer, select “Filter Current Log…”, choose the XML tab, tick “Edit query manually”, then copy the following to the textbox:
Code:
<QueryList>
<Query Id="0" Path="Security">
<Select Path="Security">*[System[EventID=4624] and EventData[Data[@Name='TargetUserName'] = 'USERNAME']]</Select>
</Query>
</QueryList>
This selects all events from the Security log with EventID 4624 where the EventData contains a Data node with a Name value of TargetUserName that is equal to USERNAME. Remember to replace USERNAME with the name of the user you’re looking for.
If you need to be even more specific, you can use additional XPath querying – have a look at the detail view of an event and select the XML view to see the data that you are querying into.
Thanks user Hamstro!
Notes:
- you need to perform this using
eventvwr.exe running as an elevated process using an Administrative user CUA token.
USERNAME needs to be the name of the user in UPPERCASE.- replacing
TargetUserName with subjectUsername (as suggested by [WayBack] How to Filter Event Logs by Username in Windows 2008 and higher | Windows OS Hub) fails.
- there are more relevant EventID values you might want to filter on (all links have screenshot and XML example of an event):
- blank (empty passwords) can only be used for local logon, so they disable network logon. That can be a useful security strategy.
Related:
–jeroen
Posted in Development, Microsoft Surface on Windows 7, Power User, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Vista, Windows XP, XML/XSD | Leave a Comment »
Posted by jpluimers on 2021/08/23
From Windows 8 on, Microsoft has been pushing more and more stuff to the App UI (sometimes called Immersive User Interface).
By default they are only easily accessible from the search feature from the “Start” button or “Search” pane in the task bar.
This is cumbersome or even problematic when you have to remember the correct terms over many localisations.
In the past you could run this from the command prompt or Windows+R keyboard shortcut “Run” pop-up:
control printers
This does not work however in either of the two:
settings printers
This works from the Windows+R keyboard shortcut “Run” pop-up:
ms-settings:printers
This works from the command prompt:
start ms-settings:printers
The difference is that with control , it will eventually find control.exe on the path, but ms-settings: is the scheme bit of an URI. The start command can handle this, the plain command-line cannot.
What in fact happens is that the URI scheme handler, will have a Windows Service (which runs under NT AUTHORITY\SYSTEM) start "C:\Windows\ImmersiveControlPanel\SystemSettings.exe" -ServerName:microsoft.windows.immersivecontrolpanel under your current user.
List of Settings URIs
Next to a List of applications behind the various control panel links – via “Stop user access to control panel”, below is a list of Settings URIs.
The below list is from [WayBack] The list of Settings pages URIs (ms-settings) in Windows 10 , but misses ms-settings:printers.
Read the rest of this entry »
Posted in Power User, Windows, Windows 10, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2021/08/23
lFor Mac keyboard keys, almost all (except the old solid and open Apple logo’s) have a Unicode code point, see for instance the modifier keys from the [WayBack] List of Mac/Apple keyboard symbols · GitHub (the “Alt” column has a solid Apple logo in the bottom right; on non-Mac systems it will look differently as it is in the Unicode private range: [WayBack] Unicode Character ” (U+F8FF): ‘<Private Use, Last>’):
| Sym |
Key |
Alt |
| ⌃ |
Control |
|
| ⌥ |
Option |
|
| ⇧ |
Shift |
|
| ⌘ |
Command |
|
These are the code points for the “Sym” column:
Keys on many platforms
Read the rest of this entry »
Posted in Microsoft Surface on Windows 7, Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 95, Windows 98, Windows NT, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista, Windows XP | 1 Comment »
Posted by jpluimers on 2021/08/20
Still a cool video. Many shortcuts for various operating systems and machines, including BBC B, Linux, Windows, and MacOS.
–jeroen
Read the rest of this entry »
Posted in *nix, 6502, Apple, BBC Micro B, History, Linux, Mac OS X / OS X / MacOS, Power User, Windows | Leave a Comment »
Posted by jpluimers on 2021/08/19
Wireshark is indispensable when doing network communications development or DevOps.
This is my choco-install-network-tools.bat batch file to install Wireshark and the pcap dependency which nmap provides:
choco install --yes nmap
:: wireshark requires a pcap for capturing; nmap comes with npcap which fulfills this dependency
:: see:
:: - https://chocolatey.org/packages/wireshark
:: - https://chocolatey.org/packages/win10pcap
:: - https://chocolatey.org/packages/WinPcap
:: - https://chocolatey.org/packages/nmap
choco install --yes wireshark
Yes, I know: Windows Subsystem for Linux could have an easier installation, but the above:
See:
–jeroen
Posted in *nix, *nix-tools, Communications Development, Development, Internet protocol suite, nmap, Power User, Software Development, Windows, Windows 10, Windows 8.1, WSL Windows Subsystem for Linux | Leave a Comment »
The Wiert Corner - irregular stream of stuff 