How to get a Windows 10 „Memory integrity“ debug log (Core isolation)

So you want to enable Windows 10’s security feature „Memory integrity“ which is part of „Core isolation“? But when you move the switch to „On“, you always get the error message „Memory integrity can’t be started. There may be an incompatibility on your device“?

Windows 10 Core isolation Memory integrity
Windows 10 Device security Memory integrity can't be started. There may be an incompatibility on your device

Here is how to figure out what is incompatible on your device

  1. Download Microsoft’s official „Device Guard and Credential Guard hardware readiness tool“, which is basically a PowerShell script. Extract the downloaded zip file to a folder of your choice.
  2. Open PowerShell with „Run as administrator“ (admin privileges) and navigate to the folder with the extracted files.
  3. First we have to allow executing the script using this command:
    Set-ExecutionPolicy Unrestricted
  4. Execute the script using the „Capable“ parameter:
    .\DG_Readiness_Tool_v3.6.ps1 -Capable
  5. Now the script will install a special driver used to verify your hardware and installed drivers, but you have to restart the PC and come back to the script afterwards. So restart the PC now!
  6. Again, open PowerShell with „Run as administrator“.
  7. Again, execute Microsoft’s tool using the „Capable“ parameter:
    .\DG_Readiness_Tool_v3.6.ps1 -Capable
    Now the script should execute the scan using the special driver, thus checking your hardware and drivers for compatibility.
    You will get a colored log directly in PowerShell and also a log file stored on your disk, the location is:
    C:\DGLogs\DeviceGuardCheckLog.txt
    Check for yellow and red lines in the log and if your are especially interested in incompatible drivers, then look for a message
    Incompatible HVCI Kernel Driver Modules found
    Incompatible drivers should be listed below that message.
  8. So now that you have your log file, let’s clean up the system again (i.e. remove the special driver that was installed by the script).
    Execute Microsoft’s tool using the „Clear“ parameter:
    .\DG_Readiness_Tool_v3.6.ps1 -Clear
  9. Restart the PC to get the special driver uninstalled.
  10. Again, open PowerShell with „Run as administrator“.
  11. Now we also restore the default safe script execution policy using this command in PowerShell:
    Set-ExecutionPolicy Restricted
  12. Done!

Kalenderwochen im Windows 10 Kalender richtig einstellen

Wochennummern in der „Mail und Kalender“-App von Windows 10 richtig anzeigen lassen

Damit die Kalenderwochen für Deutschland korrekt angezeigt werden (entsprechend ISO 8601), muss in der Kalender-App von Windows 10 folgendes eingestellt werden:

  1. Einstellungen -> Kalendereinstellungen -> Erster Tag der Woche -> Montag
  2. Einstellungen -> Kalendereinstellungen -> Wochennummern -> Erste 4-Tage-Woche
Windows 10 Kalenderwochen bzw. Wochennummern korrekt einstellen für Deutschland

Die 1. Einstellung „Montag“ erfüllt das erste ISO 8601 Kriterium: „Kalenderwochen haben 7 Tage, beginnen an einem Montag und werden über das Jahr fortlaufend nummeriert.“

Die 2. Einstellung „Erste 4-Tage-Woche“ erfüllt das zweite ISO 8601 Kriterium: „Die Kalenderwoche 1 eines Jahres ist diejenige, die den ersten Donnerstag enthält.“

How to uninstall NVIDIA Telemetry Container (clean deinstallation)

  1. Open an elevated command prompt (i.e. cmd as administrator)
  2. Run this command:
rundll32 "%PROGRAMFILES%\NVIDIA Corporation\Installer2\InstallerCore\NVI2.DLL",UninstallPackage NvTelemetryContainer

Ubuntu’s counterpart for Windows 10’s „Bass Management“ and „Speaker Fill“

If your PC is connected to an analog 5.1 or 7.1 surround sound system, you probably have these two sound options enabled in Windows 10:

  1. Speaker Fill (to hear stereo music from all the speakers and not only from two)
  2. Bass Management (with a crossover frequency set to the value recommended by your subwoofer manufacturer)

Achieving the same thing on Ubuntu 18.04

  1. Enable surround sound in Ubuntu’s settings GUI and make sure you hear sound from all channels when you click the test button
  2. Open pulseaudio’s configuration file daemon.conf. If the file
    ~/.config/pulse/daemon.conf
    does not exist then just edit
    /etc/pulse/daemon.conf
  3. Find the following configuration variables, uncomment them and change their values as shown below:

    enable-remixing = yes
    remixing-use-all-sink-channels = yes
    enable-lfe-remixing = yes
    lfe-crossover-freq = 150

  4. Stop and restart pulseaudio to apply your changes by executing these two commands:

    pulseaudio -k
    pulseaudio -D

    If you get an error on the second command you probably can ignore it. At least in my case the daemon was restarted although I got some error.

And here is what the configuration variables do:

  • Enabling the variable „remixing-use-all-sink-channels“ has the same effect as enabling „Speaker Fill“ on Windows.
  • Enabling the variable „enable-lfe-remixing“ has the same effect as enabling „Bass Management“ on Windows.
  • Assigning a value different from 0 to „lfe-crossover-freq“ lets you specify the proper crossover frequency recommended for your subwoofer. So you should probably NOT use 150 Hz as I did in the example above and instead use a value that is recommended by your subwoofer manufacturer!