The first war criminal: Peter von Hagenbach

In the 20th century, we had many individuals convicted of war crimes, with some sentenced to death. However, the first recorded trial of this kind was in Europe during the Middle Ages, over 500 years ago, a topic covered in the Nerdologia podcast. Welcome to a new episode of "História Nerdologia." My name is Felipe Figir.


As a history columnist, podcaster, YouTuber, professor, and someone familiar with law, or if you watched Nerdologia's episode on the trial of Peter Von Hagenbach in August 2023, we discussed the history and establishment of the International Criminal Court, currently prominent in the news. It is the first permanent international tribunal for judging individuals for genocide, crimes against humanity, war crimes, and the crime of aggression.


In that video, we commented on how history, unfortunately marked by violence, has many well-documented events since antiquity characterized as massacres or similar terms, especially during wartime. This violence sparked moral and ethical debates condemning episodes of excessive or unnecessary violence and advocating for what should be appropriate or ethical conduct for a warrior.


From the Code of Hammurabi onward, topics like the treatment of prisoners, pillaging of cities, and the recognition of vulnerable groups such as the elderly and children have been present across various cultures throughout history. Although not codified as war crimes as they are today, such acts were prevalent in medieval Europe, integral to its portrayal in films, series, and games—perhaps even excessively compared to reality.


On May 9, 1469, in the region of Padre Calé, the Treaty of San Omer was signed. Duke Sigismund of Habsburg leased some of his lands in southern Alsace to Duke Charles of Burgundy for 50,000 florins, a currency containing gold. Sigismund aimed to form a defensive alliance with Charles to better defend his lands against the French and Swiss, also using the money to acquire land in the Alpine region of Tyrol.


The Duchy of Burgundy enjoyed significant autonomy and rivalled its more powerful neighbors, situated between the Kingdom of France and Germanic lands, sometimes aligning with one and sometimes with another. At various times, it even served as a vassal of France. Charles of Burgundy appointed a knight named Peter Von Hagenbach as his administrator of the leased lands, including a smaller territory in Alsace.


He organized a small army and set out to control the new territories, which turned into a disaster. Initially, local German-speaking people did not welcome a new ruler who spoke French and was a vassal of the Duke of Burgundy. Peter Von Hagenbach proved to be a cruel and violent administrator, increasing taxes, imposing recruitment of farmers, and his soldiers were abusive and violent towards villagers. He ordered roadblocks, tolls, and bribes from Swiss merchants passing through, even though they were not under his authority. Reports of abusive arrests surfaced.


When representatives from the village of Tan requested an audience to complain, they were executed without trial. According to accounts cited by the French historian Baron de Barante, Peter Von Hagenbach was prone to using sexual violence against women as a weapon, authorizing his soldiers to commit such crimes freely and committing such acts himself, including against a nun.


At the same time, Peter Von Hagenbach was trusted by the Duke of Burgundy, serving as an interpreter in official talks between the Duke and Emperor Frederick III of the Holy Roman Empire, discussing a potential marriage between their children. Peter Von Hagenbach's actions against Swiss merchants prompted closer ties between the Swiss Confederation and the Duke of Austria, who leased the lands, arguing that the tax increase violated the lease agreement.


Sigismund of Habsburg sought the return of his lands, but Charles of Burgundy refused. Simultaneously, some cities in the region rebelled against Peter Von Hagenbach. An anti-Burgundy league formed, including the Swiss, the Duke of Austria, and rebellious cities in Alsace, part of a larger war lasting several years—Burgundian Wars.


The league defeated Peter Von Hagenbach's soldiers, who took refuge in the city of Brisach. The city did not want him there, so he repeated his customary actions: massacring part of the inhabitants. His behavior was so tyrannical that his own soldiers mutinied and handed him over to the enemies.


The Duke of Austria decided to convene a jury of 28 representatives from the major cities forming the league to judge the knight. The trial began at 8 a.m. on May 9, 1474, in Saas. Peter Von Hagenbach's defense argued that the court had no authority, that the accusations of sexual violence were actually consensual encounters, and that his actions were merely obeying the orders of his lord, the Duke of Burgundy. According to the records, one of his representatives said that he recognized no judge or master other than the Duke of Burgundy, from whom he received his commission and orders. He had no right to question the orders he was tasked to execute, and it was his duty to obey.


