When Launching an App-V Application, This Message is Shown “Cannot Start”.

On the VDA, open PowerShell as an Admin and verify that the application information is listed by running command:

Get-AppvClientPackage -All

The command output shows a failure, and the message “The Microsoft Application Virtualization Service may not have been started. Verify that the service is running.

That may indicate that App-V is not enabled on the VDA.

Run command Enable-App-V and restart Desktop service.

NOTE: If VDAs are not persistent, run the command in master image and update the catalog.

Related:

Update ShareConnect Desktop

User-added image

ShareConnect’s Desktop app lets you quickly connect to all of your computers from a Windows device. To make sure you have access to the latest features, this app is able to update automatically. Unfortunately an issue with a recent version of the desktop app (v5.0.1391) has prevented automatic upgrades from working properly for select users.

We want to make sure that you have access to the latest features and stability improvements for the app. You will need to install the latest version of the app manually.

Install the Desktop App Manually

1. Go to the computer where you have installed the ShareConnect Desktop App.

2. Navigate to https://shareconnect.com and log in to your account.

3. Click Download Desktop App in the sidebar.

User-added image

4. Click Get it Now to download the latest version of the App

  • Note: You do not need to uninstall the older version of the Desktop App first

5. Open the ShareConnectDesktopApp.exe download

User-added image

6. Click Install.

7. Follow the prompts to complete the installation.

Once you install the latest version, future upgrades will happen automatically. We apologize for the inconvenience and hope you enjoy the new improvements that are available in the Desktop app.

Related:

  • No Related Posts

App Layering/Unidesk: If user logs in before Office activation script runs, Office licensing will break

When an App Layering image boots (or a Unidesk desktop), there is a system startup script called kmssetup.cmd which performs Windows and Office licensing actions to ensure that the product is properly activated. In Windows 10 (and possibly other Windows versions), system startup scripts are delayed by a few minutes, meaning it’s possible for a user to login to the VM before the activation scripts have run. A user having logged in may experience licensing anomalies until our script has run. They will definitely interfere with Office licensing in a way which causes the licenses to not appear at all, and cause Office to have to do an installation repair on its own.

Unfortunately, there is no way we can perform licensing functions before our startup script runs, and no way we can force Windows to run our script sooner. The only option is to delay initial user logins until after the script has run.

Note that if you let the Office repairs run, they will eventually succeed and restore Office licensing. That’s usually not an acceptable option, however. Certainly not in App Layering, where the repair has to happen on every boot.

For nonpersistent Unidesk desktops, this delay is automatically part of the desktop creation process. For persistent Unidesk desktops, you should just add to your creation process a delay before allowing users to login, if at all possible. Once the licensing has happened once on the Unidesk desktop, it will be fine going forward.

For App Layering images, however, that licensing is going to happen on every boot, because every boot is the first boot. So on every boot, our script has to run, overwrite the license information with the captured Office licenses, and activate against the KMS server. For App Layering, you need to make sure no user can login in the middle of that.

There are two approaches we know of. The problem is that your Connection Broker may allow users to login quite early in the boot process. Delaying the machine’s availability to the broker will also delay the user logging into the machine. Add Version to the platform layer. You can identify the broker agent service in the platform layer and set it to “Automatic (Delayed Start)”. To set the specific delay, create a DWORD named AutoStartDelay within the broker agent service folder, and set it to the number of seconds to delay before the service will start.

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices<Service name>]

AutoStartDelay=240

The other approach is XenDesktop-specific, where you can set a “settlement period” for all machines in a delivery group, preventing them from accepting a user login until the delay is complete. See this:

https://citrix.github.io/delivery-controller-sdk/Broker/Set-BrokerDesktopGroup/

set-brokerdesktopgroup -SettlementPeriodBeforeUse

Related:

  • No Related Posts

App Layering/Unidesk: Published Image or Packaging Machine Blue Screens with Code STOP 0x75640007

STOP code 0x75640007 comes from the App Layering filter driver. It specifically means that all of the required layers were not mounted by Windows within 10 minutes. Since those layers should appear instantly when Windows boots up, we assume there is a problem and blue-screen so the system can try again.

The most common reason for Windows to be unable to surface the layer disk is a policy or software that blocks access to removable devices. These policies are usually designed to block access to USB drives to prevent corporate espionage. However, virtual disks from most hypervisors are also set as removable in Windows, which allows the hypervisor to add and remove them without rebooting the guest OS. Technically, both the boot disk and the package disk are removable, but Windows can’t be blocked from accessing its own boot disk. So the policy only blocks access to the package disk, which means App Layering cannot access it. We wait 10 minutes for it to become visible, and then we give up.

The only solutions are to remove the policy (or configure the software to stop that restriction), or figure out how to white-list the extra disks. If this is not possible, contact Support and we can look into software that might be able to change those disks to be non-removable.

Related:

App Layering/Unidesk: STOP 0x75640007

STOP code 0x75640007 comes from the App Layering filter driver. It specifically means that all of the required layers were not mounted by Windows within 10 minutes. Since those layers should appear instantly when Windows boots up, we assume there is a problem and blue-screen so the system can try again.

