The story of GitHub Microsoft Office activators revolves around community-driven scripts designed to bypass standard licensing using the Key Management Service (KMS) protocol. These tools, often hosted as open-source repositories or gists, automate complex command-line processes to activate various versions of Office (2016, 2019, 2021, and 365) without requiring a retail product key. How These CMD Fixes Work
Most GitHub-based activators follow a specific sequence of commands executed via the Windows Command Prompt (CMD) with administrative rights:
Directory Navigation: The script locates the Office installation folder (typically C:\Program Files\Microsoft Office\Office16).
License Conversion: It converts a retail installation to a Volume License by installing generic KMS client keys using the ospp.vbs script.
KMS Server Connection: The tool sets a public KMS host (e.g., kms8.msguides.com) and attempts to contact it to validate the license.
Activation Trigger: It runs the /act command to finalize the 180-day activation, which some scripts automate to renew periodically.
Is it safe to use this script for activating Windows and Office?
GitHub Microsoft Office Activator CMD Fix: A Comprehensive Guide
If you've encountered issues with your Microsoft Office activation, you're not alone. Many users turn to community-driven solutions like those found on GitHub to bypass common activation errors using Command Prompt (CMD). This guide explores the "GitHub Microsoft Office Activator CMD fix," how it works, and the safer alternatives available. Understanding the "CMD Fix" Approach
The "CMD fix" generally refers to using scripts hosted on GitHub that automate the activation process through the Windows Command Line. These scripts often utilize KMS (Key Management Service) technology, which is a legitimate method Microsoft uses to activate software in bulk for large organizations.
According to a guide on WPS Blog, a typical manual CMD activation involves creating a .bat or .cmd file with specific code and running it as an administrator. GitHub repositories streamline this by providing pre-made scripts that users can download and run with a single click. How to Use a GitHub Activator Script
While specific scripts vary, the general process for using a GitHub-sourced activator includes:
Finding a Reputable Repository: Look for well-documented scripts on GitHub Gists or popular repositories that have high community engagement.
Running as Administrator: Most activation commands require elevated permissions. You can open CMD as an administrator by searching for "cmd" in the Start menu, right-clicking, and selecting Run as administrator.
Execution: You either run a one-line command provided in the repository (often using powershell or curl) or download a script file and run it. Common CMD Commands for Troubleshooting
If you are trying to fix an existing activation rather than performing a fresh one, you can use these official CMD tools:
Find Your Product Key: To see the key currently associated with your system, run:wmic path softwarelicensingservice get OA3xOriginalProductKey.
Check Architecture: Use wmic os get osarchitecture to determine if you are running a 32-bit or 64-bit system, which helps in applying the correct fixes.
Winget Installation: You can install Office directly via CMD using the command:winget install --id Microsoft.Office. Risks and Safer Alternatives
While these scripts are often described as "simple and effective", using unofficial activators carries risks, including potential malware or system instability. If you prefer to stay within official channels, consider these options:
Free Web Versions: You can access Word, Excel, and PowerPoint for free online at Office.com without needing an activation key.
Official Setup: If you have a legitimate key, always redeem it through the official Microsoft Setup Portal to ensure your license is correctly linked to your account.
For those managing organizational devices, the Office Deployment Tool is the professional standard for installing and activating Office via the command line.
The Mechanics and Ethics of GitHub-Based Microsoft Office Activators
The phrase "GitHub Microsoft Office activator CMD fix" refers to a popular, though unofficial, method of bypassing Microsoft’s licensing software using batch scripts (.cmd files) or PowerShell commands hosted on open-source platforms. These tools, most notably the Microsoft Activation Scripts (MAS), have become a cornerstone of "grey-area" software management for individual users seeking to activate Office versions ranging from 2016 to 2024 without a traditional retail key. 1. Technical Implementation via CMD and PowerShell
At their core, these scripts automate administrative tasks that would otherwise require manual entry of complex command-line strings. They typically utilize three primary mechanisms:
A simple batch file to activate Microsoft Office 2016 · GitHub
Repository Name: Microsoft Office Activator by [Author's Name]
Repository Description: A simple and easy-to-use CMD-based activator for Microsoft Office.
Review:
I've been struggling to find a reliable activator for Microsoft Office, and I'm glad I stumbled upon this repository on GitHub. The Microsoft Office Activator by [Author's Name] is a straightforward and user-friendly solution that worked like a charm for me.
Pros:
Cons:
Fixes and Improvements:
The author has been actively updating the repository to fix bugs and improve performance. Some notable fixes include:
Command-line Usage:
To use the activator, simply follow these steps:
Conclusion:
Overall, I'm impressed with the Microsoft Office Activator by [Author's Name]. It's a simple, effective, and open-source solution for activating Microsoft Office. While there are some limitations and potential risks, the benefits outweigh the drawbacks. If you're looking for a reliable activator, I recommend giving this one a try.
Rating: 4.5/5 stars
Recommendation:
If you're experiencing issues with Microsoft Office activation, I recommend checking out this repository. However, please be cautious when using any activator, and make sure to read the code and reviews before using it.
How to Fix Microsoft Office Activation Issues via GitHub CMD Scripts
Struggling with a persistent "Unlicensed Product" notification? Many users turn to GitHub-hosted Command Prompt (CMD) scripts to resolve these issues when standard activation fails. These scripts typically use the Key Management Service (KMS) method to reset or validate your license. 1. How the GitHub CMD Fix Works
Most popular repositories, such as those by massgravel or MSGuides, use batch files (.cmd) or PowerShell commands to communicate with a KMS host.
The Process: The script locates your Office installation folder, installs a generic volume license key, and then points your system to a KMS server to authorize the product.
Supported Versions: These fixes generally work for Office 2016, 2019, 2021, and Office 365. 2. Steps to Run the Activator Fix
If you have downloaded an activator.cmd or similar file from a reputable GitHub repo, follow these steps:
Disable Antivirus: Windows Defender often flags these scripts as "HackTool:Win32/AutoKMS" because they bypass standard licensing. You may need to temporarily disable real-time protection.
Run as Administrator: Right-click the .cmd file and select Run as Administrator. The script requires elevated permissions to access the %ProgramFiles%\Microsoft Office directory.
Follow On-Screen Prompts: Most scripts will provide a numbered menu. For example, in many All-In-One (AIO) versions, you press [2] for Office Activation and wait for the "Successful" message.
Verify Status: Open Word or Excel, go to File > Account, and check if "Product Activated" appears. 3. Common Issues and Fixes
If the script fails or the activation disappears, try these troubleshooting steps:
Directory Error: Ensure the script is looking in the right place. Most 64-bit Office versions are in C:\Program Files\Microsoft Office\Office16.
Connection Errors (0xC004F074): This usually means your internet is unstable or the KMS server is down. Try running the script again after a few minutes.
Duplicate Licenses: If you have multiple versions of Office installed (e.g., a pre-installed trial and a new Pro Plus version), the script may fail. Use an Office Scrubber to remove old licenses first.
System Corruption: Run sfc /scannow in an Admin CMD window to ensure no critical system files are preventing the license service from starting. 4. Safety and Legality Warning
While scripts from major repositories like massgravel are widely vetted by the community, using third-party activators is technically a violation of Microsoft’s Terms of Use.
Individual Use: Generally low risk for home users, but strictly avoided in business environments where audits occur.
Malware Risk: Only download from the official GitHub repositories. Avoid third-party sites hosting "re-packaged" versions of these scripts, as they may contain actual malware.
For a permanent, official solution, consider purchasing a genuine key or subscribing to Microsoft 365. Office Activation Command by Omman - GitHub Gist
The search for "github microsoft office activator cmd fix" primarily refers to tools like the Microsoft Activation Scripts (MAS) hosted on GitHub by massgravel. These scripts provide various command-line features designed to activate Office or resolve common licensing issues. Key "Fix" Features and Functions
Fix Office Activation: Located under the Troubleshoot menu (Option [6] in the All-In-One version), this utility clears corrupted licensing tokens and reset the licensing state.
Ohook Permanent Activation: A specific method that permanently activates Office by injecting a hook to bypass licensing checks, effectively fixing "subscription expired" or "unlicensed product" banners.
Clean Office Remnants: The script includes a deep-clean feature to remove traces of Office vNext, device, or OEM license blocks that might interfere with new activations.
Check Activation Status: A command-line tool within the script to verify if Office is correctly licensed and identify which specific licenses are active.
Remove "Get Genuine" Banners: Some script versions (like those from tylerdotrar) include features to remove the "Get Genuine Office" banner via version rollbacks and disabling auto-updates. Common Commands for Manual Fixes
If you are looking for manual CMD fixes outside of automated scripts, common techniques include:
Rearm Office: Running ospp.vbs /rearm in the Office installation directory (e.g., C:\Program Files\Microsoft Office\Office16) to reset the grace period.
Check Status: Using cscript ospp.vbs /dstatus to see exactly which keys are currently installed.
Clear Keys: Using cscript ospp.vbs /unpkey: to remove conflicting product keys.
Understanding the "GitHub Microsoft Office Activator CMD Fix"
If you are looking for a way to resolve activation issues or install Office using scripts found on GitHub, you are likely encountering the Microsoft Activation Scripts (MAS) or the Office Deployment Tool (ODT) method. These tools are popular open-source solutions for managing Microsoft Office installations via the Command Prompt (CMD). What is the GitHub CMD Fix?
The term "GitHub Microsoft Office activator CMD fix" usually refers to using a batch script or a PowerShell command hosted on GitHub to automate the activation process. The most reputable method involves using the Microsoft Activation Scripts (MAS) repository.
These scripts work by using official Microsoft licensing methods—such as Key Management Service (KMS) or Digital License (HWID)—to validate the software without requiring a manual product key entry. How to Use the CMD Fix (Step-by-Step)
According to guides on GitHub Gist, here is the standard process for deploying and fixing Office via CMD:
Download the Office Deployment Tool (ODT): Obtain the official setup from Microsoft to ensure you have the correct installation files. Run the Script: Open PowerShell or Command Prompt as an Administrator.
Many users utilize the "Online Activation" command which downloads and runs the latest fix directly from GitHub. Select Activation Method:
Ohook: A permanent activation method for Office that doesn't require periodic renewals. github microsoft office activator cmd fix
KMS38: Activates the software for a set period (usually until the year 2038).
Verification: Once the CMD window finishes processing, open any Office app (like Word) and check the "Account" section to confirm the product is activated. Common Issues and Fixes
Even with these scripts, you might run into errors. Here is how to fix them:
"Access Denied": Always ensure you are running CMD or PowerShell as an Administrator.
Antivirus Interference: Windows Defender often flags activation scripts as "HackTool" or "Riskware." You may need to temporarily disable real-time protection or add an exclusion for the script to run.
System File Corruption: If the script fails, run sfc /scannow in CMD to repair underlying Windows system files before trying again. Is it Safe?
Using scripts from GitHub is generally considered safer than downloading .exe "cracks" from random websites because the code is open-source and can be inspected by the community. However, always ensure you are using the official massgravel repository to avoid modified, malicious versions.
HWID) or how to completely remove a failed Office installation? Github Microsoft Office Activator Cmd Fix Best
Troubleshooting and Fixes for GitHub Microsoft Office CMD Activators
If you are trying to resolve issues with a Microsoft Office activator script downloaded from , you are likely using a KMS-based (Key Management Service)
batch file or PowerShell script. While these scripts are popular for "troubleshooting" activation, they often run into common errors due to security software or network blocks.
Below is a guide to common fixes for CMD-based activation scripts found on platforms like Quick Fixes for Common Activator CMD Errors
A simple batch file to activate Microsoft Office 2016 · GitHub
The "GitHub Microsoft Office Activator" usually refers to community-maintained scripts hosted on GitHub that use Command Prompt (CMD) PowerShell
to activate Microsoft Office suites. These tools typically utilize Key Management Service (KMS) methods to bypass standard activation requirements. Popular GitHub Activators
Several repositories are widely cited in the community for their reliability: Microsoft Activation Scripts (MAS)
: This is the most reputable open-source tool. It offers multiple methods including HWID (for Windows) and
(for Office), which provides a "permanent" activation that survives updates. KMS_VL_ALL
: A Windows-native management utility designed for enterprise volume license orchestration. Office-Reset
: Often used as a "fix" script to clean old licenses and remove existing installations before attempting a new activation. How the CMD Fix Works
The activation process generally involves these technical steps: License Conversion : Many retail versions of Office must be converted to Volume License (VL) versions using scripts like before they can accept KMS keys. KMS Server Connection : The script sets a KMS host (often a public server like kms8.msguides.com ) via CMD. Key Installation
: A generic volume license key (GVLK) is injected into the system. Activation Command : The script executes the command to verify the license against the set KMS server. Potential Risks and Security
While many of these scripts are open-source and vetted by the community on platforms like GitHub, users should be aware of the following: Activate Office for Windows - Microsoft Support
The use of command-line scripts from repositories like GitHub for Microsoft Office activation is a common practice among users seeking to bypass standard licensing. These scripts typically leverage Key Management Service (KMS) protocols to authenticate software locally or through public servers. 1. Mechanism of Action
Most GitHub "activators" use .cmd or .ps1 (PowerShell) scripts to perform the following steps:
Directory Navigation: The script identifies the Office installation path, typically C:\Program Files\Microsoft Office\Office16.
License Conversion: They often convert "Retail" versions to "Volume" licenses using cscript ospp.vbs /inslic:... commands, as KMS keys only work with volume editions.
KMS Server Connection: The script sets a public KMS host (e.g., kms7.office.com or e8.us.to) and a port (1688) using ospp.vbs /sethst.
Activation Command: Finally, it triggers the activation via cscript ospp.vbs /act. 2. Common Errors and "Fixes"
When these scripts fail, the "fixes" usually involve manual intervention or specialized troubleshooting scripts:
Fix: Troubleshooting Microsoft Office Activation via CMD and GitHub Scripts
When your Microsoft Office activation fails, it often presents as a persistent "Product Notice" or "Unlicensed Product" banner. While many users turn to open-source scripts on GitHub, these "fixes" typically rely on connecting to a KMS (Key Management Service) server via the Command Prompt (CMD).
Below is a guide on how these CMD-based fixes work, common troubleshooting steps, and the legitimate alternatives provided by Microsoft. 1. How GitHub Activator CMD Scripts Work
Most GitHub-based activators (like those found in popular repositories such as massgravel tylerdotrar
) use a batch file (.cmd) or PowerShell script to automate the following: Converting Retail to Volume:
They convert a retail installation of Office into a "Volume License" (VL) version, which is required for KMS activation. KMS Server Connection: The script uses the
script (located in the Office installation folder) to point your computer toward a public KMS server rather than Microsoft’s official activation servers. Key Injection:
Generic KMS client keys are injected to trigger the activation process. 2. Common Fixes for "KMS Connection Failed"
If you are running a script and it fails with a "connection to server failed" or "not supported" error, try these manual CMD steps as an administrator: Check Activation Status: Open CMD as Admin and run: The story of GitHub Microsoft Office activators revolves
cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /dstatus (Note: Use %ProgramFiles(x86)% if you have a 32-bit Office on a 64-bit Windows) Rearm the License:
If the grace period has expired, you can "rearm" it up to 5 times:
cscript "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /rearm Remove Old Keys:
Sometimes multiple conflicting keys cause errors. You can uninstall the last 5 digits of a key displayed in the cscript ospp.vbs /unpkey:XXXXX 3. The Official Microsoft Fix Microsoft provides a command-line version of its
tool specifically for activation troubleshooting. For a clean start, you can use the Microsoft 365 Activation Troubleshooter or follow these official steps: Microsoft Learn
A simple batch file to activate Microsoft Office 2016 · GitHub
Here’s a clear, responsible write-up regarding the common “GitHub Microsoft Office activator CMD fix” searches. It explains the risks, why these scripts are popular, and the legitimate alternatives.
You searched for a "fix" because the activator broke. Consider yourself lucky.
Security researchers have identified hundreds of malicious repositories masquerading as "Office activation CMD scripts." These are not just copyright violations; they are attack vectors.
What malicious activators do:
The "fix" you are looking for might literally be a fix for a Trojan.
If you already own a valid license but get an activation error, try these safe solutions:
Conclusion
GitHub Microsoft Office Activator CMD errors can be frustrating and time-consuming to resolve. However, by following the step-by-step guide outlined in this article, you should be able to fix these issues and successfully activate your Microsoft Office products. Remember to always use valid product keys, ensure network connectivity, and keep your system files and software up-to-date to prevent future errors.
Additional Tips and Tricks
FAQs
Q: What is the GitHub Microsoft Office Activator CMD tool? A: The GitHub Microsoft Office Activator CMD tool is a command-line tool used to activate Microsoft Office products.
Q: Why do I get an error 0xC004F074 when using the GitHub Microsoft Office Activator CMD tool? A: Error 0xC004F074 occurs when the activation server is unable to verify the product key.
Q: How do I fix GitHub Microsoft Office Activator CMD errors? A: Follow the step-by-step guide outlined in this article to resolve GitHub Microsoft Office Activator CMD issues.
By following the information provided in this article, you should be able to resolve GitHub Microsoft Office Activator CMD issues and successfully activate your Microsoft Office products.
Report: GitHub Microsoft Office Activator CMD Fix
Introduction
Microsoft Office is a widely used productivity suite that offers various applications such as Word, Excel, PowerPoint, and more. However, some users may encounter issues with activating their Microsoft Office software. Recently, a GitHub repository has gained attention for providing a CMD (Command Prompt) fix for Microsoft Office activator issues. This report aims to provide an overview of the GitHub repository, the CMD fix, and its implications.
Background
Microsoft Office requires activation to ensure that users have a genuine copy of the software. Activation involves verifying the product key and linking it to the user's device. However, some users may face issues during the activation process, such as error messages or failed activations. These issues can be frustrating and may impact productivity.
The GitHub Repository
The GitHub repository in question provides a CMD fix for Microsoft Office activator issues. The repository contains a script that users can run in the Command Prompt to resolve activation issues. The script is designed to fix common problems with the Microsoft Office activation process, such as registry errors or incorrect product key entries.
The CMD Fix
The CMD fix provided by the GitHub repository involves running a series of commands in the Command Prompt. The commands are designed to:
The commands are as follows:
net stop msiserver
net stop wmi
net stop winmgmt
cd /d "%ProgramFiles%\Microsoft Office\Root"
del /q /f /s cache
cd /d "%ProgramFiles%\Microsoft Office\Office16"
cscript ospp.vbs /r
net start msiserver
net start wmi
net start winmgmt
Implications
The CMD fix provided by the GitHub repository has both positive and negative implications.
Positive implications:
Negative implications:
Conclusion
The GitHub repository providing a CMD fix for Microsoft Office activator issues offers a convenient and cost-effective solution for users. However, it is essential to consider the potential security risks and implications on warranty and support. Users should exercise caution when running scripts from unknown sources and ensure that they have a genuine copy of Microsoft Office.
Recommendations
Future Research Directions
I can’t help evaluate or review tools that enable bypassing software activation, license circumvention, or other piracy—those are illegal and unsafe. I can instead help with any of the following: Fixes and Improvements: The author has been actively
Which of those would you like?
No products in the download basket.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| cookielawinfo-checkbox-videocontent | 11 months | This cookie is set by GDPR Cookie Consent system. This cookie is used to store the user's consent for cookies in the category "Embedded Video Content" and allows (or disallows) showing embedded video content on our platform. |
| CookieLawInfoConsent | 11 months | The cookie is set by GDPR cookie consent system and it Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| store_notice[notice id] | session | Allows users to dismiss the store notices which might be shown at the top of the page during special announcements, events or during maintenance for example. It does not store any personal data. |
| viewed_cookie_policy | 11 months | This cookie is set by the GDPR Cookie Consent system and is used to store whether or not the user has consented to the use of cookies. It does not store any personal data. |
| woocommerce_cart_hash | session | This cookie helps our project and product 'store' determine when cart contents/data changes. It does not store any personal data. |
| woocommerce_items_in_cart | session | This cookie helps our projects and products 'store' determine when cart contents/data changes. |
| wordpress_logged_in_[hash] | session | The cookie is used to remember that you are logged in, and who you are. Without this cookie the website would not be able to recognize you as being logged-in. The [hash] part represents the value which is generated by applying a specific mathematical formula to the username and password. This is to ensure that the input values are safe and no one can access this data using the cookies. |
| wordpress_test_cookie | session | This cookie is set by the website to test if it can actually set (any) cookies, this is necessary to ensure all other functionality like logging-in, storing whether you allow certain cookies or not etc. This cookie does not store any personal information. |
| wp_lang | session | This cookie is set by the website's framework by default so that it knows which language it should use. This cookie does not store any personal information |
| wp_woocommerce_session_ | 2 days | This cookie contains a unique code for each user so that it knows where to find the cart data in the database for each user. |
| Cookie | Duration | Description |
|---|---|---|
| _twitter_sess | session | This cookie allows the use of Twitter features without having to log in, and contains some tracking information that Twitter uses to improve their services. (However IF Twitter indeed does what it says, the tracking part should be disabled due to the DNT (do not track) setting). |
| # IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookies listed here are just a few of the cookies which will be set by the Twitter Timeline, there are (quite a lot of) other cookies which are also set by the Embedded Twitter Timeline when it's enabled. We do have enabled the enhanced privacy options ("do not track") features of Twitter for this Timeline, we however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the Twitter Timeline) does place additional cookies which we are not able to all list here! |
| ct0 | 11 months | This cookie is set due to Twitter integration and sharing capabilities for the social media. |
| dnt | 12 Months | This seem to be the Do-Not-Track / Do-Not-Taylor cookie, telling the widget not to track/taylor your content depending on our website/widget. Considering this cookie only appeared when we enabled the Privacy feature of the Twitter Widget. |
| guest_id | 11 months | Unspecified |
| personalization_id | 13 months | This cookie is set due to Twitter integration and sharing capabilities for the social media. |
| Cookie | Duration | Description |
|---|---|---|
| _gads | 13 months | This cookie is associated with the DoubleClick for Publishers service from Google. Its purpose is to do with the showing of adverts on the site, for which the owner may earn some revenue. |
| # IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookies listed here are just a few of the cookies which will be set by our advertisement provider, there are (quite a lot of) other cookies which are also set by the advertisement provider (Google/AdSense/Doubleclick) when it's enabled. We do have enabled the enhanced privacy options ("do not track") features for these advertisements, meaning they should only show completely unrelated and non personalized advertisements. We however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the advertisements) does place additional cookies which we are not able to all list here! |
| Cookie | Duration | Description |
|---|---|---|
| # IMPORTANT PLEASE READ! | various | This is additional information, not a cookie! The cookie listed here are just a few of the cookies which can be set by the embedded video player(s), During multiple tests did not encounter any other cookies being placed by the embedded player accept about 4 ("randomly named") cookies once or twice during some extensive testing while using Chrome (other browsers did not seemed to do this). We however (of course) do not have control over possible cookies set and/or created by externally embedded content. This is also the reason why we disable the content altogether when you don't allow their cookies. You can view which cookies exactly are being placed by websites using the developer console of your browser, where and how to find this depends on your browser, but for most browsers this can be opened using F12 on your keyboard. Please make sure that you understand that externally embedded content (like the Embedded Video Content) can or does place additional cookies which we are not able to all list here! |
| CONSENT | 11 months | This cookie is placed by the youtube-nocookie.com domain, we suspect that it is used to tell the player that 'consent for cookies or user-tracking' is pending (and thus should not happen) because the data within this cookie says: "PENDING+162". However we unfortunately can't confirm this because there is almost no other website or information available about this cookie. And despite the fact that almost ANY website with "GDPR Compliance Tips" tells you to "just use the YouTube-nocookie feature" to be GDRP Compliant without having to ask user consent, we do not agree! Due to the simple fact that it does still place this cookie. And due to the fact that when enabling the "YouTube Privacy Enhanced feature" it gives a popup saying: "When you turn on privacy-enhanced mode, YouTube won't store information about visitors unless they play the video.", we just don't like this kind of 'sketchy behavior' and thus require you to allow such cookies and content before we will actually display it. |