Windows 7 to 10 or Windows 10 Feature Upgrade – error 0xC1900202 / 0x00000000

Finally worked out what the issue with upgrading out machines to Windows 10 from Windows 7 was – if you get a 0xC1900202 error this is “0x80240020 WU_E_NO_INTERACTIVE_USER Operation did not complete because there is no logged-on interactive user.” This points to this Microsoft Article which explains the issue can be resolved by a registry key.

  1. Locate the registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]

  2. It should exist, but if not, create it.

  3. Create a new DWORD (32-bit) Value with Name = “AllowOSUpgrade” (without the quotes), and set the Value = 0x00000001.

Check for updates and Windows 10 should now show as avalible.

This does not appear to exist as a GPO setting, so you will need to put this reg key in with your WSUS GPO (or a similar GPO policy)


Dell XPS 13 9370 Mini Review

In work we buy Dell XPS 13 units for those that staff that use a laptop. Previous models have been in the 9350/9360 line, however, we’ve recently recieved two new 9370 units with 8th Gen Intel, so I thought I’d post a few comments and pictures on them, compared to previous models.

The main difference on these is they now have three USB C ports, two on the left side, and one on the right. The two left ones can be used for charging. There’s also a Micro SD card port on the right, as well as a 3.5mm headphone port. This is a change as there are no USB3 ports and the charger uses a USB C instead.

First noticeable difference is that there is no magnetic access flap on the bottom of the unit. The serial and identifying numbers are instead printed along the bottom by the vents.

The keyboard layout is the same as before, with a full-size enter button. There’s no changes to this that I can see, however, the touchpad seems to be slightly larger, and the function buttons also share the F1 keys.