The most common reason for Windows to be unable to surface the layer disk is a policy or software that blocks access to removable devices. These policies are usually designed to block access to USB drives to prevent corporate espionage. However, virtual disks from most hypervisors are also set as removable in Windows, which allows the hypervisor to add and remove them without rebooting the guest OS. Technically, both the boot disk and the package disk are removable, but Windows can’t be blocked from accessing its own boot disk. So the policy only blocks access to the package disk, which means App Layering cannot access it. We wait 10 minutes for it to become visible, and then we give up.

The only solutions are to remove the policy (or configure the software to stop that restriction), or figure out how to white-list the extra disks. If this is not possible, contact Support and we can look into software that might be able to change those disks to be non-removable.

Related:

Is there any way to disable the toast message for configuration without disabling other notifications?

I need a solution

My normal mode of operation is to have Auto-Protect disabled, and I manually scan any new files that come onto my system.

As a result, every time I log into windows, I get a toast notification from SEP that there are problems with the product.

I know that I can disable toast notifications globally via the Client Management section of the app – however, I don’t want to disable other critical notifications (such as when malware is found).  I *only* want to disable this one annoying message.

Is there any way to do this?  Or are malware notifications separate from the toast notifications?  And if the latter, what else comes up via toast?

0

Related:

Event ID 5008 — Microsoft Antimalware Engine Update

Event ID 5008 — Microsoft Antimalware Engine Update

Updated: October 23, 2007

Applies To: Windows Server 2008

The Microsoft Antimalware Engine version is updated frequently to detect and remove the latest spyware or other potentially unwanted software. The Microsoft Antimalware Engine must be started and functioning correctly for a scan to successfully complete.

Event Details

Product: Windows Defender
ID: 5008
Source: Microsoft-Windows-Windows Defender
Version: 1.1
Symbolic Name: MALWAREPROTECTION_ENGINE_FAILURE
Message: %1 engine has been terminated due to an unexpected error. %tFailure Type:%b%5 %tException code:%b%6 %tResource:%b%3

Resolve
Restart Windows Defender

The scanning engine must be available when Windows Defender starts. Close Windows Defender and then open it again. If the scanning engine is still not available, restart the computer.

Verify

Windows Defender uses the scanning engine to run Windows Defender scans. To verify that the scanning engine updated successfully and is working correctly, you should run a Windows Defender quick scan.

To perform this procedure, you must be a member of the Users group, or you must have been delegated the appropriate authority.

To verify that the scanning engine updated successfully and is working correctly:

  1. Click Start, point to All Programs, and then click Windows Defender.
  2. Click the down arrow next to Scan, and then click Quick Scan.
  3. If the quick scan completes successfully, the scanning engine was updated successfully and is working correctly.

Related Management Information

Microsoft Antimalware Engine Update

Windows Defender

Related:

Event ID 4101 — Display Driver Timeout Detection and Recovery

Event ID 4101 — Display Driver Timeout Detection and Recovery

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

Windows Vista and Windows Server 2008 can detect when the graphics hardware or device driver take longer than expected to complete an operation. When this happens, Windows attempts to preempt the operation, and restore the display system to a usable state by resetting the graphics adapter. Typically, the only noticeable effect from this is a flicker of the display due to the reset and subsequent screen redraw. For more information, see “Timeout Detection and Recovery of GPUs through WDDM” at http://go.microsoft.com/fwlink/?linkid=77531 on the Microsoft Web site.

Event Details

Product: Windows Operating System
ID: 4101
Source: Display
Version: 6.1
Symbolic Name: DISPMSG_NOTIFY_USER_TDR_RECOVERY_TEXT
Message: Display driver %1 stopped responding and has successfully recovered.

Resolve
Check Windows Update for a New Display Driver

Windows detected that the video adapter hardware on your computer has taken longer than expected to complete a requested operation. Windows has recovered and reset the graphics hardware.

This event is for information purposes only, and no action is typically required. If this problem occurs often, use Windows Update to check if a new display driver for your display adapter is available. Some older graphics applications might display a black screen or a black section of the screen, and might need to be restarted.

To perform this procedure, you must be a member of the local Administrators group, or you must be delegated the appropriate authority.

To start Windows Update

  1. Click Start.
  2. Click All Programs.
  3. Click Windows Update.
  4. In the upper left corner of the Windows Update page, click Check for updates.
  5. After the check has completed, click View available updates.
  • If an update is available for your display adapter, select it, and then install it.
  • If no updates are currently available, check back periodically to see if your vendor has supplied a new device driver.

Verify

Confirm that you can see the desktop and your applications as expected.

Related Management Information

Display Driver Timeout Detection and Recovery

Core Operating System

Related:

How to hide Verify shortcuts from Datacap Desktop

I am migrating a 8.1 application to 9.1 and am running into an issue. We are using Desktop to scan but TMWeb to verify. We have a completely custom verify page (called Verify.aspx). After migrating the app from 8.1 to 9.1, when I open Desktop, I see all of the Verify shortcuts, because my Program option is set to Multiple.

I’m not sure how I can configure this to meet the requirements. My Verify task is set with Program = multiple, because I need to reference the custom verify page. I tried changing the Program to verifine.aspx but then when I go into the Setup screen, the web page field is disabled. Is there a way using the tool that I can use a custom Verify page while still hiding the Verify shortcuts from Desktop?

Related: