robgj821
Contributor
Contributor

Office 2016 Hardware Acceleration Nvidia Grid - Issue on session reconnect

Hi

We experience an issue where Office applications Outlook/Word goes Not Responding and does not recover upon reconnecting to a Nvidia GRID enabled Win10 client vm Horizon view session where Outlook is already opened.

This occurs every time a disconnect/reconnect to an existing session occurs, though is only an issue when the hardware graphics acceleration option for Office is enabled.

This happens whether connecting from thin clients or the Windows Horizon Client

We have tested this with a non-Grid enabled Win10 vm and it does not crash with or without graphics acceleration enabled.

Here are our environment specifics:


Hypervisor
ESXi, 6.0.0, 8934903

Model:PowerEdge R730

Host Driver Version: | NVIDIA-SMI 390.75 Driver Version: 390.75

Client OS: Win 10 1703

Client Driver Version: 391.81

GPU Profile: grid_m10-1b

Horizon View Version: 7.5

Office Version: 2016 version 1806 Build 10228.20134 Click to Run

I have a case open with VMware they are still investigating.

I also have a case open with Nvidia while they acknowledge the issue they say it's a Microsoft bug and to talk with them.

I find it hard to believe that no one else has seen this issue before, does anyone run a similar setup?

0 Kudos
5 Replies
Justin_Y
Enthusiast
Enthusiast

Any updates on this, putting in a ticket today for the same issue. Thanks

0 Kudos
jlevingston
VMware Employee
VMware Employee

Looks like it might be resolved in Windows 10 1803

0 Kudos
Justin_Y
Enthusiast
Enthusiast

Thanks, it looks like disabling hardware acceleration in office also resolved this issue from my tests. Used UEM to apply to Nvidia users. We currently can't upgrade windows 10 to test that resolution.

0 Kudos
FoodComa
Contributor
Contributor

We experience the same issue.

WIn10 1607

M10 - (1B Profile)

Office 2016

An office application crashes on reconnect.

We disabled hardware acceleration on Office via GPO for the time being.  We also cannot  upgrade our Windows version.

0 Kudos
robgj821
Contributor
Contributor

I can confirm this was resolved with Win10 1803

0 Kudos