Windows Update Troubleshooting

Found this post after running into this error (8024401C) following error 0x80244007 which I received after scanning for Windows Updates.

after attempting to check for Windows updates on a Windows 2012R2 system and it helped me solve my issue. Thanks to the original poster.

The following outlines how to stop services pertaining to Windows Update, rename system folders, register related DLL files, and then restart the previously mentioned services. This troubleshooting generally applies to all Windows Update related issues.

 Stopping services pertaining to Windows Update

1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
2. If you receive a notification from User Account Control simply click Continue.
3. At the command prompt, type the following, commands and then press ENTER after each command.
1. net stop wuauserv
2. net stop bits
3. net stop cryptsvc
   Please do not close the Command Prompt window.
4. Renaming folders pertaining to Windows Update
5. At the command prompt, type the following commands, and then press Enter after each command:
6. ren %systemroot%\System32\Catroot2 Catroot2.old
7. ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   
   Please do not close the Command Prompt window.

Registering DLL’s pertaining to Windows Update

• Please copy and paste the following text into a new Notepad document, and save the file as WindowsUpdate.BAT
  If saved correctly the icon will change from a Notepad file to BAT file which has two blue cogs as its icon.

            -OR-

• You can manually type each command at the command prompt:

regsvr32 c:\windows\system32\vbscript.dll /s

regsvr32 c:\windows\system32\mshtml.dll /s

regsvr32 c:\windows\system32\msjava.dll /s

regsvr32 c:\windows\system32\jscript.dll /s

regsvr32 c:\windows\system32\msxml.dll /s

regsvr32 c:\windows\system32\actxprxy.dll /s

regsvr32 c:\windows\system32\shdocvw.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups2.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 Softpub.dll /s

regsvr32 Mssip32.dll /s

regsvr32 Initpki.dll /s

regsvr32 softpub.dll /s

regsvr32 wintrust.dll /s

regsvr32 initpki.dll /s

regsvr32 dssenh.dll /s

regsvr32 rsaenh.dll /s

regsvr32 gpkcsp.dll /s

regsvr32 sccbase.dll /s

regsvr32 slbcsp.dll /s

regsvr32 cryptdlg.dll /s

regsvr32 Urlmon.dll /s

regsvr32 Shdocvw.dll /s

regsvr32 Msjava.dll /s

regsvr32 Actxprxy.dll /s

regsvr32 Oleaut32.dll /s

regsvr32 Mshtml.dll /s

regsvr32 msxml.dll /s

regsvr32 msxml2.dll /s

regsvr32 msxml3.dll /s

regsvr32 Browseui.dll /s

regsvr32 shell32.dll /s

regsvr32 wuapi.dll /s

regsvr32 wuaueng.dll /s

regsvr32 wuaueng1.dll /s

regsvr32 wucltui.dll /s

regsvr32 wups.dll /s

regsvr32 wuweb.dll /s

regsvr32 jscript.dll /s

regsvr32 atl.dll /s

regsvr32 Mssip32.dll /s

• Restarting services pertaining to Windows Update

1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
2. If you receive a notification from User Account Control simply click Continue.
3. At the command prompt, type the following, commands and then press ENTER after each command.
1. net start wuauserv
2. net start bits
3. net start cryptsvc

      Type <exit> to leave the command prompt

You might want to try a clean boot once you're done with the above, then check for updates once your system is back up. Rebooting was what I had to do in my case.

• Now please check for updates using Windows Update to see if the issue has been resolved.

Original Post:
https://answers.microsoft.com/en-us/windows/forum/all/access-denied-on-open-commands/2d31ce25-46a7-4ba0-838d-5b842e9991fa

Read More

PowerShell Solution for the trust relationship between this workstation and the primary domain failed

This is one possible solution for the error of 

trust relationship between this workstation and the primary domain failed

Note the solution will be using powershell run as an admin.

First you need to get an idea of when the user computer/workstation domain password was last synchronized. So I ran the following Powershell command:

get-adcomputer -Identity ProblematicComputerName -Properties PasswordLastSet

Which should give you a result like the following. Note the the only entry we care about is the PasswordLastSet field shown in the redbox here:

 

Next step is to reset that machine account password as a domain admin to fix that trust relationship without having to disjoin and rejoin the domain.

This is accomplished by running the following PowerShell command on the affected machine. Note that you have to run Powershell as admin here as well:

Reset-ComputerMachinePassword -Server dc1.your.domain.com -Credential domain\adminusr

Once you click or hit your Enter key to execute the command, you should get a prompt to enter your admin password. So fill-in your domain admin password and click OK.

Assuming all was done correctly, you should be returned to your PowerShell prompt.

So now you need to re-run your the first command to see the result of your command. So wait a minute for the command to synch across your DCs (assuming you have more than one DC) and re-run the command:

