The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,887 other followers

Archive for the ‘Windows 10’ Category

Chocolatey and TLS since early 2020

Posted by jpluimers on 2020/03/19

I was upgrading a few older systems that had been off-line for quite a while.

When installing Chocolatey, I bumped into this error:

C:\bin>"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString(''))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
Exception calling "DownloadString" with "1" argument(s): "The request was aborted: Could not create SSL/TLS secure channel."
At line:1 char:1
+ iex ((New-Object System.Net.WebClient).DownloadString('https://chocol ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

So I tried [WayBack] chocolatey “The request was aborted: Could not create SSL/TLS secure channel.” – Google Search

Results indicated TLS 1.1 support was removed early February 2020 from Chocolatey because of security reasons, which impacts the installation on older systems:

Note [WayBack] Chocolatey install Error: The request was aborted: Could not create SSL/TLS secure channel – Stack Overflow with a temporary workaround for Microsoft Windows Server 2016:

Looks like the security protocol changed:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString(''))


Posted in Chocolatey, Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2016 | Leave a Comment »

Fixing “one or more critical volumes is not having enough free space” also known as 0x81000033 during Windows backup

Posted by jpluimers on 2020/02/03

If you get this error:

Backup and Restore failed and you receive the following error message: The backup did not complete successfully. Check your backup: Windows Backup skipped backing up system image because one or more critical volumes is not having enough free space.

then you are dealing with error 0x81000033 which usually means your SYSTEM RESERVED partition is full, but might happen on other volumes you are backing up as well.

Windows tries to trick your mind, as the error actually indicates the disk you make your backup to, but in fact it is about one or more of the disks you are backing up.

Most often, this is the hidden partition SYSTEM RESERVED (sometimes called System Reserved):

The SYSTEM RESERVED partition (~100 megabyte on systems originally installed with Windows < 8 and ~350 megabyte afterwards) contains files relating to boot, recovery and BitLocker drive encryption. You find more information about it here:

The minimum free size for volumes when using Windows backup are these:

  • volumes less than 500 megabytes: 50 megabytes free space
  • between 500 megabytes and 1 gigabytes: 320 megabytes of free space
  • more than 1 gigabytes: at least 1 gigabyte of free space

That was indeed the case on my disk:

Freeing space on the System Reserved volume

A quick search for 0x81000033 reveals space issues usually are about the USN Journal which you can configuring using fsutil.

Even though the documentation doesn’t tell, fsutil accepts not just a drive letter as VolumePath, but also a VolumeName. [WayBack] 1_multipart_xF8FF_3_WolfC07.pdf (Chapter 7 of “Troubleshooting Microsoft Technologies: The Ultimate Administrator’s Repair Manual“) gets that right:

volumepath … specify the path to a logical volume (drive letter, mount path, volume name).

So you do not need a drive letter to disable the USN journal, the volumename suffices.

This volume name is the unique NTFS identification for a volume: [WayBack] NTFS Curiosities (part 2): Volumes, volume names and mount points – Antimail

You can find the volume name inside PowerShell by using Get-Volume | Format-List, then on an administrative command prompt running this:

fsutil usn deletejournal /D \\?\Volume{b41b0670-0000-0000-00e8-0e8004000000}\

In my case this wasn’t enough, so I had to assign a drive letter to see that there was a snapshots directory in the root:

Deleting that directory solved the problem.

Related articles:


Read the rest of this entry »

Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »

XW6600 WOL – stopped working on Windows 10 – my trusty APC PDU to the rescue

Posted by jpluimers on 2020/01/17

A long time ago I wrote in Mac/PC: sending Wake-on-LAN (WOL) packets « The Wiert Corner – irregular stream of stuff “I’ve succesfully woken up these machines: HP XW6600 running ESXi 5.1 ThinkPad W701U running Windows 7”.

The XW6600 have now been demoted to Windows 10 machines that I only need every now and then, so most of the time they are shutdown.

However, with the installation of Windows 10 however, they stopped reacting to WOL (Wake on LAN).

Per web-search results, I’ve tried all the permutations of the below settings to no avail.

Luckily, my trusty APC PDU AP7921 (and little sister AP7920) helped out: when setting the “Reboot Duration” to 30 seconds or more (so the power fully drains), it can be rebooted.

Note that since I bought these a long time ago, they have been replaced by these:


Power usage:

  • an XW66000 with 32 gigabytes of RAM and one hard disk takes between 0.6-1.2 Ampère of current, which at 230 Volt is 140-275 Watt.
  • over one day that is between 3.4 and 6.6 kWh

Settings tried

Read the rest of this entry »

Posted in Ethernet, Hardware, HP XW6600, Network-and-equipment, Power User, Wake-on-LAN (WoL), Windows, Windows 10 | Leave a Comment »

How to change the User Account Control (UAC) level in Windows | Digital Citizen

Posted by jpluimers on 2019/11/18

Based on, but much shorter than, [WayBack] How to change the User Account Control (UAC) level in Windows | Digital Citizen which summary is

How to change how UAC prompts are shown in Windows 7, Windows 8.1 and Windows 10. How to disable UAC when you no longer want it turned on.

  1. Run UserAccountControlSettings.exe
  2. Pull the settings up to the highest one
  3. Confirm


Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »

Enable/Disable Windows 10 “tray” notification area icons

Posted by jpluimers on 2019/08/19

It looks like they reorganised the way you can enable/disable the Windows Notification Area icons (often called “Icon Tray”) in Windows 10.

Up until Windows 8.1, you could run this:

%SystemRoot%\System32\rundll32.exe shell32.dll,Options_RunDLL 5

There you would end up editing the application specific icons.

As of Windows 10, you need to:

  1. Run %SystemRoot%\System32\rundll32.exe shell32.dll,Options_RunDLL 6
  2. Click on “Select which icons appear on the task bar” (or Dutch “Selecteren welke pictogrammen op de taakbalk worden weergegeven”)

So both the index changed, and you need an extra click to get at the application specific icons.

Further more, you can now only turn them on or off, where up until Windows 8.1, you could also choose only show notifications. I think on means only show notifications as for instance the Java Updater with a setting on on Windows 10 disappears after a Java Update has been installed, whereas on Windows 8.1 it would stay unless you switched from on to only show notifications.

The above commands are based on [WayBack] Create Direct Shortcut for “Notification Area Icons” in Windows Vista and Later – AskVG and


Posted in Power User, Windows, Windows 10 | Leave a Comment »

%d bloggers like this: