Solved – Windows Update error code 80092004 with kb4535102

Hello everyone, one of my server are having problem with windows update. This server still using windows server 2008r2. And when I try to install kb4535102 it will always show up error code 80092004.

After try to do some troubleshoot and googling from the error code, I found that I need to install missing kb that makes the error code.

The missing kb for this error are kb4490628, after install the kb4490628 manually and then I can install the kb4535102 without any error.

I hope anybody who read this article will solved the problem with same workaround.

source :

  1. here and
  2. here

Windows Update kb 4575903 Error Code – 80243004

i found error when i’m doing the update for server 2008r2.

Even this server already not supported by Microsoft our organization still using it.

when i try to install the windows update kb 4575903, I got the error like below

error code 80243004

and the problem solved with using below workarround.

  1. Right Click the taskbar and click properties
  2. Click on Costumize
  3. On the Notification Area Icons window, make sure Always show all icons and notifications on the taskbar is checked and click OK.
  4. and then click OK
  5. After doing that step, please try again to install the windows update.

hope it help someone who read this.

Source : Link

Solved – Windows Server 2008 R2 Update fails due to system-protected font – Tahomabd.ttf- KB4338818 or KB4343900

Hello,

this problem has been consume my time for almost 1 month.

i have been trying to install kb 4343900 for many times on my windows server 2008 r2, but it always failed.
The server was virtual machine on VMware.
What i already do is :
– running the sfc /scannow but it looks normal no integrity violation found
– try install the kb manually but still failed.
– running the SFCFix but still not working

– reset the windows update component.

windows update log :

2018-08-23 16:20:46:999 868 b4c Handler Post-reboot status for package Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24214.1.5: 0x80070020.
2018-08-23 16:20:46:999 868 b4c Handler WARNING: Got extended error: “POQ Operation HardLinkFile OperationData \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.1.7601.24145_none_8e5c4f96a47869ce\tahomabd.ttf, \??\C:\Windows\fonts\tahomabd.ttf”

after several troubleshoot workaround, i found that the tahomabd.ttf are lock the windows update process , and here are the workaround to solved it :

1) Use Process Explorer (Process Explorer – Windows Sysinternals | Microsoft Docs) to search for handles currently using “tahoma” or “staticcache.dat”. Please run this tools as administrator.
2) Temporarily disable or uninstall the above handles (programs/processes) that are using “tahoma” or “staticcache.dat” (for my case, manage engine service desk lock the tahoma font. Disable the manage engine services before install the KB).

3) Install KB4343900.

4) restart the server

5) Update Success, Re-enable manage engine services.

 

Source :

Source 1

Source 2 – my thread on www.sysnative.com

Solved – iscsi shared folder not shared after the server restart

I have a synology unit which I connected via iSCSI on windows server 2008r2,  the weird thing that every time I reboot, the shared folder would disappeared, and I would have to re-share again.

after read some article on the microsoft on this link , i solved the problem.

the things that i do is :

  1. Click Start, click Run, type cmd, and then press ENTER.
  2. Type sc config LanManServer depend= Samss/Srv/MSiSCSI, and then press ENTER.

    If you have administrative access to the server, you can perform this command from a network computer. To do this, type the following command, and then press ENTER:

    sc \\computer_name config LanManServer depend= Samss/Srv/MSiSCSI

Solved – windows time service not starting automatically on work-group environment

i found the problem that show up the windows time services not running when using workgroup environment.

and for the solution, please use this workaround.

Method 1

Run the following command to delete the trigger event that’s registered as the default setting and to change the Startup Type setting for the Windows Time service from Manual to Automatic:

sc triggerinfo w32time delete

Method 2

Run the following command to define a trigger event that suits your environment. In this example, the command determines whether an IP address is given to a host, and then it starts or stops the service.

sc triggerinfo w32time start/networkon stop/networkoff

w32time

Method 3

Change the Startup Type of the Windows Time service from Manual to Automatic (Delayed Start).

Note If the Startup Type of the Windows Time service is set to Automatic (Delayed Start), the Windows Time service may be started by the “Time Synchronization before the Service Control Manager starts the Windows Time service” task. (This depends on the startup timing of the Windows operating system in question.)

In this situation, the service triggers an automatic stop after the success of the Time Synchronization task. Therefore, if you use Method 3, you must disable the “Time Synchronization to avoid the task to start the Windows Time service” task. To do this, follow these steps:
Start the Task Scheduler.
Under Task Scheduler Library / Microsoft / Windows / Time Synchronization, click Synchronize Time.
Right-click, and then click Disabled on the shortcut menu.

 

source