get-adcomputer -Identity ProblematicComputerName -Properties PasswordLastSet

and you should get an updated PasswordlastSet field value:

PowerShell Command reference:

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/reset-computermachinepassword?view=powershell-5.1&viewFallbackFrom=powershell-3.0

Read More

Find O.S Install - Deployment Date

Commands to find out the initial deployment or installation of your operating systems.

Linux Systems:

tune2fs -l /dev/sda1 | grep 'Filesystem created:'

OR

tune2fs -l /dev/sdb1* | grep 'Filesystem created:'

Windows Systems:

systeminfo|find /i "original"

Read More

Skip Client For NFS username mapping - Win 2008 R2

This was found during my trouble trying to figure out why MS Windows 2008 R2 was mounting an NFS share (From a Linux NFS server) as read only and the multiple hoops you need to jump through in order to configure username mappings etc...Then I found this solution and it works:

Force ClientForNFS to mount a share using a specific UID and GID, and without the need for a user name mapping server, add the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default

Add two DWORD values: AnonymousUid and AnonymousGid and set to your appropriate values in decimal.  For example: if your server has root user & group ownership/perms for its NFS shares, then you would leave the default value of zero "0" for those two DWORD entries.

Then restart the ClientForNFS service. (You may need to reboot the server.)

Read More

Useful Windows tool of the day

I needed to grep - Linux style - for a string piped out of windows command line output, so, I started looking for something native to windows that would achieve that for me.

I can't remember if I've just forgotten about this command or if I just didn't know that the Findstr command that's built into windows existed. Anyway, it did what I needed.

Here is the FindStr command link on TechNet with all its switches and the meta-characters it accepts for regular expressions.
http://technet.microsoft.com/en-us/library/bb490907.aspx

So now I can use the findstr command to receive the output from another command and grab the string I'm looking for.

Example use: set | findstr JAVA
This grabs the string JAVA out of the windows environment variables if it's set. In my case, that output would be: JAVA_HOME=D:\Java\jdk1.6.0_39

--------------

Findstr

Searches for patterns of text in files using regular expressions.

Syntax:
findstr [/b] [/e] [/l] [/r] [/s] [/i] [/x] [/v] [/n] [/m] [/o] [/p] [/offline] [/g:file] [/f:file] [/c:string] [/d:dirlist] [/a:ColorAttribute] [strings] [[Drive:][Path] FileName [...]]

Parameters

/b   : Matches the pattern if at the beginning of a line.

/e   : Matches the pattern if at the end of a line.

/l   : Uses search strings literally.

/r   : Uses search strings as regular expressions. Findstr interprets all metacharacters as regular expressions unless you use /l.

/s   : Searches for matching files in the current directory and all subdirectories.

/i   : Specifies that the search is not to be case-sensitive.

/x   : Prints lines that match exactly.

/v   : Prints only lines that do not contain a match.

/n   : Prints the line number before each line that matches.

/m   : Prints only the file name if a file contains a match.

/o   : Prints seek offset before each matching line.

/p   : Skips files with non-printable characters.

/offline   : Processes files with offline attribute set.

/f: file   : Reads file list from the specified file.

/c: string   : Uses specified text as a literal search string.

/g: file   : Gets search strings from the specified file.

/d: dirlist   : Searches a comma-delimited list of directories.

/a: ColorAttribute   : Specifies color attributes with two hexadecimal digits.

strings   : Specified text to be searched for in FileName.

[ Drive : ][ Path ] FileName [...] : Specifies a file or files to search.

/?   : Displays help at the command prompt.

Using regular expressions with findstr 

Findstr is capable of finding the exact text you are looking for in any ASCII file or files. However, sometimes you have only part of the information that you want to match, or you want to find a wider range of information. In such cases, findstr has the powerful capability to search for patterns of text using regular expressions.

Regular expressions are a notation for specifying patterns of text, as opposed to exact strings of characters. The notation uses literal characters and metacharacters. Every character that does not have special meaning in the regular expression syntax is a literal character and matches an occurrence of that character. For example, letters and numbers are literal characters. A metacharacter is a symbol with special meaning (an operator or delimiter) in the regular-expression syntax.

The following table lists the metacharacters that findstr accepts.

Character	Value
.	Wildcard: any character
*	Repeat: zero or more occurrences of previous character or class
^	Line position: beginning of line
$	Line position: end of line
[class]	Character class: any one character in set
[^class]	Inverse class: any one character not in set
[x-y]	Range: any characters within the specified range
\x	Escape: literal use of metacharacter x
\<xyz	Word position: beginning of word
xyz\>	Word position: end of word

The special characters in regular expression syntax are most powerful when you use them together. For example, the following combination of the wildcard character (.) and repeat (*) character match any string of characters:

