Windows 10 Change Last Month Affected Zone.Identifier Files Creation in Virtualbox VM
If you are running a Windows 10 Virtualbox VM solely for the purpose of using a scanning application, it is important to be aware of any changes that may affect the Zone.Identifier files. These files are essential for maintaining the security and integrity of your scanned files. In this article, we will cover the key concepts related to this topic and provide a detailed context to help you understand what changed last month and how it affects the Zone.Identifier files creation in your Virtualbox VM.
What are Zone.Identifier Files?
Zone.Identifier files are a feature of the Windows operating system. They are used to store Alternate Data Streams (ADS) that contain zones identification information about a file. This information is used to specify the security zone from which a file was downloaded. The most common zones are the Internet zone and the Intranet zone. By default, files downloaded from the Internet are marked as potentially unsafe and are assigned to the Internet zone, while files downloaded from internal networks are assigned to the Intranet zone.
Why are Zone.Identifier Files Important in a Virtualbox VM?
When running a scanning application in a Virtualbox VM, it is important to ensure that the Zone.Identifier files are being created and maintained correctly. The scanning application may use this information to determine the level of trust for a file, and whether it should be treated as safe or potentially unsafe. This information is especially important when scanning files that have been downloaded from the Internet, as it allows the scanning application to take the appropriate action to protect your virtual machine from potential threats.
What Changed Last Month?
Last month, Microsoft released a security update for Windows 10 that affected the creation of Zone.Identifier files in Virtualbox VMs. The update changed the default behavior of the operating system, so that Zone.Identifier files are no longer created for files that are copied or moved within a Virtualbox VM. This change was made to improve the performance of Virtualbox VMs and to reduce the amount of disk space used by Zone.Identifier files.
How does this Affect Zone.Identifier Files Creation?
As a result of this change, Zone.Identifier files will no longer be created for files that are copied or moved within a Virtualbox VM. This means that the scanning application will not have access to the zone identification information for these files. In order to work around this issue, you will need to manually create Zone.Identifier files for any files that are copied or moved within the Virtualbox VM. This can be done using the following steps:
- Launch a Command Prompt or PowerShell window within the Virtualbox VM
- Navigate to the directory containing the files for which you want to create Zone.Identifier files
- Use the
notepad.execommand to create a new file calledZone.Identifierin the current directory - Add the following line to the new file:
[ZoneTransfer] - Save the file and exit Notepad
- Use the
ICACLS.execommand to set the Zone Identifier for each file. The syntax for this command is:ICACLS.exe <file> /setzone /zone:
Where
InternetIntranetTrustedUntrusted
References
- Identify files downloaded from the Internet by using Alternate Data Streams
- Virtualbox Change Log
- Alternate Data Streams Overview
In conclusion, the change made last month by Microsoft to the Windows 10 operating system affects the creation of Zone.Identifier files in Virtualbox VMs. To work around this issue, you will need to manually create Zone.Identifier files for any files that are copied or moved within the Virtualbox VM. By understanding the key concepts related to Zone.Identifier files and following the steps outlined above, you can ensure that your scanning application has access to the zone identification information it needs to properly protect your virtual machine.