WVD: Office error: something went wrong

Arif Usman 496 Reputation points
2020-03-19T15:43:52.36+00:00

folks, 

We have WVD with persistence profile with fslogix. Not all users, but two or three users are getting office error as shown below. User's account is sign in, but when trying to do anything getting this error...We have AAD (no on premise AD). Any suggestions?

5012-something-went-wrong.png

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments

Answer accepted by question author

Arif Usman 496 Reputation points
2020-03-24T04:06:26.95+00:00

ok, wasn't able to fix the way i want to. So i deleted vhd file and have user log back in. Fslogix created profile, fixed issue by restoring data from one drive. closing this call...thanks everyone

Was this answer helpful?

0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Doug Coombs 1 Reputation point Microsoft Employee
    2020-03-20T17:47:38.667+00:00

    @Arif Usman , please help me understand what you mean by 'persistence profile'? Is this not using FSLogix? Is this using FSLogix but pointing the profile to the VMs hard drive?

    Was this answer helpful?

    0 comments
  2. Arif Usman 496 Reputation points
    2020-03-20T16:49:43.12+00:00

    these are all persistence profiles

    Was this answer helpful?

    0 comments
  3. Arif Usman 496 Reputation points
    2020-03-20T16:45:44.033+00:00

    these all persistence profiles

    Was this answer helpful?

    0 comments
  4. Doug Coombs 1 Reputation point Microsoft Employee
    2020-03-20T15:20:02.777+00:00

    Is the environment set to use machine based encryption to encrypt the FSLogix VHD Files? If so, if the user is logged on to a different machine, then they would not be able to decrypt the VHD.

    I am not certain of the exact configuration that "WVD with persistence profile with fslogix" refers to. Generally I would think of that as non-pooled desktops, but in that case, 1- the user should always go back to the same VM so my comment would not apply and 2- I would need to understand the reason / configuration for FSLogix.

    In general, using non-persistent profiles that have been encrypted using a machine based mechanism (such as TPM) is not supported, and I suspect that this is possible the issue here.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.