.*

Use the following expression as part of a larger expression that matches any string beginning with "b" and ending with "ing":

b.*ing

http://technet.microsoft.com/en-us/library/bb490907.aspx

Read More

aspnet_regiis is missing from Framework64 & Framework folders for .NET v4.0.30319

Ran across this issue after installing the Microsoft .Net version 4 and tried to register asp.net version 4 with IIS 7.0 on Windows 2008 R2 64 but the executable "aspnet_regiis.exe" was not found in the newly created folder where it is supposed to be %WINDIR%\microsoft.net\Framework64\v4.0.30319\

The problem stemmed from wrong instructions directing the user to install .NET version 4 client Profile instead of the full .NET version 4 for server and development.

Once I installed the development version, all the missing files showed right up and was able to use aspnet_regiis just fine.

Current Location for the Dev standalone install files is here:

http://www.microsoft.com/en-us/download/details.aspx?id=17718

Read More

Chrome Popup: Your Profile Could Not Be Opened Correctly

I started experiencing this "Your Profile Could not be opened Correctly" message after the last Chrome update to version 20.0.1132.47

The only solution that worked for my particular setup was to delete the following two files (After making sure all Chrome Windows/tabs & processes are closed)

 “Web Data” and “Web Data-journal” files from the following location on my Windows7 machine:

 C:\Users\[Enter your username here]\AppData\Local\Google\Chrome\User Data\Default  

Although this solution was posted back in 2011, it still worked for my problem and resolved it without further tinkering.

Solution Source: http://akdora.wordpress.com/2011/11/03/solution-your-profile-could-not-be-opened-correctly-in-chrome/

P.S. I saw other solutions that suggested deleting your whole Chrome data folders & their contents. Make sure you backup your Chrome bookmarks and a list of your current extensions if you decide to go that route so you won't have to lose any of your stuff.

Read More

32Bit ODBC driver on Windows 2008 R2 64Bit OS Error

Problem: I received the following error message upon trying to create a system DSN using a 32Bit ODBC driver I had just installed on a Win2088 R2 64Bit Server (with SP1):

"You are logged on with non-Administrative privileges. System DSNs could not be created or modified"

Solution: Make sure to use the 32Bit ODBC console instead of the standard ODBC console located under Control Panel/Administrative Tools:

"C:\windows\sysWOW64\odbcad32.exe"

Read More

Delete stubborn Windows files

Found a nice (Freeware) tool called "Unlocker" for deleting/unlocking some stubborn files that a Windows 2008 machine just couldn't delete with its built-in tools.
It did the job without a hitch!

Read More

Fix Live Update Backupexec 2010

This fixes the issue of Symantec's Live update not recognizing that there are any products to be updated and throwing the following error message:

LU1805: LiveUpdate was unable to find any products to Update


Fix: Go to your Symantec's Backup Exec Program folder location and run the following executable:



BEUpdateOps.exe

You now should get a notification saying that Backup Exec was successfully registered with Live update and be able to run it to get any available updates.

Many thanks to the solution poster found here:
http://www.sudonym.com/233/unable-to-run-live-update-in-backup-exec-2010

Read More

Solution to "VBE6EXT.OLB could not be loaded." Error

I got a VBE6EXT.OLB could not be loaded error when I wanted to install this really great tool-set for Excel that I've been using for years form http://www.asap-utilities.com on my new machine which has MS Office 2010 installed.

So I found this solution posted on Solidworks forum after some Google digging:

Make sure the following items exist in your registry:

[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}]


[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}\5.3]
"PrimaryInteropAssemblyName"="Microsoft.Vbe.Interop, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
@="Microsoft Visual Basic for Applications Extensibility 5.3"


[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}\5.3\0]


[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}\5.3\0\win32]
@="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\VBA\\VBA6\\VBE6EXT.OLB"


[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}\5.3\FLAGS]
@="0"


[HKEY_CLASSES_ROOT\TypeLib\{0002E157-0000-0000-C000-000000000046}\5.3\HELPDIR]
@="[{0002E157-0000-0000-C000-000000000046}]"

Note: You could download & import the above registry keys into your registry as a .reg file from the original post below.

Source: https://forum.solidworks.com/thread/40593

undefined

Read More

MSI Installer error code 2230

Symptoms

When trying to install/uninstall a citrix hotfix, installing/uninstalling the server software or when adding or removing some components of the server software one may receive the following error:

Internal error 2203. c:\windows\installer\xxxxx.ipi, -2147024629

Resolution

Ensure the path of the administrator’s user variables in the system properties of the temp and tmp variables are as follows:

TEMP:%USERPROFILE%\Local Settings\Temp

TMP:%USERPROFILE%\Local Settings\Temp

Solution Source: http://support.citrix.com/article/CTX104619 

Read More