User Profile
SDingemanse
MCT
Joined 7 years ago
User Widgets
Recent Discussions
Re: WVD Issue -Explorer Constantly Crashing and Restarting
PieterWigleven Hi Pieter, Do you got any update regarding this issue? Just saw the same behaviour with the Windows 10 Enterprise multi-session, Version 2004 + Microsoft 365 Apps image from the gallery. This is not acceptable for any production environment at the moment! With kind regards, Stefan Dingemanse20KViews0likes23CommentsRe: (Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004
PieterWigleven Hi Pieter, Do you got some more information about the versions which should get installed on the 20H1 image version? and which agent are we talking about? I can see the Configuration.zip file has been updated with a newer version of the Remote Desktop Services Infrastructure Agent. This is 1.0.1932.4800, after deployment via the gallery (Spring release), there is a newer version 1.0.1932.6700 being installed during the Upgrading status (the other version still remains installed after installation). And the same issue still exist, after a reboot the host become Available again in the portal but the same error occured when connecting. Error code: 0x3000047 What can I check to make sure the fix Microsoft has provided in the new WVD agent has been applied? With kind regards, Stefan Dingemanse28KViews0likes0CommentsRe: (Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004
Hi Pieter, I noticed this a few days ago when deploying an image based on 20H1, the issue is that the SXS component will not automatically be installed during deployment. So I did some more testing today, my conclusion so far. Deploying a WVD host based on 20H1 will fail to install the Remote Desktop Services SxS Network Stack component. Initial the host will be Unavailable in the hostpool. After some minutes the host will get the status Upgrading. Initial only two components will be installed (Remote Desktop Agent Boot Loader and the Remote Desktop Services Infrastructure Agent). After upgrading the Geneva Agent will be installed, but still the status of the machine is Unavailable. If you check your remoting connection with qwinsta you will not see the SXS component, this component is needed for the reseverse connectivity. In the folder C:\DeployAgent you will find a folder RDInfraSxsStackInstall with a single .MSI file, you can install this manually. You will find version 1811. After installing the machine will once again go to the upgrading status. This time a newer version of the SXS stack will be installed but the status will eventually be Upgrade failed. The result is two versions of the SXS agent are installed. the 1811 and 2003 version. I think this has something to do with the fact that the installer is unable to remove the agent. You can manually remove the older version and reboot the host (Watch out, the uninstall will stop the Remote Desktop services).After the reboot the host should be available and you can now login. Do you have any ETA for a fix? If you need some testers let me know!30KViews1like1CommentRe: Windows 10 Enterprise for Virtual Desktop Language issues
knowlite Sorry, I didn't have the time to update this thread. Indeed it looks like the issue's have been fixed with some updates. With the latest build 535 the issues with the Edge browser and Startmenu are fixed. knowlite Can you explain what settings for the keyboard you have done, I can test this for you in my environment.13KViews0likes3CommentsWindows 10 Enterprise for Virtual Desktop Language issues
Hi all, I will try to explain the behaviour of the issue's we are experiencing with a Virtual Machine with the Windows 10 Enterprise for Virtual Desktop image. We are deploying a VM through Azure Marketplace and we are choosing the Windows 10 multi-session image (1809/1903/1909). After the VM is created we are logging in with the local administrator account. Everything is working as expected. Now we want to add another display language, we can do this multiple ways (1. cab and appx files, 2. Through the settings menu, via the microsoft store). The language will be added and we can configure this language to be the default language. After we logoff and logon again the following is happening. 1) Search in startmenu is not working anymore (in the eventlog there is an event where cortana search is crashing) will provide the details later. 2) Microsoft Edge will not display the navigation buttons but instead just squares, when we click on a menu item Edge is crashing. 3) In the language settings menu there is some strange text like Regional Settings is filled with the letter j. Errors with %1 in the text. When we reconfigure the default language to English, everything is working again. This behaviour is for all languages and all WVD images. When deploying the normal Windows 10 Enterprise everything is working as expected with the languages. No strange errors. Am I missing something where we should apply a different configuration for the languages on the Windows 10 Multi User? Thank you in advance! With kind regards Stefan Dingemanse13KViews1like5Comments
Recent Blog Articles
No content to show