By 4 p.m. that day, the jury found Peter Von Hagenbach guilty of murder, sexual violence, perjury, and pillaging. He symbolically lost his titles and was sentenced to death. Representatives from seven cities vied for the chance to be the executioner. The criminal asked for forgiveness for his crimes and for other even worse things, and was beheaded with an axe, according to Father Erhard Von Oppenweiler. 6,000 people were reportedly present.


Later, Peter Von Hagenbach's history of cruelty took on legendary proportions, with his mummified head displayed, and stories of his ghost haunting a forest. His widow ordered the construction of a chapel in his honor, demolished in the 16th century to build a fortress. In the 20th century, a play was written about him.


With the consolidation of scientific historical methodology, historians began to address other issues, considering that some of Peter Von Hagenbach's crimes may have been exaggerated to ensure his guilt not only for the crimes he committed but also to serve as a scapegoat to exonerate the Duke of Burgundy.


His trial was resurrected as a precedent during preparations for the trials of Nazi criminals in Nuremberg after World War II. Peter Von Hagenbach's defense that he was merely following orders was not accepted in his time, and in 1946, it became the fourth principle of Nuremberg: that a person cannot justify a crime by claiming they were just following orders; this effectively creates two guilty parties and does not absolve those involved.


Today, the Nuremberg principles are a crucial part of international law against war crimes and crimes against humanity. Peter Von Hagenbach is considered the first war criminal in the modern sense of the term. Remember, this video is a condensed version; unfortunately, many fascinating details had to be omitted. Sources and further suggestions are available in the description and comments of Nerdologia.

The Trial of Peter von Hagenbach: A Landmark in War Crimes Justice

**The Trial of Peter von Hagenbach: A Landmark in War Crimes Justice**


In the annals of history, the 15th century marked a significant turning point with the trial of Peter von Hagenbach, a momentous event often overshadowed by more recent legal precedents. Situated amid the tumultuous backdrop of medieval Europe, this trial stands as a seminal episode in the evolution of international law concerning war crimes.


Peter von Hagenbach, a knight appointed by Duke Charles of Burgundy, governed a region in Alsace with an iron fist during the mid-1400s. His administration was marked by brutal taxation, arbitrary imprisonment, and heinous acts of violence, including reported sexual assaults against women. These atrocities sparked local outrage and ultimately led to his trial in May 1474.


Convened in the town of Breisach, the trial was extraordinary for its time. It represented a stark departure from the prevailing norms where such acts of cruelty by feudal lords often went unpunished or were dealt with leniently. The proceedings, conducted by a jury composed of representatives from several cities in the region, charged Hagenbach with murder, rape, perjury, and pillaging.


The defense argued that Hagenbach was merely executing orders from his superior, Duke Charles, and therefore should not be held individually accountable—a defense eerily reminiscent of subsequent claims made during more modern war crime tribunals. However, the jury’s verdict was unequivocal: Hagenbach was found guilty on all counts and sentenced to death by decapitation.


The execution of Peter von Hagenbach resonated far beyond the borders of Alsace. It set a precedent that transcended the era, influencing legal doctrines centuries later, particularly during the Nuremberg Trials after World War II. The principle that individuals cannot evade responsibility for their actions by citing superior orders—a principle underscored in the Nuremberg Principles—was foreshadowed in Hagenbach’s trial.


In contemporary context, Hagenbach serves as a poignant reminder of the enduring struggle to uphold justice in times of conflict. His trial highlighted the evolving moral and ethical standards surrounding warfare, challenging the impunity often enjoyed by those in positions of power.


Today, the legacy of Peter von Hagenbach endures not only as a historical curiosity but as a foundational moment in the development of international humanitarian law. His trial represents a pivotal step towards holding individuals accountable for egregious acts committed during war—a principle that continues to shape legal frameworks aimed at preventing atrocities and protecting human rights worldwide.


As we reflect on this watershed moment in history, we are reminded that justice, though often belated and imperfect, remains a beacon of hope in the face of unchecked brutality.


Enhancing Android Emulator Performance by Disabling Hyper-V and Windows Sandbox

Enhancing Android Emulator Performance by Disabling Hyper-V and Windows Sandbox

As Android emulators become increasingly popular for developers and users alike, ensuring optimal performance is crucial. However, certain virtualization technologies, such as Hyper-V and Windows Sandbox, can conflict with Android emulators, leading to performance issues or even preventing them from starting. This article will guide you through the steps to disable these technologies, improving the performance of your Android emulator.

Understanding the Problem

Hyper-V and Windows Sandbox are powerful tools integrated into Windows 10 and Windows 11 (Pro, Enterprise, and Education editions). Hyper-V allows users to create and manage virtual machines, while Windows Sandbox provides a lightweight, isolated environment to run untrusted applications. However, these technologies can consume system resources and create conflicts with Android emulators like BlueStacks, NoxPlayer, and others.

System Requirements

Before proceeding, ensure your system meets the following requirements:

  • Operating System: Windows 10 Pro, Enterprise, or Education; Windows 11 Pro, Enterprise, or Education.
  • Virtualization: Must be enabled in BIOS/UEFI.
  • Memory: At least 4 GB of RAM (8 GB recommended).
  • Disk Space: At least 1 GB of free disk space.
  • CPU Cores: 2 CPU cores (4 cores with hyperthreading recommended).

Steps to Disable Hyper-V and Windows Sandbox

  1. Open Windows Features

    • Press Windows + R to open the Run dialog.
    • Type optionalfeatures and press Enter to open the Windows Features dialog.
  2. Disable Hyper-V

    • In the Windows Features list, locate Hyper-V.
    • Uncheck the box next to Hyper-V to disable it.
  3. Disable Windows Sandbox

    • Scroll down in the Windows Features list to find Windows Sandbox.
    • Uncheck the box next to Windows Sandbox to disable it.
  4. Apply Changes

    • Click OK to apply the changes. Windows will process the disabling of these features.
    • Once the process is complete, you will be prompted to restart your computer. Click Restart now for the changes to take effect.

Verifying Hyper-V and Windows Sandbox are Disabled

After restarting your computer, follow these steps to confirm that Hyper-V and Windows Sandbox have been disabled correctly:

  1. Check Hyper-V

    • Open PowerShell with administrative privileges (search for "PowerShell" in the Start menu, right-click, and select "Run as administrator").
    • Type the following command and press Enter:
      powershell
      Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
    • The status should indicate that the feature is disabled.
  2. Check Windows Sandbox

    • Similarly, in PowerShell, type:
      powershell
      Get-WindowsOptionalFeature -Online -FeatureName "Containers-DisposableClientVM"
    • The status should indicate that the feature is disabled.

Disabling Virtualization in BIOS/UEFI

If you need to disable virtualization at the BIOS/UEFI level, follow these steps:

  1. Restart and Access BIOS/UEFI

    • Restart your computer and press the appropriate key (such as F2, F10, DEL, or ESC) to enter BIOS/UEFI during startup.
  2. Disable Virtualization

    • In the settings menu, look for an option related to virtualization, such as "Intel VT-x", "AMD-V", or "Virtualization Technology".
    • Disable this option.
    • Save the changes and exit BIOS/UEFI.

Conclusion

By following these steps, you can disable Hyper-V and Windows Sandbox, freeing up system resources and enhancing the performance of Android emulators on your computer. This will allow you to use emulators like BlueStacks, NoxPlayer, and others without compatibility issues related to these virtualization technologies. Whether you're a developer testing applications or a user enjoying mobile games on your PC, ensuring these settings are configured correctly can make a significant difference in your emulator's performance.

How to Disable Hyper-V and Windows Sandbox to Improve Android Emulator Performance

How to Disable Hyper-V and Windows Sandbox to Improve Android Emulator Performance

Certain Android emulators, such as BlueStacks, may experience performance issues or fail to start if virtualization technologies like Hyper-V and Windows Sandbox are enabled on your computer. This guide explains how to disable these technologies to enhance emulator performance.

The Issue

Hyper-V and Windows Sandbox are virtualization technologies provided by Microsoft that can be incompatible with some Android emulators. When enabled, these technologies can consume system resources needed for the emulators to function properly.

Steps to Disable Hyper-V and Windows Sandbox

  1. Open Windows Features

    • Press Windows + R to open the Run dialog.
    • Type optionalfeatures and press Enter to open the Windows Features dialog.
  2. Disable Hyper-V

    • In the Windows Features list, locate Hyper-V.
    • Uncheck the box next to Hyper-V to disable it.
  3. Disable Windows Sandbox

    • Scroll down in the Windows Features list to find Windows Sandbox.
    • Uncheck the box next to Windows Sandbox to disable it.
  4. Apply Changes

    • Click OK to apply the changes. Windows will process the disabling of these features.
    • Once the process is complete, you will be prompted to restart your computer. Click Restart now for the changes to take effect.

Verifying Hyper-V and Windows Sandbox are Disabled

