diff --git a/Translations/Language.ar.xml b/Translations/Language.ar.xml index 6018111b..1545a0d5 100644 --- a/Translations/Language.ar.xml +++ b/Translations/Language.ar.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.be.xml b/Translations/Language.be.xml index 2c22a496..f534cbf6 100644 --- a/Translations/Language.be.xml +++ b/Translations/Language.be.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.bg.xml b/Translations/Language.bg.xml index 4603e8ab..41bd03bf 100644 --- a/Translations/Language.bg.xml +++ b/Translations/Language.bg.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ca.xml b/Translations/Language.ca.xml index a6e1632f..f780d77c 100644 --- a/Translations/Language.ca.xml +++ b/Translations/Language.ca.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.co.xml b/Translations/Language.co.xml index 429e7800..71ed0413 100644 --- a/Translations/Language.co.xml +++ b/Translations/Language.co.xml @@ -1693,6 +1693,16 @@ Information about Corsican localization: Solu Linux. Quandu st’ozzione hè attivata, VeraCrypt esamineghja l’apparechju virtuale dicifratu cù « blkid -p » è munta i sistemi di schedarii NTFS scuperti cù ntfs3 invece di u terminale NTFS predefinitu. S’è a scuperta NTFS ùn riesce, VeraCrypt impiegheghja a selezzione autumatica nurmale di sistema di schedarii. S’è ntfs3 hè indispunibule, o bluccatu da a distribuzione, a muntatura pò fiascà. St’ozzione d’accettazione pò evità i blucchime d’interruzzione o d’invernazione cagiunati da sistemi di schedarii FUSE cù spaziu d’utilizatore senza risposta. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.cs.xml b/Translations/Language.cs.xml index a14e0c6d..106fed1f 100644 --- a/Translations/Language.cs.xml +++ b/Translations/Language.cs.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.da.xml b/Translations/Language.da.xml index 3dff694b..ad9551ca 100644 --- a/Translations/Language.da.xml +++ b/Translations/Language.da.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.de.xml b/Translations/Language.de.xml index 29ce609f..97d1c40c 100644 --- a/Translations/Language.de.xml +++ b/Translations/Language.de.xml @@ -1675,6 +1675,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.el.xml b/Translations/Language.el.xml index 07e83eb7..6c8fe94b 100644 --- a/Translations/Language.el.xml +++ b/Translations/Language.el.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.es.xml b/Translations/Language.es.xml index 0d608555..4dbdd9b5 100644 --- a/Translations/Language.es.xml +++ b/Translations/Language.es.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.et.xml b/Translations/Language.et.xml index 4b1e60c9..d8eb6c02 100644 --- a/Translations/Language.et.xml +++ b/Translations/Language.et.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.eu.xml b/Translations/Language.eu.xml index b2a1941d..7208007f 100644 --- a/Translations/Language.eu.xml +++ b/Translations/Language.eu.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.fa.xml b/Translations/Language.fa.xml index b2d0a880..603fba15 100644 --- a/Translations/Language.fa.xml +++ b/Translations/Language.fa.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.fi.xml b/Translations/Language.fi.xml index 1d87d0a1..b1312a08 100644 --- a/Translations/Language.fi.xml +++ b/Translations/Language.fi.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.fr.xml b/Translations/Language.fr.xml index 98c52fa5..a0bc38bb 100644 --- a/Translations/Language.fr.xml +++ b/Translations/Language.fr.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.he.xml b/Translations/Language.he.xml index a5dfe7ee..724edde6 100644 --- a/Translations/Language.he.xml +++ b/Translations/Language.he.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.hu.xml b/Translations/Language.hu.xml index d3aec106..0bc66511 100644 --- a/Translations/Language.hu.xml +++ b/Translations/Language.hu.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.id.xml b/Translations/Language.id.xml index 477ace57..12819153 100644 --- a/Translations/Language.id.xml +++ b/Translations/Language.id.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.it.xml b/Translations/Language.it.xml index f39553c5..02afdf5c 100644 --- a/Translations/Language.it.xml +++ b/Translations/Language.it.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ja.xml b/Translations/Language.ja.xml index 490b50ae..63781b62 100644 --- a/Translations/Language.ja.xml +++ b/Translations/Language.ja.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ka.xml b/Translations/Language.ka.xml index 17e68052..4c66b3d0 100644 --- a/Translations/Language.ka.xml +++ b/Translations/Language.ka.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ko.xml b/Translations/Language.ko.xml index 46960fbe..663d82d7 100644 --- a/Translations/Language.ko.xml +++ b/Translations/Language.ko.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.lv.xml b/Translations/Language.lv.xml index 7eba85b2..ad9d761e 100644 --- a/Translations/Language.lv.xml +++ b/Translations/Language.lv.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.my.xml b/Translations/Language.my.xml index 9732c952..792f9424 100644 --- a/Translations/Language.my.xml +++ b/Translations/Language.my.xml @@ -1674,6 +1674,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.nb.xml b/Translations/Language.nb.xml index 0d65496f..0d1e04d5 100644 --- a/Translations/Language.nb.xml +++ b/Translations/Language.nb.xml @@ -1672,6 +1672,16 @@ Kun for Linux. Når dette er aktivert, undersøker VeraCrypt den dekrypterte virtuelle enheten med blkid -p og monterer oppdagede NTFS-filsystemer med ntfs3 i stedet for standard NTFS-bakgrunnssystem. Hvis NTFS-deteksjonen mislykkes, bruker VeraCrypt vanlig automatisk filsystemvalg. Hvis ntfs3 er utilgjengelig eller blokkert av distribusjonen, kan monteringen mislykkes. Dette valgfrie alternativet kan forhindre at hvile- eller dvalemodus henger seg opp på grunn av fastlåste FUSE-filsystemer i brukermodus. Normal avmontering av volumet {0} mislyktes. Dette kan skje når programmer fortsatt har filer eller mapper åpne på volumet, eller når den underliggende enheten ble frakoblet og monteringen ble foreldet.\n\nHvis enheten fortsatt er tilkoblet, velg Nei, lukk programmene som bruker volumet, og prøv å avmontere på nytt.\n\nHvis enheten ble frakoblet eller monteringen er foreldet, kan VeraCrypt forsøke en nødopprydding ved å frakoble filsystemet og fjerne eller planlegge fjerning av VeraCrypts kjerneobjekter. Ventende skrivinger kan ha mislyktes, data kan gå tapt, og oppryddingen kan forbli ventende inntil programmene lukker åpne filer. Kontroller filsystemet med fsck eller et passende reparasjonsverktøy før du bruker det igjen.\n\nFortsette? Nødopprydding for volumet {0} er igangsatt. Hvis volumet ble frakoblet, monteringen var foreldet, eller det var ventende skrivinger, kontroller filsystemet med fsck eller et passende reparasjonsverktøy før du bruker det igjen. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.nl.xml b/Translations/Language.nl.xml index 8689f3cd..93181bad 100644 --- a/Translations/Language.nl.xml +++ b/Translations/Language.nl.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.nn.xml b/Translations/Language.nn.xml index 910f0476..b244909e 100644 --- a/Translations/Language.nn.xml +++ b/Translations/Language.nn.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.pl.xml b/Translations/Language.pl.xml index 82070006..d7ceb871 100644 --- a/Translations/Language.pl.xml +++ b/Translations/Language.pl.xml @@ -1672,6 +1672,16 @@ Tylko system Linux. Po włączeniu tej opcji VeraCrypt skanuje odszyfrowane urządzenie wirtualne za pomocą blkid -p i podłącza wykryte systemy plików NTFS za pomocą sterownika NTFS3 zamiast domyślnego NTFS. Jeśli wykrycie NTFS się nie powiedzie, VeraCrypt użyje standardowego automatycznego wyboru systemu plików. Jeśli NTFS3 jest niedostępny lub zablokowany przez dystrybucję, podłączenie może się nie powieść. To opcjonalne ustawienie pozwala uniknąć zawieszeń w trybie uśpienia lub hibernacji spowodowanych przez zamrożone systemy plików FUSE w przestrzeni użytkownika. Nie udało się wykonać normalnego odłączenia wolumenu {0}. Może się to zdarzyć, gdy programy nadal mają otwarte pliki lub katalogi na wolumenie lub gdy urządzenie bazowe zostało rozłączone, a podłączenie stało się nieaktualne.\n\nJeśli urządzenie jest nadal podłączone, wybierz opcję „Nie”, zamknij programy korzystające z wolumenu i spróbuj ponownie odłączyć.\n\nJeśli urządzenie zostało rozłączone lub podłączenie jest nieaktualne, VeraCrypt może podjąć próbę awaryjnego czyszczenia poprzez leniwe odłączenie systemu plików i usunięcie lub zaplanowanie usunięcia obiektów jądra VeraCrypt. Oczekujące zapisy mogły się nie powieść, dane mogły zostać utracone, a czyszczenie może pozostać w toku do momentu zamknięcia otwartych plików przez programy. Sprawdź system plików za pomocą fsck lub odpowiedniego narzędzia naprawczego przed ponownym użyciem.\n\nKontynuować? Rozpoczęto awaryjne czyszczenie wolumenu {0}. Jeśli wolumen był rozłączony, podłączenie było nieaktualne lub występowały oczekujące operacje zapisu, sprawdź system plików za pomocą fsck lub odpowiedniego narzędzia naprawczego przed ponownym użyciem. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.pt-br.xml b/Translations/Language.pt-br.xml index 2226458d..c2b21a91 100644 --- a/Translations/Language.pt-br.xml +++ b/Translations/Language.pt-br.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ro.xml b/Translations/Language.ro.xml index 310f225c..ce6d07ee 100644 --- a/Translations/Language.ro.xml +++ b/Translations/Language.ro.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.ru.xml b/Translations/Language.ru.xml index 254a4387..80f214e3 100644 --- a/Translations/Language.ru.xml +++ b/Translations/Language.ru.xml @@ -1672,6 +1672,16 @@ Только Linux. Если включено, VeraCrypt проверяет расшифрованное виртуальное устройство с помощью blkid -p и монтирует обнаруженные файловые системы NTFS с помощью драйвера ntfs3 вместо стандартного NTFS-бэкенда. Если NTFS не удалось определить, VeraCrypt использует обычный автоматический выбор файловой системы. Если ntfs3 недоступен или заблокирован дистрибутивом, монтирование может завершиться ошибкой. Эта необязательная настройка может предотвратить зависания при ждущем режиме или гибернации из-за замороженных файловых систем FUSE, работающих в пользовательском пространстве. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.sk.xml b/Translations/Language.sk.xml index 8473c57d..67f61f64 100644 --- a/Translations/Language.sk.xml +++ b/Translations/Language.sk.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.sl.xml b/Translations/Language.sl.xml index 37046183..f1675291 100644 --- a/Translations/Language.sl.xml +++ b/Translations/Language.sl.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.sv.xml b/Translations/Language.sv.xml index d797fd74..2589d478 100644 --- a/Translations/Language.sv.xml +++ b/Translations/Language.sv.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.th.xml b/Translations/Language.th.xml index a19409f9..d5996a44 100644 --- a/Translations/Language.th.xml +++ b/Translations/Language.th.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.tr.xml b/Translations/Language.tr.xml index e7339806..ac84621c 100644 --- a/Translations/Language.tr.xml +++ b/Translations/Language.tr.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.uk.xml b/Translations/Language.uk.xml index abc18273..4847a238 100644 --- a/Translations/Language.uk.xml +++ b/Translations/Language.uk.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.uz.xml b/Translations/Language.uz.xml index 5faf38ae..ce420e65 100644 --- a/Translations/Language.uz.xml +++ b/Translations/Language.uz.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.vi.xml b/Translations/Language.vi.xml index 2de225bd..8d13e858 100644 --- a/Translations/Language.vi.xml +++ b/Translations/Language.vi.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml index 1f48c4b1..142839ad 100644 --- a/Translations/Language.zh-cn.xml +++ b/Translations/Language.zh-cn.xml @@ -1673,6 +1673,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.zh-hk.xml b/Translations/Language.zh-hk.xml index 040567ca..feb2c27d 100644 --- a/Translations/Language.zh-hk.xml +++ b/Translations/Language.zh-hk.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/Translations/Language.zh-tw.xml b/Translations/Language.zh-tw.xml index c52b20aa..be583826 100644 --- a/Translations/Language.zh-tw.xml +++ b/Translations/Language.zh-tw.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/src/Common/Language.xml b/src/Common/Language.xml index c798b957..2d65663b 100644 --- a/src/Common/Language.xml +++ b/src/Common/Language.xml @@ -1672,6 +1672,16 @@ Linux only. When enabled, VeraCrypt probes the decrypted virtual device with blkid -p and mounts detected NTFS filesystems with ntfs3 instead of the default NTFS backend. If NTFS detection fails, VeraCrypt uses the normal automatic filesystem selection. If ntfs3 is unavailable or blocked by the distribution, mounting may fail. This opt-in option can avoid suspend or hibernate hangs caused by frozen user-space FUSE filesystems. Normal unmount of volume {0} failed. This can happen when applications still have files or directories open on the volume, or when the backing device was disconnected and the mount became stale.\n\nIf the device is still connected, choose No, close applications using the volume, and try unmounting again.\n\nIf the device was disconnected or the mount is stale, VeraCrypt can attempt emergency cleanup by lazy-detaching the filesystem and removing or scheduling removal of VeraCrypt kernel objects. Pending writes may have failed, data may be lost, and cleanup may remain pending until applications close open files. Check the filesystem with fsck or the appropriate repair tool before using it again.\n\nContinue? Emergency cleanup for volume {0} has been initiated. If the volume was disconnected, the mount was stale, or there were pending writes, check the filesystem with fsck or the appropriate repair tool before using it again. + Creating volume data. Please wait. + Finalizing volume creation: writing backup header. + Finalizing volume creation: flushing data to disk. This can take several minutes on large volumes or slow/USB storage. + Finalizing volume creation. + Volume creation has been aborted. + Volume creation failed. + Finalizing volume creation: mounting temporary volume. + Finalizing volume creation: preparing temporary device. + Finalizing volume creation: creating filesystem using {0}. + Finalizing volume creation: dismounting temporary volume. diff --git a/src/Core/VolumeCreator.cpp b/src/Core/VolumeCreator.cpp index d4b1a110..564e5b27 100644 --- a/src/Core/VolumeCreator.cpp +++ b/src/Core/VolumeCreator.cpp @@ -29,7 +29,9 @@ namespace VeraCrypt { VolumeCreator::VolumeCreator () - : SizeDone (0) + : SizeDone (0), + Stage (ProgressStage::NotStarted), + mProgressInfo {false, 0, 0, ProgressStage::NotStarted} { } @@ -58,6 +60,7 @@ namespace VeraCrypt if (filesystemSize < 1) throw ParameterIncorrect (SRC_POS); + Stage.Set (ProgressStage::WritingData); DataStart = Layout->GetDataOffset (HostSize); WriteOffset = DataStart; endOffset = DataStart + Layout->GetDataSize (HostSize); @@ -137,6 +140,8 @@ namespace VeraCrypt { SizeDone.Set (Options->Size); + Stage.Set (ProgressStage::WritingBackupHeader); + // Backup header SecureBuffer backupHeader (Layout->GetHeaderSize()); @@ -191,19 +196,26 @@ namespace VeraCrypt VolumeFile->Write (backupHeader); } + Stage.Set (ProgressStage::FlushingData); VolumeFile->Flush(); + Stage.Set (ProgressStage::Finished); } + else + Stage.Set (ProgressStage::Aborted); } catch (Exception &e) { + Stage.Set (ProgressStage::Error); ThreadException.reset (e.CloneNew()); } catch (exception &e) { + Stage.Set (ProgressStage::Error); ThreadException.reset (new ExternalException (SRC_POS, StringConverter::ToExceptionString (e))); } catch (...) { + Stage.Set (ProgressStage::Error); ThreadException.reset (new UnknownException (SRC_POS)); } @@ -214,6 +226,9 @@ namespace VeraCrypt void VolumeCreator::CreateVolume (shared_ptr options) { EncryptionTest::TestAll(); + SizeDone.Set (0); + Stage.Set (ProgressStage::NotStarted); + ThreadException.reset(); { #ifdef TC_UNIX @@ -379,6 +394,9 @@ namespace VeraCrypt Options = options; AbortRequested = false; + mProgressInfo.TotalSize = options->Size; + mProgressInfo.SizeDone = 0; + mProgressInfo.Stage = ProgressStage::NotStarted; mProgressInfo.CreationInProgress = true; struct ThreadFunctor : public Functor @@ -412,6 +430,7 @@ namespace VeraCrypt VolumeCreator::ProgressInfo VolumeCreator::GetProgressInfo () { mProgressInfo.SizeDone = SizeDone.Get(); + mProgressInfo.Stage = static_cast (Stage.Get()); return mProgressInfo; } } diff --git a/src/Core/VolumeCreator.h b/src/Core/VolumeCreator.h index bd63e26b..9bab5e33 100644 --- a/src/Core/VolumeCreator.h +++ b/src/Core/VolumeCreator.h @@ -144,11 +144,26 @@ namespace VeraCrypt { public: + struct ProgressStage + { + enum Enum + { + NotStarted = 0, + WritingData, + WritingBackupHeader, + FlushingData, + Finished, + Aborted, + Error + }; + }; + struct ProgressInfo { bool CreationInProgress; uint64 TotalSize; uint64 SizeDone; + ProgressStage::Enum Stage; }; struct KeyInfo @@ -180,6 +195,7 @@ namespace VeraCrypt shared_ptr Layout; shared_ptr VolumeFile; SharedVal SizeDone; + SharedVal Stage; uint64 WriteOffset; ProgressInfo mProgressInfo; diff --git a/src/Main/Forms/VolumeCreationProgressWizardPage.cpp b/src/Main/Forms/VolumeCreationProgressWizardPage.cpp index b4472369..19e6727a 100644 --- a/src/Main/Forms/VolumeCreationProgressWizardPage.cpp +++ b/src/Main/Forms/VolumeCreationProgressWizardPage.cpp @@ -22,7 +22,9 @@ namespace VeraCrypt ProgressBarRange (1), RealProgressBarRange (1), VolumeCreatorRunning (false), - MouseEventsCounter (0) + MouseEventsCounter (0), + CurrentProgressStage (VolumeCreator::ProgressStage::NotStarted), + MaxStaticTextWidth (-1) { DisplayKeysCheckBox->SetValue (displayKeyInfo); #ifdef TC_WINDOWS @@ -170,9 +172,61 @@ namespace VeraCrypt void VolumeCreationProgressWizardPage::SetMaxStaticTextWidth (int width) { + MaxStaticTextWidth = width; InfoStaticText->Wrap (width); } + void VolumeCreationProgressWizardPage::SetPageText (const wxString &text) + { + InfoStaticText->SetLabel (text); + + if (MaxStaticTextWidth > 0) + InfoStaticText->Wrap (MaxStaticTextWidth); + + Layout(); + if (GetParent()) + GetParent()->Layout(); + } + + void VolumeCreationProgressWizardPage::SetProgressStage (VolumeCreator::ProgressStage::Enum stage) + { + if (stage == CurrentProgressStage) + return; + + CurrentProgressStage = stage; + + switch (stage) + { + case VolumeCreator::ProgressStage::WritingData: + SetPageText (LangString["FORMAT_STAGE_WRITING_DATA"]); + break; + + case VolumeCreator::ProgressStage::WritingBackupHeader: + SetPageText (LangString["FORMAT_STAGE_WRITING_BACKUP_HEADER"]); + break; + + case VolumeCreator::ProgressStage::FlushingData: + SetPageText (LangString["FORMAT_STAGE_FLUSHING_DATA"]); + break; + + case VolumeCreator::ProgressStage::Finished: + SetPageText (LangString["FORMAT_STAGE_FINISHED"]); + break; + + case VolumeCreator::ProgressStage::Aborted: + SetPageText (LangString["FORMAT_STAGE_ABORTED"]); + break; + + case VolumeCreator::ProgressStage::Error: + SetPageText (LangString["FORMAT_STAGE_ERROR"]); + break; + + case VolumeCreator::ProgressStage::NotStarted: + default: + break; + } + } + void VolumeCreationProgressWizardPage::SetProgressState (bool volumeCreatorRunning) { if (volumeCreatorRunning) diff --git a/src/Main/Forms/VolumeCreationProgressWizardPage.h b/src/Main/Forms/VolumeCreationProgressWizardPage.h index 226ff752..d893cd42 100644 --- a/src/Main/Forms/VolumeCreationProgressWizardPage.h +++ b/src/Main/Forms/VolumeCreationProgressWizardPage.h @@ -30,8 +30,9 @@ namespace VeraCrypt void OnRandomPoolTimer (); void SetKeyInfo (const VolumeCreator::KeyInfo &keyInfo); void SetMaxStaticTextWidth (int width); - void SetPageText (const wxString &text) { InfoStaticText->SetLabel (text); } + void SetPageText (const wxString &text); void SetProgressRange (uint64 progressBarRange); + void SetProgressStage (VolumeCreator::ProgressStage::Enum stage); void SetProgressValue (uint64 value); void SetProgressState (bool volumeCreatorRunning); void IncrementEntropyProgress (); @@ -54,6 +55,8 @@ namespace VeraCrypt bool VolumeCreatorRunning; int MouseEventsCounter; Mutex AccessMutex; + VolumeCreator::ProgressStage::Enum CurrentProgressStage; + int MaxStaticTextWidth; }; } diff --git a/src/Main/Forms/VolumeCreationWizard.cpp b/src/Main/Forms/VolumeCreationWizard.cpp index 4d0c107d..74a31219 100644 --- a/src/Main/Forms/VolumeCreationWizard.cpp +++ b/src/Main/Forms/VolumeCreationWizard.cpp @@ -429,11 +429,14 @@ namespace VeraCrypt VolumeCreator::ProgressInfo progress = Creator->GetProgressInfo(); VolumeCreationProgressWizardPage *page = dynamic_cast (GetCurrentPage()); - page->SetProgressValue (progress.SizeDone); + if (page) + { + page->SetProgressStage (progress.Stage); + page->SetProgressValue (progress.SizeDone); + } if (!progress.CreationInProgress && !AbortConfirmationPending) { - SetWorkInProgress (false); OnVolumeCreatorFinished (); } } @@ -447,16 +450,29 @@ namespace VeraCrypt } } + void VolumeCreationWizard::SetCreationProgressText (const wxString &text) + { + VolumeCreationProgressWizardPage *page = dynamic_cast (GetCurrentPage()); + if (!page) + return; + + page->SetPageText (text); + page->Refresh(); + page->Update(); + Gui->Yield(); + } + void VolumeCreationWizard::OnVolumeCreatorFinished () { VolumeCreationProgressWizardPage *page = dynamic_cast (GetCurrentPage()); ProgressTimer.reset(); - page->SetProgressState (false); - - Gui->EndInteractiveBusyState (this); - SetWorkInProgress (false); - UpdateControls(); + if (page) + { + page->SetProgressState (false); + page->EnableAbort (false); + } + bool workInProgressCleared = false; try { @@ -472,6 +488,8 @@ namespace VeraCrypt { wxBusyCursor busy; + SetCreationProgressText (LangString["FORMAT_STAGE_PREPARING_TEMP_VOLUME"]); + MountOptions mountOptions (Gui->GetPreferences().DefaultMountOptions); mountOptions.Path = make_shared (SelectedVolumePath); mountOptions.NoFilesystem = true; @@ -483,10 +501,11 @@ namespace VeraCrypt shared_ptr volume = Core->MountVolume (mountOptions); finally_do_arg (shared_ptr , volume, { Core->DismountVolume (finally_arg, true); }); - + shared_ptr layout((volume->Type == VolumeType::Normal)? (VolumeLayout*) new VolumeLayoutV2Normal() : (VolumeLayout*) new VolumeLayoutV2Hidden()); uint64 filesystemSize = layout->GetMaxDataSize (VolumeSize); + SetCreationProgressText (LangString["FORMAT_STAGE_PREPARING_TEMP_DEVICE"]); Thread::Sleep (2000); // Try to prevent race conditions caused by OS // Temporarily take ownership of the device if the user is not an administrator @@ -540,10 +559,16 @@ namespace VeraCrypt args.push_back (string (virtualDevice)); + SetCreationProgressText (StringFormatter (LangString["FORMAT_STAGE_CREATING_FILESYSTEM"], fsFormatter)); Process::Execute (fsFormatter, args); + SetCreationProgressText (LangString["FORMAT_STAGE_DISMOUNTING_TEMP_VOLUME"]); } #endif // TC_UNIX + Gui->EndInteractiveBusyState (this); + SetWorkInProgress (false); + workInProgressCleared = true; + if (OuterVolume) { SetStep (Step::OuterVolumeContents); @@ -559,10 +584,24 @@ namespace VeraCrypt } catch (exception &e) { + if (!workInProgressCleared) + { + Gui->EndInteractiveBusyState (this); + SetWorkInProgress (false); + workInProgressCleared = true; + } Gui->ShowError (e); } - page->SetProgressValue (0); + if (!workInProgressCleared) + { + Gui->EndInteractiveBusyState (this); + SetWorkInProgress (false); + } + + if (page) + page->SetProgressValue (0); + if (SelectedVolumeType == VolumeType::Normal && !SelectedVolumePath.IsDevice()) { try diff --git a/src/Main/Forms/VolumeCreationWizard.h b/src/Main/Forms/VolumeCreationWizard.h index cccdae00..1f52f41f 100644 --- a/src/Main/Forms/VolumeCreationWizard.h +++ b/src/Main/Forms/VolumeCreationWizard.h @@ -59,6 +59,7 @@ namespace VeraCrypt void OnThreadExiting (wxCommandEvent& event); void OnVolumeCreatorFinished (); WizardStep ProcessPageChangeRequest (bool forward); + void SetCreationProgressText (const wxString &text); volatile bool AbortConfirmationPending; volatile bool AbortRequested;