Posts Tagged ‘xp’

Windows XP: April 8th – Almost Here!

For the past couple of years, Microsoft has been advising customers of the planned end of extended support date for Windows XP. We’ve even been using a countdown clock on the Windows XP page ( ) In fact, you’ve probably also been made aware of or have seen first-hand the end of notifications that are now popping up on Windows XP machines. You may have also recently read this as well:

The update KB 2934207 (Information Here – also adds in a notification prompt (which some in the press have affectionately referred to it as the “Death Notice.”)

If you are not seeing this update, it is likely because your Windows XP machine is being managed by WSUS, or Configuration Manager, or through the cloud with Windows Intune. Only Windows XP machines (Windows XP Home and Professional editions) who receive updates via WindowsMicrosoft Update will see these notifications.

If for some reason you are receiving these notices and you would like to disable them, you can do so in the registry under the one of the following keys:




Set the value of DisableEOSNotification (DWORD) to 1 to disable notifications. ) enables it.

Regardless of this change, the fact remains that end of all support except for custom support agreements is still April 8, 2014. If you are still running Windows XP in *ANY* form (physical desktops, VDI, MED-V, etc.) this affects you. Without a CSA, you will receive no further security updates and you run a risk of being vulnerable after that date. Also bear in mind that if you are virtualizing Internet Explorer 6, 7, or 8 with any non-Microsoft application virtualization solution, you will be indirectly affected as well.

Consumers, and Small-to-Midsize customers looking to update, can receive special offers and discounts via out Get2Modern page here:

A Custom Support Agreement (CSA) requires a Premier Services Agreement with Microsoft. If you are current an enterprise customer with a Premier contract, we have been making some changes to the Windows XP Custom Support Standard Program, which provides critical security updates, technical assistance and continued support for the product after April 8th. Please contact your Technical Account Manager (TAM) for more information.

Please note. This applies to Windows XP and NOT Windows XP Embedded. Windows XP Embedded is a different operating system designed for specialized OEM embedded devices and it has always ran on a different support lifecycle ending in 2016, which has been in place for a while in spite of what you may have read in articles out there on the Internet.

Categories: Uncategorized Tags: , , , , , , ,

Here’s a Short Blog with a very Important Message (T-MINUS LESS THAN 6 MONTHS)

November 14, 2013 Leave a comment

Early last year I wrote a blog specifying how MED-V does NOT affect the Windows XP EOL Support issue: 

