Skip to content

Instantly share code, notes, and snippets.

View Ridys's full-sized avatar
🧿

Dmitry Ridys

🧿
  • Krasnoyarsk
  • 08:28 (UTC +07:00)
View GitHub Profile
@xbb
xbb / windows-firewall-cleanup.ps1
Last active September 9, 2024 19:44
Removes Windows Firewall program rules pointing to non-existing paths
# Usage: windows-firewall-cleanup.ps1 [-y]
# use -y parameter to actually remove the rules
param(
[switch]$y = $false
)
Get-NetFirewallApplicationFilter | ForEach-Object {
$program = $_.Program
if ([System.IO.Path]::IsPathRooted($program)) {
if (!(Test-Path -Path "$program" -PathType Leaf)) {
@bahadiraraz
bahadiraraz / Git_Commit_Freeze_Solution.md
Last active May 8, 2025 17:41
Git Commit Freeze Due to GPG Lock Issues (Solution)

Git Commit Freeze Due to GPG Lock Issues

If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.

Solution Steps

1. Check for GPG Lock Messages

Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.