While trying to log in on our Novell servers using Client for OES 2 SP4 IR7a on Windows 10 1709, I was greeted with:
A required network service has not started.
Please check your error log for details.
The third reply of this post gave me a clue, simply run
setup.exe one more time and reboot.
Uninstallation of IR7a still gives me error
0x80070005. The Registry settings in
HKEY_LOCAL_MACHINE\SOFTWARE\Novell was accessible to me as a regular user. Maybe the client’s uninstaller is complaining about rights in the filesystem.
iobit‘s uninstaller free saved the day.
I really wish for more specific error messages.
yourscript.cmd from an elevated Command Prompt window eliminated all my problems. Search for “Command Prompt” on the start menu and hold down Ctrl+Shift when you click on the menu item. Simply right-clicking on
yourscript.cmd and selecting “Run as administrator” proved to be insufficient. Creating
HKEY_LOCAL_MACHINE\SOFTWARE\Novell manually might also set things straight.
0x800F081F while installing .NET Framework 3.5 on Windows 10 might be due to corporate WSUS servers not allowing such updates.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU in the Windows registry and set
0 (zero). Restart the Windows Update service (
net stop wuauserv & net start wuauserv) and retry installing .NET Framework 3.5. Set
UseWUServer back to
1 (one) and restart the Windows Update service.
I keep Star Trek Online installed in two separate directories. One of the copies is simply a backup which I update but never play, while the other is for playing.
Keeping these two copies updated got a bit messy after the STO launcher began recording the
InstallLocation in the Windows registry.
Subsequently, I have to remove this value from the registry prior to launching the game from another location.
reg delete "HKEY_CURRENT_USER\Software\Cryptic\Star Trek Online" /v "InstallLocation" /f
One or more of the recent updates for Windows 10 rendered my laptop incapable of communicating with the outside world. The Windows Firewall failed to run due to Base Filtering Engine not being able to run either. It’s the dreaded “Error 5: Access denied” error message all over again. Windows 10 also thought it was not activated, which is plain wrong. And no, I haven’t changed any hardware, save upgrading the wireless NIC in May last year. Running
sfc /scannow with elevated privileges found nothing wrong. Restoring the system to the state prior to the latest updates made the network and firewall subsystems running again. All is well. What a mess.
The Office 365 instance installed on a student’s laptop showed signs of not being activated and in need of an update. Clicking on any of the small buttons below the ribbon made no difference. Running Office updates manually from “File → Account → Update” gave us an error message: 30125-28 (404).
sfc /scannow with elevated rights managed to repair enough of the corruption to allow Office 365 to continue working.
Why are modern “cloud” software so fragile? Why are Dropbox and Google Drive far superior to the equivalent of Microsoft? Why is OneDrive for Business more on the order of OneDrive from Hell?
Yesterday, a student installed Autodesk Revit 2018 on his Windows 10 x64 laptop. He then upgraded to Revit 2018.1. After entering the licensing details, Revit crashed. Installing the latest drivers from nVidia, currently at version 385.41, and rebooting the laptop saved us from any more grief.
I’ve been exploring Pässler PRTG on Microsoft Windows Server 2016 (Microsoft Imagine Premium) for the past couple of days. While the system is impressive and on the border of being overwhelming, it lacks complete IPv6 support.
The web interface is IPv4 only, and the NetFlow v9 collector only understands IPv4. PRTG can do PING, SNMP, etc, over IPv6, but you can only specify whether PRTG should contact a device using IPv4 or IPv6, not both. For as long as our networks remain dual-stack it makes sense to explore both network protocols simultaneously, in the same manner we can do with Icinga and Nagios, i.e. specify IPv4 and IPv6 addresses where applicable. A workaround is to register a device twice, once for IPv4 and again for IPv6. Be careful not to create too many duplicate sensors.
I wish PRTG would ask me if I wanted to run autodiscovery after installing it. PRTG detected our core switch as the DHCP (relay) service, duplicating all the sensors it could find.
Neither SNMP nor PRTG are ZFS aware, and in many cases it’s utterly pointless to monitor a lot of ZFS filesystems. Instead we should monitor ZFS pools, if only that were possible.
SNMP doesn’t convey whether a filesystem is diskbased or not, so I had to remove sensors for mountpoints such as
Updates to Trend Micro OfficeScan last week resulted in four cases of
Reboot to safe mode, uninstall Trend Micro OfficeScan, reboot, and reinstall Trend Micro OfficeScan.
One additional positive outcome was the firmware update we conducted simultaneously.
… Windows machines try to request two URLs (www.msftncsi.com/ncsi.txt and ipv6.msftncsi.com/ncsi.txt, the former over IPv4, the latter over IPv6) to ascertain whether a given network is routed to the Internet and if there is a captive portal in the way (NCSI stands for “Network Connection Status Indicator”).
See also: https://blogs.technet.microsoft.com/networking/2012/12/20/the-network-connection-status-icon/.
Et virus definerer jeg som et uønsket program som installerer seg uten mitt samtykke, sender data til en fjern server, har uønskede funksjoner, og er vanskelig å bli kvitt. Altså det samme som Windows 10.