Little did I know how widely pulicized this would be (re: quoted in The Register and others –

Today’s a good reminder for all that we are now within six months. If you are looking to start a Windows XP migration please be advised that if the purpose of migration is to avoid unsupported or expensive custom extended support agreements, then MED-V will not resolve these concerns. Everything in that article is still valid. If you are still on XP, please feel free to comment on what your migration blockers are below. Are you being held back by a legacy LOB app or is it an Internet Explorer 6 issue?

Categories: Uncategorized Tags: , , , ,

How MED-V Affects Windows XP End-of-Life Support Policy (It Doesn’t.)

Lately, I have many customers who are in the process or quickly planning their migration from Windows XP to Windows 7. Some of them are even looking to become early adopters of Windows 8. In the process of inventorying, rationalizing, and providing application compatibility remediation for their legacy applications, the need for leveraging MED-V for last-resort application compatibility remediation has created questions with regards to Windows XP supportability and how MED-V may or may not affect that. For application issues such as 16-bit remediation for x64, MED-V is the only option for enterprise customers.
Given that the supported MED-V solutions (v1 and v2) and its scaled-back VPC counterpart Windows XP Mode leverage the use of a Windows XP operating system instance, the question is always posed to me – Does the Windows XP EOL policy also apply to MED-V? The question may also be asked slightly differently but more pointedly: Does MED-V extend the Windows XP EOL policy?

The short answer is: No MDOP solution extends or affects the Windows XP Lifecycle end-of-life date for support. That date is firm and will not change. April 8, 2014 – as per the reference here:

MED-V Version 1

MED-V Version 1 is technically still in support however, only MED-V V1 workspaces containing the Windows XP operating system are. Even though MED-V V1 did temporarily allow for the use of Windows 2000 workspaces on Windows 7 when released in 2009, it did not extend the support date for Windows 2000 instances beyond the end of 2010. Since mainstream support for MED-V v1 ends on August 10, 2013 (per there is no confusion as there is with MED-V V2 since MED-V V1 will already be out of support by the time 2014 arrives. If customers running MED-V V1 have not already started looking for alternative means of application remediation going forward for Windows 7 and/or Windows 8, the time to start thinking about that is now. Note: MED-V (any version) is not supported on Windows 8.

MED-V Version 2 and Virtual PC for Windows 7

MED-V version 2 will be supported until December 4, 2016 (per
What this means is the actual MED-V and VPC7 code will be supported beyond the Windows XP EOL date – but the Windows XP code will not be. In essence, the host machine’s software will be fully supported until that date but no security or critical updates will be released for the guest operating system (other than potentially code fixes for elements pertaining to the MED-V guest agent.) Remember, MED-V is designed to only serve as a temporary solution for remediation. The end game should be the modernization or replacement of the application(s) in question. Also take heed the same applies for Windows XP Mode.

So the big question . . .

Finally, the last question I am always asked is: What do you recommend our end game date for leveraging MED-V should be?

My honest answer has never wavered: April 8, 2014 – if not sooner.

App-V: App-V Client Issues Streaming from App-V/IIS Server using XP with IPV6

The App-V Client (running under Windows XP) may fail to stream from App-V Server (or IIS Server) when running IPV6. You may get an error similar to the following:

[08/18/2011 10:23:32:058 JGSW ERR] {tid=10CC:usr=steveth}
The Application Virtualization Client could not connect to stream URL ‘http://server/content/application/package.sft’ (rc 16D1100A-0000E005, original rc 16D1100A-0000E005).

[08/18/2011 10:23:32:058 PMGR ERR] {tid=10CC}
Failed to background load package {package} (rc 16D1100A-0000E005).

[08/18/2011 10:23:32:059 AMGR WRN] {tid=10CC}
Attempting Transport Connection
URL: http://server/content/application/package.sft
Error: 24604F0A-40002EE2

Windows XP supports DNS queries only over the IPv4 protocol, but will support IPv6 queries (such as PTR and AAAA) which is why name resolution will fail.  Unless the the WinXP client is dual-stacked with both IPv4 and IPV6, you may have issues with the App-V client and IPv6.

It is important to note that this problem is only found on clients running exclusively IPv6 on Windows XP clients only.


Categories: Uncategorized Tags: , , , , ,

App-V: This Stack is Full of Crazy . . .

June 2, 2011 3 comments

Scenario: A Computer (likely running Windows XP) with the App-V Client crashes with the

STOP: UNEXPECTED_KERNEL_MODE_TRAP Blue Screen (0x0000007F) during or immediately after installation of the App-V 4.6 client.

Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Unfortunately, this will likely happen during an installation or upgrade process. If it happens during an upgrade, it will result in a partially installed App-V state and no applications will be able to launch.

This may happen when one of the App-V file system drivers is conflicting with a driver used by the DeviceLock software. DeviceLock is a third-party application designed for Kiosks.

This can happen on any versions of DeviceLock earlier than 6.4.1.

The solution is to either remove DeviceLock or upgrade to a version compaitble with App-V 4.6 BEFORE installing the App-V 4.6 client.

NOTE: When you check out a dump caused by this issue one tell-tale sign will be the massive stack overflow so the stack trace will be full of crazy:

f6b80038 f6d35ccf 82691018 82667838 00000001 DeviceLockDriver0+0x2926f
f6b800e0 f6d36936 82691018 82667838 00000023 DeviceLockDriver0+0x1eccf
f6b800f4 f65d1ffa 82691018 82667838 82667838 DeviceLockDriver0+0x1f936
f6b80108 f6d363f8 82691018 82667838 f6b80234 Sftfsxp!SoftFSFsdClose+0x3a
f6b801a0 f6d36936 82691018 82667838 00000023 DeviceLockDriver0+0x1f3f8
f6b801b4 f65d1ffa 82691018 82667838 82667838 DeviceLockDriver0+0x1f936
f6b801c8 f6d363f8 82691018 82667838 f6b802f4 Sftfsxp!SoftFSFsdClose+0x3a
f6b80260 f6d36936 82691018 82667838 00000023 DeviceLockDriver0+0x1f3f8
f6b80274 f65d1ffa 82691018 82667838 82667838 DeviceLockDriver0+0x1f936
f6b80288 f6d363f8 82691018 82667838 f6b803b4 Sftfsxp!SoftFSFsdClose+0x3a
f6b80320 f6d36936 82691018 82667838 00000023 DeviceLockDriver0+0x1f3f8
f6b80334 f65d1ffa 82691018 82667838 82667838 DeviceLockDriver0+0x1f936
f6b80348 f6d363f8 82691018 82667838 f6b80474 Sftfsxp!SoftFSFsdClose+0x3a

Steve Thomas

Categories: App-V Tags: , , , , , ,

How to Make an MS-DOS Bootable Floppy Disk for Hyper-V or VPC

January 11, 2011 8 comments

If you are stuck trying to do this, you would be surprised at how quickly it can still be done. The Challenge is getting a boot sector – which you can override with a new set of MS-DOS files if require a specific version.

1.) Mount a Blank VFD

2.) Start a Windows XP VM.

3.) Attach a VFD to the XP VM after you have logged on to the XP VM.

4.) Right-click the floppy in the Windows XP Guest OS and select Format.

5.) Check the option to create an MS-DOS System Disk.

Post format you can do whatever you need to copy over the files on the disk if you need an older version such as MS-DOS 6.22. Overwrite files as needed as all you needed from step #5 was the creation of the boot sector.

Categories: Hyper-V, Virtualization, VPC Tags: , , , , , , ,

Random STOP (BSOD) crashes with Forefront Endpoint Protection and App-V 4.5

You may receive random STOP (BSOD) crashes with Forefront Endpoint Protection and App-V 4.5 and later. The frequency increases with Virtualized Outlook 2007.

The problem was caused indirectly by Forefront but Forefront is not entirely at fault here. If you have Forefront Endpoint Protection installed but do not exclude PSTs nor PKG files from Forefront real-time scanning, then you might run into this issue.

This is difficult to nail down due to the STOP Error. The STOP 0xDF bugcheck is referenced here:


Explanation:  This Stop message occurs when a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is seriously compromised and security can no longer be guaranteed. The operating system switches into kernel-mode and generates this error. Because Windows 2000 cannot run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can shut down the system. Running the kernel debugger is not useful in this situation because the actual error occurred in a user-mode process. Because this Stop message occurs in a user-mode process, the most common culprits are third-party applications. Other common causes of this message are the installation of a new or updated device driver, or system service. Mismatched system files can also cause this error. Running a full system restore from tape might generate this error, because( some restore programs might skip restoring system files they determine are in use).

With Windows XP, Forefront hooks in through GINA chaining and user mode hooking and so does App-V 4.5 and later. If PKG files are being scanned by Forefront and PSTs are going to them, this creates a nightmare scenario for functionality if PKGs and PSTs are not excluded from FCS.

PLEASE NOTE: This problem only occurs on Windows XP with FCS and App-V installed. It has only been reproduced with that configuration and the only application we could get to reproduce virtually was Outlook and that was with PSTs inside of PKG files (not recommended) or server-based PSTs (also not recommended.)

The only resolution for this is to ensure you create exclusions for PSTs and PKG files using Forefront. Please refer to this link for instructions on how to do this:

Categories: App-V Tags: , , , , , , , , , ,