File C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1639

Sometimes error are not exactly what they seem

Error 1639: Windows Installer Error 1639: 'Invalid command line argument' during installation

is seen in your ccmsetup.log file or the client.msi.log file similar to this:

clent.msi.log

MSI (s) (D0:A4) [09:48:51:623]: PROPERTY CHANGE: Modifying SMSCACHEDIR property. Its current value is 'Default'. Its new value: 'D:\CorpCache" CCMHTTPSSTATE='.

ccmsetup.log

Running installation package
  Package:     C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
  Log:         C:\Windows\ccmsetup\Logs\client.msi.log
  Properties:   REINSTALL=ALL REINSTALLMODE=vmous  SMSSITECODE="ABC" DNSSUFFIX="foo.com" CCMHTTPPORT="80" CCMHTTPSPORT="81" SMSCACHESIZE="20000" SMSCACHEDIR="D:\CorpCache"" CCMHTTPSSTATE="480" CCMFIRSTCERT="1"

File C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1639
Action:

Solution:

Turned out the machine was seeing an extra " or space. 
I re-arranged the setup command and placed "" around the values, it installed correctly

Always check your install package or command line when running the full commnad line with parameters.

Could not access network location %APPDATA%

Installing the SCCM 2012 client can be a daunting task when errors occur.  Here one such error can be seen:

MSI: Action 12:51:08: CostFinalize. Computing space requirements
MSI: Could not access network location %APPDATA%\.
MSI: Could not access network location %APPDATA%\.
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1603
Action: CostFinalize.
I have seen this error only once on a new machine.  I have seen it several times on a machine that was upgraded from SCCM 2007 to SCCM 2012 and then reveted back to SCCM 2007.  This error occurs shortly after the install process to once again move it to SCCM 2012.

I don't know if the state of the machine was already damaged but you will see the Security regisitry look something like this:

In order to fix this problem you need to fix the AppData folder setting seen here in a working machine:

In some cases the damaged registry is missing many of the enviromental variables and it is necessary to recreate or fix all of them.  The registry in question is the s-1-5-18 account SID:
SECURITY_LOCAL_SYSTEM_RID

A special account used by the operating system. 

Failed to Add Update Source for WUAgent of type (2) and id ({GUID}). Error = 0x80004005.

There are many reasons why WU will not work correct with the SCCM Agent.
Various fixes:

1. Run Windows Update and let the update fix the machine
2. Stop the Update Agent Service, Delete the Software Distribution folder and restart the service.

Here is yet another way:

WUAHandler.log:
Unable to find or read WUA Managed server policy.
Unable to read existing WUA Group Policy object. Error = 0x80004005.
Failed to Add Update Source for WUAgent of type (2) and id ({GUID}). Error = 0x80004005.

UpdatesHandler.oog:
Updates scan completion received, result = 0x80004005.

Try this:

C:\Windows\System32\GroupPolicy\Machine
Rename the Registry.pol file

Then re-run the Software Updates Scan Cycle in the Configmgr Actions tab.

then watch the logs:

WUAHandler.log:
Waiting for 2 mins for Group Policy to notify of WUA policy change...
Added Update Source ({GUID}) of content type: 2
Async searching of updates using WUAgent started.