Z: drive appears on Zbook 15 G3

Joe9999xxx · ‎02-10-2017

I have installed a new Zbook 15 for a client. While setting it up, but before domain attach, I would notice in File Explorer that a Z: drive would appear for a short time. When I attempted to view the drive, it would respond that I did not have permission. Looking in Disk Management, there is only the C: drive showing as having an assigned drive letter.

Now that the PC is domain attached, I am periodically losing the mapped Z: drive from group policy. Anyone have any ideas on some HP software or setting that might be taking this drive letter assignment?

Thanks in advance.

banhien · ‎02-10-2017

Hi,

Microsoft should tell us about this drive. Anyway, it is a temporary drive which holds information during Windows updates and it will go away then re-appear again.

Regards.

BH
***
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Joe9999xxx · ‎02-13-2017

Thanks for the quick reply. I looked into this a little more and found this over at TenForums.

https://www.tenforums.com/drivers-hardware/74921-mysterious-drive-z-appears.html

The poster seems to think that HP Support Assistant is causing the issue. I was at this client again today, so I set Support Assistant to not check for updates, thinking this may keep the system from stepping on the existing Z: drive map. I'll update in a couple of days with more info.

Joe9999xxx · ‎02-21-2017

The client contacted me again yesterday, saying his Z: drive was again missing. I asked if this is the first time since last Monday that this had happened, and he admitted that he didn't know, as the only day of the week he access it is on Monday.

I went ahead and uninstalled HP Support Assistant this time. I will update in a few days with more info.

Joe9999xxx · ‎02-24-2017

Well, the Z: drive is still occasionally showing up, causing my client to lose his Z: drive mapping. At this point, I still believe this is an HP issue, as I have yet to encounter this at any other client.