After restarting your computer, follow these steps to confirm that Hyper-V and Windows Sandbox have been disabled correctly:

  1. Check Hyper-V

    • Open PowerShell with administrative privileges (search for "PowerShell" in the Start menu, right-click, and select "Run as administrator").
    • Type the following command and press Enter:
      powershell
      Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
    • The status should indicate that the feature is disabled.
  2. Check Windows Sandbox

    • Similarly, in PowerShell, type:
      powershell
      Get-WindowsOptionalFeature -Online -FeatureName "Containers-DisposableClientVM"
    • The status should indicate that the feature is disabled.

Disabling Virtualization in BIOS/UEFI

If you need to disable virtualization at the BIOS/UEFI level, follow these steps:

  1. Restart and Access BIOS/UEFI

    • Restart your computer and press the appropriate key (such as F2, F10, DEL, or ESC) to enter BIOS/UEFI during startup.
  2. Disable Virtualization

    • In the settings menu, look for an option related to virtualization, such as "Intel VT-x", "AMD-V", or "Virtualization Technology".
    • Disable this option.
    • Save the changes and exit BIOS/UEFI.

Conclusion

By following these steps, you will disable Hyper-V and Windows Sandbox, freeing up system resources and improving the performance of Android emulators on your computer. This will allow you to use emulators like BlueStacks without compatibility issues related to these virtualization technologies.

Exploring Windows Sandbox: A Secure Environment for Testing and Running Untrusted Applications

 Exploring Windows Sandbox: A Secure Environment for Testing and Running Untrusted Applications

In the digital age, the need to run and test applications safely has become paramount. Whether you are a developer testing new software, an IT professional evaluating untrusted applications, or an everyday user concerned about security, Windows Sandbox offers a perfect solution. This feature, integrated into Windows 10 and Windows 11 (Pro, Enterprise, and Education editions), provides a lightweight, isolated environment where you can execute applications without risking your main system. This article explores what Windows Sandbox is, how to enable it, and the benefits it offers.

What is Windows Sandbox?

Windows Sandbox is a virtualized environment that uses Microsoft's hypervisor and hardware virtualization to create a temporary and secure environment. This isolated space allows users to run untrusted software, visit potentially dangerous websites, or open suspicious files without worrying about compromising their main operating system. Once the sandbox is closed, everything within it is discarded, ensuring that no changes or malware persist.

System Requirements

Before enabling Windows Sandbox, ensure that your system meets the following requirements:

  • Operating System: Windows 10 Pro, Enterprise, or Education; Windows 11 Pro, Enterprise, or Education.
  • Virtualization: Must be enabled in BIOS/UEFI.
  • Memory: At least 4 GB of RAM (8 GB recommended).
  • Disk Space: At least 1 GB of free disk space.
  • CPU Cores: 2 CPU cores (4 cores with hyperthreading recommended).

Enabling Windows Sandbox

Follow these steps to enable Windows Sandbox on your system:

  1. Check Virtualization Support in BIOS/UEFI:

    • Restart your computer and enter the BIOS/UEFI settings (commonly accessed by pressing keys like F2, F10, DEL, or ESC during startup).
    • Locate and enable the virtualization option (labeled as "Intel VT-x", "AMD-V", or "Virtualization Technology").
    • Save changes and exit BIOS/UEFI.
  2. Enable Windows Sandbox:

    • Press Windows + R to open the Run dialog.
    • Type optionalfeatures and press Enter to open the Windows Features dialog.
    • Scroll down and check the Windows Sandbox option.
    • Click OK and wait for the necessary components to install. Restart your computer if prompted.

Using Windows Sandbox

Once enabled, Windows Sandbox can be launched and used with ease:

  1. Launch Windows Sandbox:

    • Open the Start menu and search for "Windows Sandbox".
    • Click on Windows Sandbox to start the environment. A new window will open, displaying a clean instance of Windows.
  2. Run Applications:

    • You can now copy files from your host system and paste them into the sandbox environment.
    • Install and run any software within the sandbox without worrying about affecting your main system.
  3. Temporary Environment:

    • Remember that Windows Sandbox is designed for temporary testing. Any changes made, applications installed, or files created will be lost once the sandbox is closed. The environment resets to its original state upon each launch.

Benefits of Windows Sandbox

Security: The primary benefit of Windows Sandbox is security. By running applications in an isolated environment, you protect your main system from potential threats like malware, viruses, or unintended system changes.

Convenience: Windows Sandbox is built into Windows 10 and Windows 11, making it easily accessible without the need for third-party software. It's straightforward to set up and use, requiring minimal configuration.

