AppV Client error 0600000011

A user encountered an AppV Client error 0600000011, with the Powershell cmdlet “Get-AppvClientpackages”.

(I used the “-all” property, because my admin user didn’t had the application published)

AppV Client error 0600000011

AppV Client error 0600000011

The AppV log shows all required information: Failed to load a manifest document from one particular package.

AppV failed to load manifest document

AppV failed to load manifest document

This package had two package-versions. If we browse the AppV cache and goto the package with Package GUID eadb7b20-d9d9-4e5f-b568-8312a090d9f8 we see two versions. But deleting the package with the well known pipe command wasn’t possible.

AppV cache shows two versions of one packge

AppV cache shows two versions of one packge

Removing with “Get-AppvClientPackage | Remove-AppvClientPackage” doesn’t work out because the Get-AppvClientPackage throws the error 0600000011. Using Remove-AppvClientPackage with the appropriate package and version GUIDs however does the job.

AppV delete packages from cache

AppV delete packages from cache

After deleting the faulty packages from cache, do a Sync-Publishing server and you’re back in business.


AppV 5 Package convertor

Because I cannot remember the AppV Sequencer PowerShell commands to convert a Softgrid (App-V 4.6 .sft) package to a App-V 5.x package (.appv). I dedicated to write it down at last, freed some memory for playing Commander Keen without using QEMM or whatever some cool memory management tool.

First import the cmdlet;

Import-Module AppVPkgConverter

Do the converthingy:

ConvertFrom-AppvLegacyPackage -SourcePath “C:\temp\v4_pkg” -DestinationPath “C:\temp\new_v5_pkg”

Btw Better use the 5.1 Sequencer or newer, because the AppVPkgConverter was updated in the 5.1 release. Also don’t try to convert older Softgrid 4.1/4.2/4.5 packages. First convert them to the 4.6 format using the App-V 4.6 Sequencer.

App-V 5 Inside the bubble (AKA break into the Virtual Environment)

As App-V grows up, this old post “Softgrid/App-V: Inside the bubble” became outdated. With App-V 5.x we have Powershell to break into the bubble.

Launch a cmd.exe processes inside the App-V 5 virtualized environment:

$AppVName = Get-AppvClientPackage <Package>
Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe

Or as a oneliner:

Start-AppvVirtualProcess -AppvClientObject (Get-AppvClientPackage “<AppVApplicationName>”) cmd.exe

Change “cmd.exe” to your needs, and of course change AppVApplicationName to the application name you would break into..

Another approach is the /appvve switch:


Or using a virtual process id:

cmd.exe /appvpid:8108



Clear the App-V 5.0 cache

Clearing the App-V cache is a common task for IT Pro’s, helpdesk have it in there toolbox. Back in the App-V 4.x days clearing the Softgrid cache could be done with sftmime.exe, the registry and some old fashion batch scripting,  but things are different now in App-V 5 Powershell land.

Remove all packages from disk (AKA machine cache)

First remove all connection groups, because packages that are a member of any connection group couldn’t be removed:

Get-AppvClientConnectionGroup -All | Remove-AppvClientConnectionGroup

After that, remove all App-V 5 apps from the cache:

Get-AppvClientPackage -All | Remove-AppvClientPackage

Clear application settings (AKA user cache/user state)

Using the packageName:

Repair-AppvClientPackage <packageName>

Using the packageGUID and versionGUID:

Repair-AppvClientPackage -PackageId <packageGUID> -VersionId <versionGUID>

Pipe things (usefull in scripts or to target multiple applications using a wildcard):

Get-AppvClientPackage -PackageId <packageGUID> -VersionId <versionGUID> | Repair-AppvClientPackage

More on the Repair-AppvClientPackage cmdlet on Technet.

0x80240037 Windows Update woes

After installing a Windows 7 x64 Sequence machine, I wanted to apply all patches via Windows Update.

But, Computer says noooo:

0x80240037 Microsoft Update kan niet op de computer worden geïnstalleerd

In English:

0x80240037 Microsoft Update cannot be installed on this computer.

For the record: I was logged in with an administrator account.

Solution: Remove the NoAutoUpdate key in HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Windows Update: NoAutoUpdate regkey

Windows Update: NoAutoUpdate regkey

The app manager could not create an application from 44-00001007

After sequencing an application using App-V 4.x, the client refuses to get the virtual app.

The sftlog.txt says:

The app manager could not create an application from ‘\\servername\contentshare\appname\osd filename.osd’ (rc xxxxxx45-00000107).

Most of the time this error is about the OS VALUE-tag in the OSD-file. I only had the Win764 value. As I’m only using a Windows 7 x64 client machine there is no problem to use this value.

Because I was out of possibilities to troubleshoot this issue, I removed this OS VALUE from my OSD file. After an AppV server refresh my sftlog.txt gives more info then before!

The client has encountered an XML parsing problem. The error code is 0xC00CE508. Reason: An invalid character was found in text content.

Source Text:   Blah blah blah, (near line 35, character position 156).

AHA, I got the bastard!

I’m using the ABSTRACT-tag as a placeholder for some sequencing/packaging info. Apparently some unsupported character sneaked in!

The previous error message says enough, but opening the OSD file in Internet Explorer can give more information about the XML syntax.

After removing some brackets and colons from the ABSTRACT-tag, the client was able to load my sequenced application!

Error 1153 Got a packet bigger than ‘max_allowed_packet’ bytes when importing into the database

After importing a .sql dump file using PhpMyAdmin into a MySQL database I got this error:

#1153 – Got a packet bigger than ‘max_allowed_packet’ bytes

Solved by changing “max_allowed_packet” to 10MB in the MySQL config file my.ini (on the target database only).


max_allowed_packet = 1M

Changed to:

max_allowed_packet = 10M


Missing App-V Management Console snap-in (MMC)

I like to have all my admin management tools grouped in one MMC Console (ADUC, ConfigMgr ..). But the Application Virtualization Management Console wasn’t listed in the available snap-ins. Although this was never a big issue to me, but couldn’t handle it anymore 🙂

Missing App-V Management Console Snap-in


The AppV Management Console Snap-in was listed on my AppV Server. After reading this blog post on the AppV Blog, I exported this registry key:


AppV Missing Snapin export regkey

And imported it on my workstation .. but no luck, no App Virt Management Console in the Available Snap-ins list.

After digging arround I found out that it’s possible to launch MMC.EXE in a 32bit environment.

mmc.exe /32

AppV Missing Snapin MMC 32bit

Now I’m able to use the AppV Management Console into my own custom console.

AppV Management Console Snap-in available again

Sync a redirected My Document folder with SkyDrive

I used this workaround before to sync My Documents folder with Dropbox. But apparently SkyDrive didn’t synced the symbolic link.

Mklink with the /j parameter works with local paths and drives, but I’m using redirected folders for “My Documents” (UNC path). So I needed to use mklink with the /d option. Creating the symbilic link wasn’t a problem, but SkyDrive wouldn’t sync it.

  • Close the SkyDrive application
  • Create a symbolic link with mklink:

Syntax: mklink /d “%userprofile%\SkyDrive\folderYouJustCreated” \\server\share$\profileName\documentsFolder

for example: mklink /d “%userprofile%\SkyDrive\Documents” “\\anatool\home$\devribe\My Documents”


  • Launch the SkyDrive application again, syncing will begin.