Windows 10 ping through firewall- GUI, PowerShell netsh command

enable ping requests on Windows.
CMD als Admin:
netsh advfirewall firewall add rule name=“ICMP Allow incoming V4 echo request“ protocol=icmpv4:8,any dir=in action=allow

There are a couple of ways to open the blocked ping request in Windows 10 by configuring a firewall. It can be using the graphical user interface or via the command line PowerShell or centrally via group policies. By default, Windows 10 not allows other computers in the network to ping due to security concerns. After all, the service is often misused for attacks, preferably for denial-of-service attacks, thus Microsoft decided to turn it off, out of the box.

Well, still many times we need the pining facility to solve the network connectivity problems and for that newbies usually turn off the Firewall completely. However, we can manually allow Windows 10 Ping in its firewall, whereas those who concern about security risks they can mitigate it by activating the predefined firewall rule only for the domain profile or by restricting permissible requests to certain IP addresses.

Allow Windows 10 ping through Firewall GUI

One of the easiest ways to allow ping is by activating the pre-configured firewall in Windows via a graphical user interface with the help of the Advanced Security option. However, you should have admin access to enable or disable firewall rules. Here are the steps to follow:

  1. Go to Windows 10 or 7 Search box.
  2. Type- Windows Defender firewall, as its icon appears, click to open it.
  3. From the left side panel select “Advanced Settings“.
  4. On Windows Defender Firewall with Advanced Security select Inbound Rule from the left side panel.
  5. Now, in the Inbound Rules area search for “File and Printer Sharing (Echo Request ICMPv4-In). This rule exists in versions for the profile domain as well as for public and private. They can be activated for a specific profile or several profiles as required. In this option, the private profile allows pining through IP V4 address”.
  6. Once you find this predefined rule, right-click on it and select “Enable rule“.
  7. After that Windows 10 system could be pinged from a remote or local PC.
  8. In the same way, if you are interested in pinging Windows through Domain or IPv6, then select Echo Request ICMPv6 for IP version 6 whereas the same option with Domain Profile will the pinging through the domain name.

Open WIndows 10 firewall advance settings Enable WIndows 10 ping through firewall advance rule

Furthermore, if you want to secure pining by restricting it to some particular IP address then after enabling the rule, again right-click on the same and select Properties.

Open Firewall Rule properties min

In the Properties dialog select the Scope Tab and to restrict all clients from sending ping requests, click on the Add button and mentioned the Remote IP Address of the only those machines that you want to allow to ping your Windows 10 PC. If there are several NICs on the computer, it is also possible to use local IP addresses to specify those to which requests are allowed.

Secure Ping by adding remote ip address

Allow Windows ping with PowerShell or Command-line Prompt

Those who don’t want to use the GUI method because of the multiple steps involved to allow Ping on Windows can go for command-line one. In which, we just need to run Powershell or Command prompt with Administrative right and after that copy-paste the command given here.

  • Click in Windows 10 or 7 search box.
  • Type- Powershell or Command prompt
  • Then as per your selection of command-line tool, run it as administrator.
  • After that simply run the below netsh command to enable ping requests on Windows.

netsh advfirewall firewall add rule name=“ICMP Allow incoming V4 echo request“ protocol=icmpv4:8,any dir=in action=allow
In the same way, if you want to disable Windows 10 Ping then use this command:
netsh advfirewall firewall add rule name=“ICMP Allow incoming V4 echo request“ protocol=icmpv4:8,any dir=in action=block
Command to enable or disable windows 10 ping


Content retrieved from:

Das Hinzufügen des ARP-Eintrags ist fehlgeschlagen: Der Zugriff wird verweigert: arp -s geht nimmer

Stattdessen wir jetzt netsh verwendet:

netsh interface ipv4 add neighbors „Name der LAN-Verbindung“ [IP] [MAC]

für Copy & Paste:
netsh interface ipv4 add neighbors LAN-Verbindung 00-11-32-B7-00-E9
netsh interface ipv4 add neighbors Local Area Connection 00-24-01-d2-3a-bd
netsh interface ipv4 add neighbors Ethernet 00-11-32-B7-00-E9

Netzwerkkarten anzeigen:
netsh interface show interface

How to restore Registry from its secret backup on Windows 10

On Windows 10, it is never a good idea to modify the Registry because the database contains low-level settings necessary for the system and certain apps to operate correctly, and the slightest mistake can prevent the device from booting again.

If you recently made system setting changes or installed a buggy update that caused the computer to stop working, you can still recover Windows 10 using the secret Registry backup.

However, there is one caveat, since the operating system no longer creates these backups automatically, you have to re-enable it manually before you can use it.