Efficiency: Unlike traditional virtual machines, Windows Sandbox is lightweight and optimized for quick startup and shutdown. It leverages integrated virtualization capabilities, ensuring efficient resource usage.

Testing Environment: For developers and IT professionals, Windows Sandbox provides an ideal environment for testing new applications, scripts, or configurations without the risk of affecting the host system.

Conclusion

Windows Sandbox is an invaluable tool for anyone who needs to run untrusted applications or test software in a secure, isolated environment. By leveraging the power of hardware virtualization, it provides a convenient, efficient, and secure solution for everyday users and professionals alike. Whether you're a developer, IT professional, or just someone cautious about security, Windows Sandbox can help you maintain the integrity of your main operating system while exploring the digital world with confidence.

Windows Sandbox

Windows Sandbox is a lightweight, virtualized environment integrated into Windows 10 and Windows 11 (Pro, Enterprise, and Education editions) that allows you to run untrusted applications in isolation without risking your main system. Here's how to enable and use Windows Sandbox:

1. Check System Requirements

Before enabling Windows Sandbox, ensure your system meets the following requirements:

  • Operating System: Windows 10 Pro, Enterprise, or Education; Windows 11 Pro, Enterprise, or Education.
  • Virtualization enabled in BIOS/UEFI.
  • At least 4 GB of RAM (8 GB recommended).
  • At least 1 GB of free disk space.
  • 2 CPU cores (4 cores with hyperthreading recommended).

2. Enable Virtualization in BIOS/UEFI

  1. Restart your computer and enter the BIOS/UEFI settings (usually by pressing a key like F2, F10, DEL, or ESC during startup).
  2. Look for an option related to virtualization (it may be called "Intel VT-x", "AMD-V", or "Virtualization Technology") and enable it.
  3. Save the changes and exit the BIOS/UEFI.

3. Enable Windows Sandbox

  1. Press Windows + R to open the Run dialog.
  2. Type optionalfeatures and press Enter to open the Windows Features dialog.
  3. In the Windows Features list, check the Windows Sandbox option.
  4. Click OK. Windows will install the necessary components. Restart your computer if prompted.

4. Using Windows Sandbox

  1. After restarting your computer, open the Start menu and search for "Windows Sandbox".
  2. Click on Windows Sandbox to launch it.
  3. A new window will open, displaying a clean Windows environment. You can now run any application or perform any action within this sandbox without affecting your main system.
  4. When you close the Windows Sandbox, all changes made within it are discarded, and the environment resets to its original state.

Tips for Using Windows Sandbox

  • File Transfer: You can copy files from your host system and paste them into the sandbox environment.
  • Internet Access: Windows Sandbox has internet access, so you can download and test online applications securely.
  • Temporary Environment: Remember that any changes or files created in the Sandbox will be lost when you close it. It's designed for temporary testing and running untrusted applications.

By following these steps, you can enable and use Windows Sandbox to run applications safely and test potentially risky software in an isolated environment.

How to uninstall hyper-v from windows?

 To uninstall Hyper-V from your Windows system, you need to disable it through the Windows Features dialog. Here are the steps to do so:

1. Open Windows Features

  1. Press Windows + R to open the Run dialog.
  2. Type optionalfeatures and press Enter to open the Windows Features dialog.

2. Disable Hyper-V

  1. In the Windows Features dialog, scroll down and find the Hyper-V option.
  2. Uncheck the Hyper-V option along with its sub-options (such as Hyper-V Management Tools and Hyper-V Platform).
  3. Click OK. Windows will process the changes and uninstall Hyper-V. This might take a few minutes.

3. Restart Your Computer

  1. Once the process is complete, you will be prompted to restart your computer. Click Restart now to complete the uninstallation process.

Using PowerShell to Uninstall Hyper-V (Optional)

You can also use PowerShell to uninstall Hyper-V. Here’s how:

  1. Open PowerShell with administrative privileges. You can do this by searching for "PowerShell" in the Start menu, right-clicking on it, and selecting Run as administrator.
  2. In the PowerShell window, type the following command and press Enter:
    powershell
    Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
  3. Wait for the command to complete, then restart your computer if prompted.

By following these steps, you can successfully uninstall Hyper-V from your Windows system.

Mirra Andreeva

  Mirra Andreeva Mirra Andreeva is making a big splash in women's tennis. She recently amazed fans at a major tournament. Her skills sh...