Author: Nico Maas

Windows 10 Update Error 0x80070001

I had two Windows 10 machines which had stopped pulling upgrades from Microsoft for quite long (1703, anyone?) and I could not get it back working.
Windows Update just showed me the error 0x80070001 and did refuse to do anything.

Tried:
- Clearing Windows Update Cache
- WSUS Offline Patching (installed the updates, but the normal Windows Update did not start working after that...)
- Windows Update Repair Tool from Microsoft

Nothing did really work, until I stumbled upon a post by OksiQuatzel:
Culprit was the installed ImDisk, a virtual Floppy Drive. With this installed and an A Drive mounted - this error arose.
As soon as I unmounted the drive and removed the driver - everything started working again.
Kind of nuts that something like this could occur.

Actually I tried it with ImDisk, Virtual Floppy Drive 2.1 and other Virtual Floppy Drives and RAMdisk drives - there is a high chance that - if you use such a program, the Windows 10 Update does cease function...

Source in german

BeagleLogic

To get your Beaglebone Black (BBB) to work as an Logic Analyzer, you can use BeagleLogic:

1.) Download latest version of BeagleLogic
from: https://beaglelogic.readthedocs.io/en/latest/beaglelogic_system_image.html
Released on 2017-07-13, sha256sum = be67e3b8a21c054cd6dcae7c50e9e518492d5d1ddaa83619878afeffe59c99bd
https://goo.gl/RiXGBs

2.) Burn it onto sdcard with Etcher

3.) Put SDCard into BeagleBone Black

4.) Hold "Boot" Button, plug in BBB with Mini USB Cable to your PC

5.) After 10 seconds or so, release "Boot" Button (this will just boot from SDcard with this trick)

6.) Wait some time and login to 192.168.7.2 via SSH
Username: debian
password: temppwd

7.) Test if BeagleLogic works
ls -l /dev/beaglelogic
There should be entry /dev/beaglelogic as answer, if not check the BeagleLogic Website

8.) Change uEnv.txt
sudo vi /boot/uEnv.txt
#go to following lines:
##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

remove # from #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

#save and exit

9.) Shutdown
sudo shutdown now

10.) Boot again, this time with flasher
Hold "Boot" Button, plug in BBB with Mini USB Cable to your PC, after 10 seconds, release the button.
During the flash process of the eMMC, the 4 leds will make a "Knight Rider" like lightshow.
This will take some minutes. The BBB will shutdown afterwards (all LEDs off).

11.) Remove SDCard, replug Mini USB and boot without holding any buttons

12.) Wait some time and login to 192.168.7.2 via SSH
Username: debian
password: temppwd

13.) Open your webbrowser and go to: http://192.168.7.2:4000/#

Next:
- Upgrade
- this enables you to also use the BeagleLogic as "external analyzer" and control it from i.e. a Window System running a special version of pulseview 🙂
- More infos: https://goo.gl/L9QUrt
Connect to Ethernet / Internet
cd /opt/BeagleLogic/
git config http.sslVerify false
git pull
sudo apt update
sudo ./install.sh --upgrade
sudo reboot now

Useful infos:
https://beagleboard.org/getting-started#update
http://beagleboard.org/latest-images
https://beaglelogic.readthedocs.io/en/latest/beaglelogic_system_image.html
https://beaglelogic.readthedocs.io/en/latest/install.html

Cannot start Virtual Machine on ESXi 6.5

As described by JC-LAN, I had a lot of trouble with one particular "special" VMDK on a ESXi 6.5 system, which did not start after a reboot of the ESXi host.

The power-on failed with "File system specific implementation of LookupAndOpen[...] failed" - however in the end it just gave me the overall error that it failed to start the machine. As it turned out, the VMDK was corrupted.

1.) Enable SSH on the ESXi host with the corrupted VMDK - and login

2.) Check the main VMDK (not with the name -s####.vmdk, the main file!) with

vmkfstools -x check /absolute/path/vm.vmdk

3.) It will probably report that the fail is defective. Repair with

vmkfstools -x repair /absolute/path/vm.vmdk

4.) Now you can try to start the VM again, helped me already 3 times 🙂

Taken from: https://jc-lan.tk/2017/02/01/esxi-6-5-host-crash-then-guest-fails-to-power-on/

How to delete Hyper-V Virtual Networkcards in Windows 10

As a "Edge" Version user of Docker for Windows, I tend to reinstall Docker from time to time, just to get a clean base. However, Hyper-V digs quite deep into the system and creates its own virtual network interfaces, which you just can't delete from the Hyper-V Manager.

Best option is to use (READ ALL BEFORE COPY AND PASTE, PLEASE!):

netcfg -d

in a Administrator CMD window.

This does only delete virtual network devices - HOWEVER, it does delete devices like i.e. your OpenVPN interface AS WELL - AND does DELETE ALL SETTINGS of other network interfaces, i.e. your IP configuration or all your saved WIFI credentials.

So use with care!

Taken from: https://serverfault.com/questions/584316/how-to-delete-hyper-v-virtual-switch-extensions-adapters-from-device-manager