Probably because you tried to run a batch file in a shared folder on the network. If I'm not mistaken there are some commands that force a net use that will generate by default drive Z:. Try if you wanna get rid of that: Code: net use /delete Z: & REM If this is a network folder subst Z: /D & REM If this is a folder remapped cheers
I believe that's your system's reserved space. You shouldn't be able to see it, since windows usually don't assign driver letter (Z: ) to it. Not sure for all of its functions, but one of them is keeping info for your encrypted drive in case you are using an encryption. If you want to get rid of it, just open DiskManager and remove the letter Z: from the said 350mb partition, click ok and you wont see it again in Explorer.
Maybe Windows assigned a drive letter to your System Reserved Partition, it's where your boot files are stored. Take a look in Disk Management.
This. If it bothers you go into Disk Management and remove the drive letter and it will no longer be visible. Understand that's remove the assigned drive letter, NOT the drive or partition.
Best? That's mostly a matter of opinion. I'll reserve judgement for "best" after the anniversary update is installed on our computers. Now, if you're a boating buddy of mine, Windows 10 is the worst thing since ME. It all just depends, and as is the usual case YMMV.
Thanks for the replies so far. Though generally informative, they don’t seem to address the issues: Those who advise me to deal with it in Disc Management, should note my statement in my OP that drive Z is not shown in Disc Management. @ ofernandofilo I have not tried to run a batch file in a shared folder on the network. @ MrMagic To the suggestion about Office doing it, I clarify that I’ve only installed Word and no other Office apps. @ crexis I am not using an encrypted drive. And I cannot see drive Z in Disc Management. @ TrustMe & PhaseDoubt As I said, I cannot see drive Z in Disc Management. The suggestion about boot files being stored there seems interesting in view of the file system being FAT32, where would I find those? Shouldn’t they be normally hidden? Finally, there is the fact that it wasn’t there (visible) before and now it is. I clarify that I’m not so bothered about leaving it there, as long as I know what it is and why it suddenly appeared.
@Katzenfreund Can you please attach the output of the following: Code: diskpart select disk 0 list volume Looks like the the EFI boot system partition is somehow assigned a drive letter.
Excellent 100, you get 100 out of 100! TrustMe & PhaseDoubt were also of course correct in saying that boot files are stored there. There only remains my curiosity why it suddenly appeared.
Like I said repeatedly, partition Z didn't appear in DM, there was no Z mentioned there, otherwise I wouldn't have posted the question. EFI does show, but without a letter, without mention of FAT32 and with a size of 360 MB instead of the 256 MB of partition Z. Close, but not the same. MS are experts at creating confusion with simple things. And unfortunately they seem to catch me out every time. And a new development, which is the cause of this post. Though I did not delete Z yesterday, today after the anniversary update it's gone of its own. The reason I can think of for the disappearance is that...err...since the mystery was solved, MS no longer had a reason to show it there.
Yes, I got that. But when you agreed with 100's assessment that it was the ESP that suddenly showed up, my point was that if it truly was the ESP, it ought to have been visible in Disk Mgmt. as well. Since this partition doesn't, I'm still confused as to what it is. I suppose you could use a utility that tells you what partition type ID it is precisely, but since it's gone from view now perhaps you're not interested.
Odd. So if diskpart showed Z: as ESP, and disk management shows another one... I suppose it's possible that you somehow ended up with two ESPs. Disk management can't really be trusted since it doesn't show hidden partitions. Here's how to do it in PowerShell: Code: Get-Partition | select DiskNumber, PartitionNumber, DriveLetter, Size, GptType | ft The type GUID for ESP is {c12a7328-f81f-11d2-ba4b-00a0c93ec93b}.
Just open the disk management utility and remove the unneded drive letters, two mouse clicks. No need for obscure powershell commands.
Office starter uses a virtual drive, but it calls it Q, not Z. For the record it still works perfectly on W10 anniversary (it needs an update)