Windows Update failed with error code 0x80004005

Since weeks one windows machine wasn’t able to install the latest “Monthly Rollups”, but other updates work. After reboot the installer starts until 86% and undone the update. Internet search did not bring much, except some users with an alternative bootloader who have the same problem. But this machine has no other bootloader. The Windows Update log did not have any helpful details, which also makes sense since it had to give for the installation of the update its own log. I remembered the SBC.log, which I used in another problem and what should I say … there was the error code 80004005 – with helpfull details.

It was not possible to write parts of the bootloader. I assign a drive letter to \HarddiskVolume1 with diskpart and i see the problem. The drive was out of space. Only 12Kb free, but lots of garbage. The drive is also used for Recovery (WinRE). Then I recognized the cause. The disk was cloned from a HDD to a SSD with lower capacity. After resize the HarddiskVolume1 to original size, the update works without any problem.

Bugzilla checksetup.pl stops with segmentation fault

After upgrading an openSUSE machine, the Bugzilla installation no longer works. Each run of the checksetup.pl crashes with “segmentation fault”. After updating perl with cpan and some research the solution for the problem was very simple:

  1. Rename the lib folder in the Bugzilla directory
  2. Run ./install-modules –all
  3. Run ./checksetup.pl again

Hardlink, Symlink and Junctions

To create a softlink, which should work through a network share, a junction should be created with mklink:

Remove VMware VIBs/VIB conflict

FDTI USB-to-Serial adapter showing only gibberish

I order two new – cheap – FTDI FT232RL USB-to-Serial Adapters on AliExpress.

IMG_7764

After connecting, the first disappointment came directly. The Windows Device Manager displayed no COM port. Only a USB Serial Converter. The update of the driver brought no improvement. By coincidence I discovered the “Load VCP option. After I activated this, the USB Serial Interface was displayed correctly.

2016-09-04 16_49_23-Eigenschaften von USB Serial Converter

Quickly the next disappointment came, both showing only gibberish.

I thought at first that the baud rate is incorrect, but with an older adapter it working correctly. On the FTDI website i found a tool called “FT_Prog”. With these programming utility you can read and write the EEPROM for use with FTDI devices. After a few clicks I could see the difference:

2016-09-04 16_24_14-FTDI - FT Prog - Device_ 0 [Loc ID_0x212]

2016-09-04 16_28_39-FTDI - FT Prog - Device_ 0 [Loc ID_0x212]

Since I was not sure if there are other differences, I used the template function of the tool to copy the settings.

2016-09-04 16_37_31-FTDI - FT Prog - Device_ 0 [Loc ID_0x212]

2016-09-04 16_38_10-FTDI - FT Prog - Device_ 0 [Loc ID_0x212]

2016-09-04 16_38_39-Program Devices

Allow Remote Desktop login with saved credentials

When trying to use saved credentials in Remote Desktop Connection you might receive this message:

Your credentials did not work. Your system administrator does not allow the use of saved credentials to log on to the remote computer because its identity is not fully verified. Please enter new credentials.

To be able to use saved credentials in this situation you need to do the following:

  1. Open Group Policy Editor (gpedit.msc)
  2. Navigate to Local Computer Policy\Computer Configuration\Administrative Templates\System\Credentials Delegation\
  3. Open Setting Allow Delegating Saved Credentials with NTLM-only Server Authentication, set it to Enabled click on button Show… and in Show Contents window add Value TERMSRV/*
  4. Run gpupdate command to update your policy.

Now you should be able to use your saved credentials.

Add password to .p12/.pfx-certificate

With following procedure you can change your password on an .p12/.pfx certificate using openssl.

Export you current certificate to a passwordless pem type:

Convert the passwordless pem to a new pfx file with password:

Now you are done and can use the new mycert2.pfx file with your new password.

Bugzilla: Add user to all components CC list of a product