Windows-10 upgrade notes
on the PC to be upgraded, and ensure that you can get remote access to it before
you start the upgrade. Set up the Unattended Remote Access.
As with Windows from Vista onwards, there are some programs which are better
installed outside the Program Files tree, as they have user-editable data
stored in the program's directory. For such software, I recommend using a
separate "Tools" directory, set with completely open security.
There are some notes here.
Things I routinely change after upgrading
- Disable password-protected file sharing. This allows Windows systems
lower than 10 to access shares without needing to specify a user name and
- Turn off Update propagation over the network. To reduce network
traffic and allow me better control.
- Set the SNMP service to accept packets from any host. The default is
local host only, even if all hosts were allowed before the upgrade.
- Either: Control Panel, Administration Tools, Services
Or: Control Panel, search for "local", View local services.
- Select the SNMP service, right-click, Properties
- Security tab
- Either: check "Accept SNMP packets from any host"
- Or: add at least 127.0.0.1 (from Arne van Belle)
- Press the restart service button on the toolbar
- If you are using the Interface Number in MRTG, you may need to check that
it hasn't changed. Generally now I prefer to use the IP address rather
than the Interface Number. With Linux boxes I prefer the interface
Things I need to re-install for MRTG monitoring
I found that these programs needed to be uninstalled and then re-installed
during the Insiders Preview period of Windows-10, and it seems that the same
applied to upgrades.
- SNMP Informant
- the Standard Version 1.7 works correctly.
- 4.5.1 works correctly. You may need to check the index numbers when
- SpeedFan SNMP extension - sfsnmp-0.1.2.tgz - works correctly. This
download seems to have disappeared, but I have copies.
- PL2303 serial over USB. There's no driver which supports the older
chip I have in this device, so after the upgrade, and getting error code
-10, I tried telling the PC to search for the previous driver in the
Windows.Old\Windows\System32\ directory, and it found, installed, and is
happily using that previous driver (from Windows Vista I believe).
- A Chinese AE1200 USB Wi-Fi adapter was not recognised, but the same method as
above produced a working driver. As this was then a "new"
device, the Wi-Fi credentials needed to be added again.
- If you are using NTP with the serialpps.sys driver, that will need to be
installed again. On one PC I needed to stop and restart the NTP
service even after installing the driver and rebooting.
- The Zadig driver fix for RTL DVB-T dongles has to be reinstalled.
Windows Help (old version for .HLP files)
I needed to open a .HLP file on one PC, so I took the WinHelp32.exe from an XP system and placed it in C:\Windows\
Note that you need to change the ownership of the Win-10 WinHelp32.exe to e.g. David, add David to the
permissions list, and give him Full Control. David can then rename the file to e.g.
WinHelp32.new.exe and copy the XP version.
Whether this survives across reboots or updates is yet to be discovered!
My own personal preference is still for the free Classic
Shell add-on, but my wife prefers the native Win-10 shell.
PKI eToken issue
Ian Deans reports:
I recently reported that both myself and Douglas were seeing intermittent problems with Windows 10 boot up. In my case my main
EUMETCast computer was most of the time not booting at all.
We quickly established that the problem was the eToken and removing it returned boot ups to 100%. One or two different things were tried including
re-loading software/drivers under Windows 10, but no improvement was achieved.
The current Aladdin software/drivers used by EUMETSAT is PKI client 4.5 which is probably 9 years old, but Aladdin was taken over by Safenet a few
years ago and I could not find any software/drivers for the eToken on their site. However trawling through the internet I came across a Windows 7 SP1
update for the eToken which was PKI client 5.1 and probably from 2009. Both Douglas and myself installed the 5.1 client ( after completely removing
PKI 4.5 ) and the boot up issues have been completely resolved.
- Needed to set the IP address of the virtual network card (Tap) to the same
address as in BDADataEx.
- Only needed to allow throughput monitoring to work.
I have seen one report that the new Edge browser does not work with
TelliCast, although it seems to work here.
- The PIE
Studio program required entering its licence key again, but I had already
updated all my own software to the non-hardware-locked versions.
- If you are installing NTP afresh,
likely you will need to use the SYSTEM account rather than the preferred NTP
- One PC didn't seem to like the ISO which I had burned to DVD, so I used
- One PC said invalid licence with the DVD, but was fine with the
- You will need to see the display and have a mouse or keyboard connected
during the later stages of the upgrade to be able to click on
- A couple of PCs seem to not be able to use the Power, Restart correctly,
and hang with a black screen. A power reset allows normal boot to
continue. Two reports that this could also be related to the EUMETCast
eToken issues mentioned above.
- The black screen issue, and possibly the issue below, may be fixed by
disabling the fast start-up. See:
- A Tesco 7-inch tablet upgraded correctly, but the display was continually out of
sync (like a TV with frame roll, but worse) during the upgrade. Fortunately, having Team Viewer
installed and allowing remote access saved the day. The device worked
normally after the upgrade a couple of power-down reboots.
- One Windows-7 Starter PC showed a high CPU usage after upgrading, which
was fixed by re-registering the Apps. See: http://www.tenforums.com/tutorials/3175-apps-re-register-windows-8-10-a.html
- On the same PC the time zone was wrong, but easily reset, of course.
- On a virtual PC running VMware Player the network connection was lost, but
this was fixed by updating to the current VMware Player software: VMware-player-7.1.2-2780323.exe.
Saw this on the Creators Update as well, fixed by updating the player from
12.5.2 to 12.5.5.
- On a PC with VMware Workstation 8, a repair install was needed to get the
licence manager working. The virtual PC worked correctly after that.
- If you are installing afresh from Windows Vista or XP, expect that some
older programs may not react well to the reduced user-mode privileges
available when they are installed inside the C:\Program Files\ tree, and you
may solve that by creating a new C:\Tools\ tree. See here
Generally, by far the easiest Windows update yet, taking between 1 and 2 hours.
A few peculiarities after updating in November 2015 to the version 1511
- Settings for the Task Manager such as full details view and columns
selected were reset from what I had to some new default settings.
- Size and position of the Notepad.exe window was arbitrarily reset - which
on my systems had been fixed for a long period for a precise position and
- Lost connection to network printer. Cured by using Explorer to look
at the PC with the printer, selecting the printer, and right-click
Connect. From a command prompt:
- The PIE
Studio program required entering its licence key again.
- The sleep.exe program had been removed by the update, even though it was
working correctly. This required editing a command file to use the
timeout command instead.
- Needed to do the SNMP allow all nodes access, SpeedFan & SNMP extensions
uninstall, and SNMP Informant re-install, as listed above.
- Needed to reinstall serialpps.sys for NTP (didn't need to do this for
the Win-7 to Win-10 upgrade, though). It seems that the update removed
references to this driver. Run the Install.bat in an
Administrator mode command prompt from the download: http://people.ntp.org/burnicki/windows/serialpps-20120321-signed.zip
Windows 10 Anniversary Update (Version 1607)
The Windows 10 Anniversary Update was released at the start of
August-2016. As none of my PCs was showing the update as being available
just yet, I downloaded the update tool here.
Look for the button labelled: "Get the Anniversary Update now".
This provides a 5.6MB file which will start the update process, downloading
Windows from the Internet. Allow between 1 and 3 hours depending on your
PC's speed (disk, processor, network), and Wi-Fi will likely be slower than a
100 Mbps LAN connection. You can carry on working during the first 15-30
minutes, and you get a 30-minute warning before the PC will reboot. I
found a few oddities, likely most specific to my PCs' configuration, but I'll
list them here just in case.
- Two tablet PCs with just 32 GB of SSD storage would not even start
the update process as it said it needed 16 GB free. I am waiting to
see whether the non-forced update has the same issue.
- If you have scheduled tasks which start at midnight then repeat every 30
minutes (or whatever), those tasks will not be started after the upgrade,
and may require a manual restart, although this appears to fail as the job
doesn't run. They will be started at the next
midnight otherwise. Unless the task includes a critical time element
(e.g. it must run at 23:59), consider starting the task at boot or user
login, repeat every 30 minutes, repeat "Indefinitely".
- One PC needed a network drive to be restored by hand: X: => \\PC1\SharedDocs
This didn't happen on other PCs and could simply have been my impatience!
- The PL2303 driver had been updated by Windows. I needed to point the
USB serial device at an older driver version. See: http://www.miklor.com/COM/UV_Drivers.php
Condensed: Unplug USB serial, install 220.127.116.11 drivers from the Vista install, plug the USB, Device Manager, select port, Update driver, choose from drivers on the PC, Ports, select 18.104.22.168.
- On one EUMETCast PC with the TBS5925 USB box, the interface numbers changed, and so
needed to be edited in MRTG.
- One PC taking EUMETCast HVS data seemed to have problems getting data,
even though it was getting the Announcement channel. The eToken was
OK. Nothing in the log file. As I was pinging the IP receiver to
see whether it was alive, TelliCast started seeing data. Unsure why
- I have the impression that the TelliCast 2.12.1 process is using a little
more CPU (2% vs. 1% on the receive-only PC Harstad since Sunday,
2016-Aug-07, week 31 - see: Harstad CPU
On other TelliCast PCs it's more difficult to see the effect as the CPU
usage is much higher.
- One PC had problems with a VMware Player virtual PC, eventually cured by
opening the virtual PC in VMware Workstation. Then the player worked,
albeit with a very slow start-up.
- On all PCs I needed to reset the SNMP service security uninstall and
then re-install SNMP
Informant and SpeedFan to allow all my MRTG monitoring to
work. Needed to reinstall serialpps.sys for the stratum-1 PPS NTP
server allowing kernel level PPS precision.
- The settings for the Task Manager had changed back to "Fewer
details" with a previously added column removed.
- If your printer was switched off at the time of the install, you may need
to re-connect from any remote PCs. The same fix mentioned above works,
by using Explorer to look
at the PC with the printer, selecting the printer, and right-click
Connect. From a command prompt:
- James Brown writes: On my processing machine I lost audio drivers and needed a reinstall action of Adobe Audition.
Some program defaults also got reset to MS preferences rather than mine.
- Jan Verduyn notes on the VNWA
Yahoo group: Microsoft is currently rolling out Windows 10 Anniversary edition, which requires the VNWA USB
codecs to be reconfigured. Following the Windows 10 Anniversary upgrade when you plug-in the VNWA in a USB socket, the USB
codec drivers are automatically updated to driver version 10.0.14393.0 dated 15/07/2016 by Windows.
Depending on your Internet and processor speed, this may take from 10 seconds up to several minutes.
After the drivers have been updated the previous USB codec settings are lost and new settings must be configured.
The best method to do this is to reboot your PC after the new drivers have been installed.
Plug in the VNWA and run VNWA application. Use "Auto-Setup Audio Devices" in the Audio Settings Tab, and follow the on screen instructions.
Most likely you will have to change the USB codec settings to 2 Channels 48000
bps. If you connect the VNWA to a different USB port then you have to follow the same procedure again.
There's a much more comprehensive list here.
Windows-10 Creators Update (build 1703)
The story so far ...
- Immediately after install, run Settings, Updates to check if there is an
update available. This resolved one issue for a user with an early
version of the TelliCast software.
- It seems that the Network tab in File Explorer won't show any connected
PCs until all Win-10 PCs are at 1703, and even then, PCs running Windows
other than 10 are not shown.
- On Windows-10/32 Home I found that the SNMP extension for SpeedFan no
longer worked. I ended up writing a small program which reproduced the
functionality for MRTG so if you need this please contact me.
- If you have previously used a serial port for GPS/NMEA data for NTP, you
might find that the Microsoft Ballpoint Mouse becomes detected afresh and
re-enabled after the update, and you will need to disconnect the device from
the port and disable the Ballpoint mouse once again.
- On one PC I found that TeamViewer wouldn't accept incoming connections
after the update. Uninstalling and re-installing TeamViewer fixed that
- Thorsten Miglus reports that in a repeatedly looping shell script the
"move" command causes a memory leak when it produces an error. Replacing
"move" with the equivalent "robocopy" command resolves
the issue. robocopy C:\dir1\ C:\dir2\ *.jpg /move
- If you are running the BDADataEx software, it's recommended that you
update to the current version and the current SignalEx.exe too.