The screen on this model is extremly glossy and shiny. We tend to buy matte screens but I don’t actually know if this is an option on the newer models. This is a non-touch screen (which is just as well, because otherwise it would be instantly covered in fingerprints. The main thing on the screen area is the webcam is now in the bottom middle of the screen, instead of the bottom left hand corner. It’s still not a flattering angle, however, for Discord or Skype conversations it should be fine. This also includes Windows Hello for facial recognition too.

As mentioned there are 3 USB C ports, a 3.5mm headphone port and a Micro SD Card slot. There’s also an apple-eque battery monitor button on the left hand side. The USB charger also has a LED on to indicate power and enables you to find it better if you’re rummaging around in the dark – nice touch.

One major change however is the lack of the power light on the power button. The only indication of the machine being powered on is the light on the front of the machine now. I’m not a huge fan of this, and a colleague who has an older machine with this function was a bit confused when I showed him this.

The screen is nothing short of *awesome*. That’s all I can say. This picture doesn’t do it justice. It’s only a 1920×1080 resolution screen but the image quality is spectacular.

Okay, let’s go with a full machine spec sheet.

CPU: Intel Core i5-8250U CPU @ 1.60GHz – 4 cores, 8 threads.
Graphics: Intel UHD Graphics 620
Storage: PM961 NVMe SAMSUNG 256GB
Wireless: Killer Wireless-n/a/ac 1435 Wireless Network Adapter
Screen: 13.3″ Full HD display
OS: Windows 10 Pro
Colour: Silver
Price: £970 (Amazon)

Overall an improvement on previous models. We’ll have to see what the users that will be getting them think…

Dell XPS 13 asking for Bitlocker key every startup

I’ve recently been encrypting our fleet of Dell XPS 13 laptops ready for GDPR compliance come May 2018. I have had some issues with the machine asking for the bitlocker recovery key on each startup and from what I can tell this involves a TPM level 2.0 being used when Secure boot mode is off and Legacy boot options are used. A TPM 2.0 does not like secure off and legacy boot options, so I found the solution (for me at least, on Dell XPS 13 9360 units) was to use the Dell TPM Switcher Utility and downgrade the TPM from 2.0 to 1.2. This has to be done from Windows, but I found disabling Bitlocker, downgrading the TPM, and then enabling BitLocker resolves the issue.

Windows 7 USB Drivers for a Razer Phone

[To finish]

Razer Phone (USB Hardware ID: USB\VID_1532&PID_9052&REV_0404 and USB\VID_1532&PID_9052) says driver software cannot be installed when using Media Transfer Mode. Transfer Photos in PTP mode works fine however. Using a USB3 or USB2 port doesn’t seem to make a difference, and using an Anker USB3 to USBC also does not work.

Plugging into my work desktop PC (Dell Optiplex 7010) running Windows 7 Enterprise picks up fine, also using an Anker USB3 to USBC cable. Following drivers are loaded:

Phone manual (english).

Editing a Windows 7/Windows 10 Hosts File

The Hosts file is a file within Windows which can be used to map IP addresses to hostnames, and can also be used to override settings from DNS servers. The file can be found at C:\Windows\System32\drivers\etc however you will need to run NotePad (or Notepad++) as administrator, as it is a protected system file.

Search for Notepad, then right-click and “Run as Administrator”.





You can then add and edit the hosts file as nessecary. The lines starting with # are comments and will be ignored by the system.

WSUS stuck on “Downloading Updates 0%” for Windows 10 1503, 1511, 1607, 1703 upgrades and 7/8 to 10 upgrade.

Wow, that’s some title gore.

In my work I have taken ownership of our WSUS Server. All updates have been approved/declined fine and are deploying and installing correctly, with the exception of the Windows 10 Feature Updates. These are the major updates to Windows 10, versions 1511, 1607 and 1703,  more commonly know as the Anniversary and Creators’ updates. The symptoms of this issue is the machine appears to start to download the update and then gets stuck on “Downloading Updates 0%”.

The tl;dr version is that I am 99% sure it is down to the corporate proxy. We added a entry on our internal squid proxy for the WSUS server name and the FQDN of the WSUS server as resolutions to the web server that WSUS ran on was failing, even though the GPO for specifying the download location was set correctly. If you would like to test it yourself I would suggest changing the hosts file of an affected machine. I am still in the process of testing this, however, and will update when I am fully happy how to solve the issue.

First off, check the WindowsUpdate.log file on the client. This can be found on C:\Windows\WindowsUpdate.log on Windows 7, or by invoking the Powershell command get-windowsupdatelog on a Windows 10 machine.

Check the server status:

2017/06/23 11:51:16.7784571 1068 1500 Agent
WSUS server
: 11:51:16.7784577 1068 1500 Agent
WSUS status server:

Check that the reporting and client/server URL is set and accessible on the client

2017/06/23 11:48:43.9962046 288 4180 Misc
Got WSUS Reporting URL:””

2017/06/23 11:48:44.0327708 288 4180 Misc
Got WSUS Client/Server URL:””

Check for 0x80244022 for filetypes, especially the .esd and .exe, and look at the URL.

2017/06/23 10:18:41.2272275 892 1020 DownloadManager
File: http://officewsus01:8530/Content/0F/ACAF6BAF9D5F52B23E3136BB847CFDB49E357B0F.esd

2017/06/23 10:18:41.2309928 892 1020 DownloadManager
Error 0x80244022 occurred while downloading update; notifying dependent calls.

If I browsed to the http://officewsus01:8530/Content/0F/ACAF6BAF9D5F52B23E3136BB847CFDB49E357B0F.esd URL, I got a “page cannot be displayed” error message. If I manually changed the URL to it worked fine.

We put in a entry in the hosts file of the machine name and the fqdn of the wsus server name and then tried to access the http://officewsus01:8530/Content/0F/ACAF6BAF9D5F52B23E3136BB847CFDB49E357B0F.esd URL which worked. Checked for update, this then downloaded the content fine.

Further reading: my WSUS Technet forum thread.

When trying to resolve this I:

  • Check that the KB3159706 for decryption of ESD content is installed
  • Checked that the prerequisites for KB3095113 are all installed
  • Checked that the KB3095113 for WSUS support for Windows 10 feature upgrades.
  • Set the MIME type on the IIS Server for the .esd file and .msu file types(which the above update should have sorted).
  • Removed the Windows Update cache from the machines, stopped the BITS/Windows Update services and restarted.
  • Restarted IIS Website
  • Rebooted WSUS server
  • Checked Windows Firewall status (disabled on Server)
  • Asked the Windows 10 machine to get updates from Windows Updates rather than WSUS (this appeared to download and install OK) so this makes me think it’s an issue with our WSUS server.
  • Installed the Windows 10 ADMX templates and set the “Download Mode” in GPO to both “Bypass”  and “HTTP only”.
  • Set WSUS to download express installation files (don’t do this unless you have the storage, it bloats the WSUS content folder).
  • Build a different Windows Server 2012 R2 machine, updated Windows Update GPO policy and got machines checking in, but download of this one update does still not happen.

“Catastrophic Failure” on deleting a BackupExec Backup to Disk Volume

Recently ran into an issue which required me to remove and re-add the Backup to Disk location within Backup Exec. However when I tried to remove the location Backup Exec popped up with “catastrophic error”.

  1. Download and install the Microsoft SQL Server 2012 Management tools (found here).
  2. Go to Backup Exec – Configuration and Settings – Backup Exec Services -Stop all services, or, stop all the services from the Services.msc console
  3. Stop the SQL Server Servoce
  4. Go to the C:\Program Files\Symantec (or Veritas)\Backup Exec\Data folder and take a copy of the .mdb and .mdf files.
  5. Open SQL Management Studio 2012
  6. Connect to Backup Exec Server, then choose “Databases” – “BEDB” (or name of database) – “Tables” – “dbo.device” and choose “Edit first 200 rows”.
  7. Find the device with the issue (typically use the device name).
  8. Delete the row.
  9. Go back into Backup Exec and start all services.
  10. Go to the Storage tab and re-add the backup to disk location.

That should do the trick. Thanks to “munetadmin” on

Writing last logged on user to a machine’s description field in AD (with serial and model of machine)

Originally from

  1. Open Active Directors Users and Computers MMC
  2. Right click on your domain, and select ‘properties’ from the context menu
  3. On the ‘security’ tab, click the ‘advanced’ button
  4. Click the ‘add’ button, type ‘Authenticated Users’. Then click OK.
  5. In the permission > properties >  dialogue, set the ‘apply to’ pull-down menu to ‘Descendant Computer Objects’, allow the option for ‘Write Description’

Save the following script as a vbs file, then create a logon script policy.

Set WshNetwork = WScript.CreateObject(“WScript.Network”)
Set objWMI = GetObject(“winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2”)
‘ Get service tag and computer manufacturer
For Each objSMBIOS in objWMI.ExecQuery(“Select * from Win32_SystemEnclosure”)
serviceTag = replace(objSMBIOS.SerialNumber, “,”, “.”)
manufacturer = replace(objSMBIOS.Manufacturer, “,”, “.”)
‘ Get computer model
For Each objComputer in objWMI.ExecQuery(“Select * from Win32_ComputerSystem”)
model = trim(replace(objComputer.Model, “,”, “.”))
‘ Get computer object in AD
Set objSysInfo = CreateObject(“ADSystemInfo”)
Set objComputer = GetObject(“LDAP://” & objSysInfo.ComputerName)
‘ Build up description field data and save into computer object if different from current description
‘ We also do not update computers with a description that starts with an underscore (_)
newDescription = WshNetwork.UserName & ” (” & serviceTag & ” – ” & manufacturer & ” ” & model & “)”
if not objComputer.Description = newDescription and not left(objComputer.Description,1) = “_”  then
objComputer.Description = newDescription
end if

Upgrade your HP printer firmware with this one weird trick! (technicians hate him)

Sorry for clickbait title.

Anyhow, if you have HP Printers and need to upgrade the firmware, you can actually download the firmware and then submit it to the printer via the “print job” form in the printer web interface to upload and update the firmware. This is easier than trying to use the “firmware sender” utility.

To do this, first locate, download and extract the printer firmware. This will be in a .rfu file format.

Next, go to the web interface of the printer and view the Information > Print tab.

Click on “Browse” under the file selector, then locate and click on the .rfu file that has been extracted.

The printer will then upload and upgrade itself. This may take a few minutes depending on size of the firmware.

Once done the printer will then tell you.