In this guide, you will learn the steps to restore the previous version of the Registry manually from its automated backup on Windows 10.

Important: Remember that modifying system files can further damage the installation if it is not done correctly. It is assumed that you know what you’re doing and that you have previously created a full backup of your computer. Use these steps at your own risk.

Restore Registry manually on Windows 10

To manually restore the Registry on Windows 10, use these steps:

    1. Start computer with the Advanced startup options.
    2. Click on Troubleshoot.
    3. Click on Advanced options.
    4. Click on Command Prompt.

When your device starts in Command Prompt, it will start on X:WindowsSystem32. Now you need to move to the drive letter where Windows is installed. While the operating system is installed on the C: drive, when you boot your computer on recovery mode, this drive letter could change to something else. However, in most cases, the drive letter is D:. Type the following command to enter into the correct drive where Windows 10 is installed and press Enter:

  1. d:
  2. Type the following command to verify you are in the correct drive and press Enter:
    Command Prompt in Advanced startupCommand Prompt in Advanced startup
    If you see the Windows folder, you are in the correct drive letter. If not, return to step No. 5 and try another letter.
  3. Type the following command to enter into the System32 folder and press Enter:
    cd d:windowssystem32
    Change D in the command with the correct drive letter for your scenario.
    Windows 10 Config folderWindows 10 Config folder
  4. Type the following command to create a folder to temporary backup of files on the config folder, which also happens to store a copy of the Registry, and press Enter:
    mkdir configBak
  5. Type the following command to create a temporary backup of the files in the config folder, and press Enter:
    copy config configBak
    Making a backup copy of the Registry on Windows 10Making a backup copy of the Registry on Windows 10
  6. Type the following command to move inside the RegBack, which contains a backup of the Registry, and press Enter:
    cd configRegBack
  7. Type the following command to verify the content of the RegBack folder and press Enter:
    RegBack folder contentRegBack folder content


    Warning: After running the dir command, the files’ size (SYSTEM, SOFTWARE, SAM, SECURITY, DEFAULT) should be similar to the ones you see in the screenshot. If any of the files shows 0, do NOT continue as you won’t be able to repair your Windows 10 installation, and your device may stop booting.
  8. Type the following command to copy the files from the RegBack folder to the config folder and press Enter and the Y key on every question to confirm:
    copy * ..*
    Restoring Registry from its backupRestoring Registry from its backup on Windows 10
  9. Click the Close (X) button from the top-right.

Once you complete the steps, the computer will reboot, and Windows 10 should start correctly.

We are focusing this guide on Windows 10, but the concept also should work on Windows 8.1 and Windows 7.

How to enable automatic Registry backup on Windows 10

Windows 10 adds option to enable automatic backups for the Registry. In previous releases, Windows 10 used to save a copy of the entire Registry inside the RegBack system folder automatically, but to help reduce storage space, since the April 2018 Update, the operating system has removed the functionality.

As a result, users wanting to recover the system after a corrupt registry hive, quickly found that inside the C:WindowsSystem32configRegBack folder, each registry hive was 0kb in size.

If you want the legacy behavior back, Windows 10 includes a registry key to re-enable automatic backups for the entire Registry every time your computer restarts successfully.

In this guide, you’ll learn the steps to allow Windows 10 to create backups of the Registry every time your computer starts.

  • Enable automatic backup for Registry
  • Create manual backup of Registry

Enable automatic backup for Registry

To enable automatic backups of the Registry, use these steps:

Warning: Modifying system files can further damage your Windows installation if it’s not done correctly. It’s assumed that you know what you’re doing and that you have previously created a full backup of your computer. Proceed with caution and use this as the last course of action.
    1. Open Start on Windows 10.
    2. Search for regedit and click the top result to open the Registry.
    3. Browse the following path:
      HKLMSystemCurrentControlSetControlSession ManagerConfiguration Manager
    4. Right-click the Configuration Manager (folder) key and select New submenu, and click the DWORD (32-bit) Value option.
      Configuration Manager registryConfiguration Manager registry
  1. Name the key EnablePeriodicBackup and press Enter.
  2. Double-click the newly created DWORD and set the value from 0 to 1.
    Configuring EnablePeriodicBackup for automatic Registry backups on Windows 10Configuring EnablePeriodicBackup for automatic Registry backups on Windows 10
  3. Click the OK button.
  4. Restart your computer.

Once you complete the steps, Windows 10 will create a backup of the entire Registry inside the RegBack folder, and it’ll create a “RegIdleBackup” task in the Task Scheduler to manage future backups.

If the time comes when you computer can’t start because of corruption in one of the registry hives, then you can use this guide to restore the registry from backup to allow Windows 10 to start correctly.

Create manual backup of Registry

To run the Windows 10 Registry backup manually, use these steps:

  1. Open Start.
  2. Search for Task Scheduler and click top result to open the console.
  3. Browse the following path:
    Task Scheduler Library > Microsoft > Windows > Registry.
  4. Right-click the RegIdleBackup task and select the Run option.
    Running RegIdleBackup task on Windows 10Running RegIdleBackup task on Windows 10

After you complete the steps, the task will run to create a backup of the entire Registry using five files (Default, Sam, Security, Software, and System) overwriting the previous backup in the RegBack folder.

Dateisortierung nach Sonderzeichen

_ Unterstrich
۞ Stern mit Loch ?

a A-Z
z Lower case Z

ι Greek letter
Ι Greek letter, capital version of above character, not an „I“)
α alpha U+03B1 Alt 224
Γ gamma U+0393 Alt 226
δ delta U+03B4 Alt 235
ε epsilon U+03B5 Alt 238
Θ theta U+0398 Alt 233
π pi U+03C0 Alt 227
Σ sigma upper U+03A3 Alt 228
σ sigma lower U+03C3 Alt 229
τ tau U+03C4 Alt 231
Φ phi upper U+03A6 Alt 232
φ phi lower U+03C6 Alt 237
Ω omega U+03A9 Alt 234
一 Japanese Character? (Thanks, Jam)
口 Japanese character? (Thanks, Jam)
末 Japanese character „End“ (Thanks, Jam)
 (a private use character) (Thanks, Peter O.)

Und man kann auch tatsächlich (fast) alle Sonder-Zeichen außer \ / : * ? “ < > | verwenden.

So, jetzt zum wirklich Wichtigen, die Buchstaben nach „Z“.

Zuerst habe ich das Ohm-Zeichen Ω gefunden (das griechische Omega).

Dann herausgefunden das alle griechischen Buchstaben α β γ δ ε … φ χ ψ ω nach den deutschen Buchstaben kommen
und danach die kyrillischen Buchstaben Ё Ђ Ѓ Є … Ҳ Ҹ Һ Ә Ө .

Vor der Null kommen anscheinend nur Satzzeichen und Symbole,
den Anfang macht das ! dann # $ % & irgendwann kommt das @ ,
Plus, Minus und Underline sind auch vor Null.

Ein paar schöne Symbole vor Null sind Pik, Kreuz, Herz und Karo ♠ ♣ ♥ ♦ ,
sowie ■ ▲ ▼ ► ◄ wobei diese komischer Weise im Explorer unterschiedlich groß dargestellt werden.

Und noch ein ganz Spezielles, weil ja * nicht erlaubt ist, kann man alternativ den arabischen Stern ٭ verwenden,
der aber hier im Textfenster etwas Probleme macht, ist wohl ein Steuerzeichen für irgend was,
er schaut hier im Text auch nicht so schön aus wie im Explorer.

Die Sortierreihenfolge nach unterschiedlichen Sonderzeichen, speziell Minus, bleibt wohl für ewig ein Rätsel,
hier ein Beispiel:


Unicode Chart:

Make Device Manager show Non present devices in Windows

  1. CMD als Admin
  2. set devmgr_show_nonpresent_devices=1
  3. start devmgmt.msc
  4. Device Manager Ausgeblendete Geräte anzeigen


Der Geräte-Manager zeigt nur Plug&Play-Geräte, -Treiber und -Drucker an, wenn Sie im Menü Ansicht auf Ausgeblendete Geräte anzeigen klicken. Nicht an den Computer angeschlossene Geräte, die Sie installieren (z. B. USB-Geräte oder „verwaiste“ Geräte), werden im Geräte-Manager nicht angezeigt, auch dann nicht, wenn Sie auf Ausgeblendete Geräte anzeigen klicken.


Gehen Sie folgendermaßen vor, um dieses Verhalten zu umgehen und Geräte mit der Option Ausgeblendete Geräte anzeigen anzuzeigen:

  1. Klicken Sie auf Start, zeigen Sie auf Alle Programme, zeigen Sie auf Zubehör, und klicken Sie anschließend auf Eingabeaufforderung.
  2. Geben Sie an der Eingabeaufforderung den folgenden Befehl ein, und drücken Sie anschließend die EINGABETASTE:set devmgr_show_nonpresent_devices=1
  3. Geben Sie an der Eingabeauforderung den folgenden Befehl ein, und drücken Sie dann die EINGABETASTE:start devmgmt.msc
  4. Führen Sie eine Problembehandlung für die Geräte und Treiber im Geräte-Manager durch.

    HINWEIS: Klicken Sie im Menü Ansicht im Geräte-Manager auf Ausgeblendete Geräte anzeigen, um Geräte sehen zu können, die nicht an den Computer angeschlossen sind.
  5. Wenn Sie die Problembehandlung abgeschlossen haben, schließen Sie den Geräte-Manager.
  6. Geben Sie an der Eingabeaufforderung exit ein.

    Wenn Sie das Eingabeaufforderungsfenster schließen, deaktiviert Windows die Variable devmgr_show_nonpresent_devices=1 zurück, die Sie in Schritt 2 erstellt haben, und verhindert, dass verwaiste Geräte bei Anklicken von Ausgeblendete Geräte anzeigen angezeigt werden.

[Fix] Remote Desktop DPI scaling issues

Do you have a computer with High-DPI screen? A very high resolution display? And is everything too small to see within your Remote Desktop Connection, try this solution…


This issue is caused by lack of not being DPI scaling aware of the Remote Desktop Client. If you open a Remote Desktop connection to a server or other computer the native resolution of the computer is used instead of the scaling to 1920×1080, so you’ll get very small icons etc.

Some other blogs mention to fix the issue with using Remote Desktop Connection Manager 2.7 or using RD Tabs.

Another solution where you don’t need extra tools or programs is to make a manifest file, see the steps below.

First tell Windows to look for a manifest file for an application by default. This can be done by setting a registry entry.

Open regedit and navigate to the registry key:
Right-click, select NEW -> DWORD (32 bit) Value
Type PreferExternalManifest and then press ENTER.
Right-click PreferExternalManifest, and then click Modify.
Enter Value Data 1 and select Decimal.
Click OK. Exit Registry Editor.

Next step is to make the manifest file, mstsc.exe.manifest. Copy the contents below and put it in Notepad or similar tool and save it to a file as %SystemRoot%System32mstsc.exe.manifest. Download of the file is also available, here. Important is that you save the file in the same directory as the Remote Desktop Client executable (mstsc.exe).
<?xml version=“1.0″ encoding=“UTF-8″ standalone=“yes“?> <assembly xmlns=“urn:schemas-microsoft-com:asm.v1″ manifestVersion=“1.0″ xmlns:asmv3=“urn:schemas-microsoft-com:asm.v3″> <dependency> <dependentAssembly> <assemblyIdentity type=“win32″ name=“Microsoft.Windows.Common-Controls“ version=“″ processorArchitecture=“*“ publicKeyToken=“6595b64144ccf1df“ language=“*“> </assemblyIdentity> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type=“win32″ name=“Microsoft.VC90.CRT“ version=“9.0.21022.8″ processorArchitecture=“amd64″ publicKeyToken=“1fc8b3b9a1e18e3b“> </assemblyIdentity> </dependentAssembly> </dependency> <trustInfo xmlns=“urn:schemas-microsoft-com:asm.v3″> <security> <requestedPrivileges> <requestedExecutionLevel level=“asInvoker“ uiAccess=“false“/> </requestedPrivileges> </security> </trustInfo> <asmv3:application> <asmv3:windowsSettings xmlns=““> <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings=““>false</ms_windowsSettings:dpiAware> </asmv3:windowsSettings> </asmv3:application> </assembly>
Note that you can use the manifest for other applications also that aren’t scaling aware.



Siehe auch


Content retrieved from:


The MaxShadowCopies registry value specifies the maximum number of client-accessible shadow copies that can be stored on each volume of the computer. A client-accessible shadow copy is a shadow copy that is created using the VSS_CTX_CLIENT_ACCESSIBLE value of the _VSS_SNAPSHOT_CONTEXT enumeration. Client-accessible shadow copies are used by Shadow Copies for Shared Folders. For more information about shadow copies, see the VSS documentation.

If the MaxShadowCopies registry value does not exist, the backup application can create it under the following registry key:


Create a value with the name MaxShadowCopies and type DWORD. The default data for this value is 64. The minimum is 1. The maximum is 512.


For other types of shadow copies, there is no registry value that corresponds to MaxShadowCopies. The maximum number of shadow copies is 512 per volume.

Note  The MaxShadowCopies setting is supported on Windows Server 2003 or later.

Windows Server 2003: On cluster servers, MaxShadowCopies registry value’s data may need to be set to a lower number. For more information, see „When you use the Volume Shadow Copy Service on Windows Server 2003-based computers that run many I/O operations, disk volumes take longer to go online“ in the Help and Support Knowledge Base at

Betrieben von WordPress | Theme: Baskerville 2 von Anders Noren.

Nach oben ↑