<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="ar" key="RESCUE_DISK_BURN_NO_CHECK_WARN">‮تحذير: إن كنت أنشأت بالفعل قرص إنقاذ تروكربت فيما مضى فاعلم أنه لا يمكن استخدامه لقسم\\سواقة النظام هذه لأنه أنشئ لمفتاح رئيسي مختلف! في كل مرة تعمّي قسم\\سواقة نظام ينبغي إنشاء قرص إنقاذ تروكربت حديث لها حتى إذا استخدمت كلمة السر ذاتها.</string>

<string lang="ar" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">‮عطل: تعذّر حفظ تضبيطات تعمية النظام.</string>

<string lang="ar" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">‮تعذّر استبداء الاختبار المبدئي لتعمية النظام.</string>

<string lang="ar" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">‮تعذَّر استبداء صيرورة إنشاء نظام التشغيل المخفي.</string>

<string lang="ar" key="WIPE_MODE_TITLE">‮طور المحو</string>

<string lang="ar" key="INPLACE_ENC_WIPE_MODE_INFO">‮في بعض أنواع وسائط التخزين عندما تطمس البيانات ببيانات أخرى فقد يكون من الممكن استرجاع البيانات المطموسة باستخدام تقنيات مثل مجاهير الطاقة المغناطيسية. ينطبق هذا كذلك على البيانات التي تنطمس بنسخ معماة منها (و هو ما يحدث عندما يعمّي تروكربت قسما غير معمّى أو سواقة). طبقا لبعض الدراسات و المنشورات الحكومية فإن استرجاع البيانات قد يمكن الحول دونه (أو تصعيبه) بطمس البيانات ببيانات شبه عشوائية و بيانات عشوائية بعدد معين من المرات. لذا إن كنت تعتقد أن خصمك قد يلجأ لمثل تلك الأساليب لاسترجاع البيانات التي تنوي تعميتها فقد تحب اختيار أحد أطوار المحو (البيانات الحالية لن تفقد). لاحظ أن المحو لا يمكن إجراؤه بعد تعمية القسم\\السواقة. عندما تم تعمية القسم\\السواقة فلن تكتب أية بيانات غير معماة إليها. كل البيانات التي تكتب إليها تعمى أولا لحظيا في الذاكرة ثم تكتب هذه البيانات المعماة على القرص.</string>

<string lang="ar" key="WIPE_MODE_INFO">‮في بعض أنواع وسائط التخزين عندما تطمس البيانات ببيانات أخرى (مثلا عند حذف البيانات) فقد يكون من الممكن استرجاع البيانات المطموسة باستخدام تقنيات مثل مجاهير الطاقة المغناطيسية. طبقا لبعض الدراسات و المنشورات الحكومية فإن استرجاع البيانات قد يمكن الحول دونه (أو تصعيبه) بطمس البيانات ببيانات شبه عشوائية و بيانات عشوائية بعدد معين من المرات. لذا إن كنت تعتقد أن خصمك قد يلجأ لمثل تلك الأساليب لاسترجاع البيانات التي ستحذف فقد تحب اختيار أحد أطوار المحو عديدة المرات. لاحظ أنه كلما زادت مرات المحو ازدادت المدة المطلوبة لإتمام لمحو البيانات.</string>

<string lang="ar" key="DEVICE_WIPE_PAGE_TITLE">‮المحو</string>

<string lang="ar" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nn‮ملاحظة: تمكن مقاطعة صيرورة المحو و إطفاء الحاسوب ثم تشغيل النظام المخفي مجددا و معاودة الصيرورة (هذا المرشد سيشتغل تلقائيا). لكن إن قوطعَت الصيرورة فإنه سيتوجب بدؤها من جديد.</string>

<string lang="ar" key="DEVICE_WIPE_PAGE_INFO">\nn‮ ‮ملاحظة: إن قوطعت صيرورة المحو ثم عوودت فإن الصيرورة ستتوجب إعادة بدئها من جديد.</string>

<string lang="ar" key="CONFIRM_WIPE_ABORT">‮أتريد إجهاض صيرورة المحو؟</string>

<string lang="ar" key="CONFIRM_WIPE_START">‮تحذير: كل محتويات القسم\\النبيطة المختارة ستُمحى و تُفقد.</string>

<string lang="ar" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">‮كل محتويات القسم الذي فيه النظام الأصلي ستُمحى. ‮ ‮ملاحظة: كل محتويات القسم الذي سيُمحى قد تم نسخها إلى قسم النظام المخفي.</string>

<string lang="ar" key="WIPE_MODE_WARN">‮تنبيه: لاحظ أنه مثلا عند اختيار طور المحو ذي المرات الثلاث فإن الزمن المطلوب لتعمية القسم\\السواقة سيزيد أربع مرات. كذلك إن اخترت طور المحو ذي ‪35‬ مرة فإن المدة سيكون أطول ‪36‬ مرة (و قد يستغرق عدة أسابيع). ‮ ‮لكن لاحظ أن المحو لا يمكن إجراؤه بعد تمام تعمية القسم\\السواقة. فبعد تعمية القسم\\السواقة لن تكتب إليه أية بيانات غير معمّاة. كل البيانات التي تكتب إليه ستعمى أولا لحظيا في الذاكرة قبل أن تكتب إلى القرص (لذا فإن الأداء لن يتأثر). ‮ ‮أمتأكد أنك تريد استخدام طور المحو؟</string>

<string lang="ar" key="WIPE_MODE_NONE">‮بلا (الأسرع)</string>

<string lang="ar" key="WIPE_MODE_1_RAND">‮مرة واحدة (بيانات عشوائية)</string>

<string lang="ar" key="WIPE_MODE_3_DOD_5220">‮3 مرّات (‪US DoD 5220.22-M‬)</string>

<string lang="ar" key="WIPE_MODE_7_DOD_5220">‮7 مرّات (‪US DoD 5220.22-M‬)</string>

<string lang="ar" key="WIPE_MODE_35_GUTMANN">‮‪35‬ مرة (Gutmann)</string>

<string lang="ar" key="SYS_MULTI_BOOT_MODE_TITLE">‮عدد نظم التشغيل</string>

<string lang="ar" key="MULTI_BOOT_FOR_ADVANCED_ONLY">‮تحذير: ينبغي ألا يعمي المستخدمون غير ذوي الخبرة ويندوز في التجهيزات عديدة الإقلاع. ‮ ‮أأواصل؟</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">‮سواقة الإقلاع</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">‮هل نظام التشغيل العامل حاليا منصّب على سواقة الإقلاع؟ ‮ ‮ملاحظة: أحيانا لا يكون ويندوز منصّبا على ذات السواقة التي عليها مُحمِّل إقلاع ويندوز (قسم الإقلاع). إن كان هذا هو الحال، انقر 'لا'.</string>

<string lang="ar" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">‮لا يدعم تروكربت حاليا تعمية نظام تشغيل لا يُقلع من السواقة التي هو منصّب عليها.</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">‮عدد سواقات النظام</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">‮كم سواقة تحوي نظام تشغيل؟ ‮ ‮ملاحظة: مثلا إن كان أي من نظم التشغيل (مثل: ويندوز أو ماك أوإس أو لينكس، إلخ) مُنَصَّبا على السواقة الرئيسية و توجد أي نظم تشغيل إضافية منصّبة على السواقة الثانوية فاختر 'اثنتين أو أكثر'.</string>

<string lang="ar" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">‮لا يدعم تروكربت حاليا تعمية السواقة بكاملها إن كانت تحوي عدة نظم تشغيل. ‮ ‮حلول ممكنة: ‮ ‮- لا يزال بوسعك تعمية أحد النظم إن رجعت لخيار تعمية قسم نظام واحد (بدلا من خيار تعمية سواقة النظام بكاملها). ‮ ‮- أو يمكنك تعمية السواقة بكاملها إن نقلت النظم الأخرى إلى سواقات أخرى تاركا نظاما واحدا و حسب على السواقة التي تريد تعميتها.</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">‮عدة نظم على سواقة واحدة</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">‮هل توجد نظم تشغيل أخرى منصّبة على السواقة المنصّب عليها نظام التشغيل العامل حاليا؟ ‮ ‮ملاحظة: مثلا إن كان نظام التشغيل العامل حاليا منصّبا على السواقة رقم 0 و التي تحوي عدة أقسام، و إذا كان أحد تلك الأقسام يحوي ويندوز و قسم آخر يحوي أي نظام تشغيل آخر (مثلا: ويندوز أو ماك أوإس أو لينكس، إلخ) فاختر 'نعم'.</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">‮مُحمِّل إقلاع غير ويندوز</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">‮هل سجل الإقلاع الرئيسي ‪MBR‬ منصب فيه مُحمِّل إقلاع لغير ويندوز (أو مدير إقلاع ما)؟ ‮ ‮ملاحظة: مثلا، إن كان المسار الأول لسواقة الإقلاع يحوي ‪GRUB‬ أو ‪LILO‬ أو ‪XOSL‬ أو محمل إقلاع أو مدير إقلاع لا يخص ويندوز، فانقر 'نعم'.</string>

<string lang="ar" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">‮عديد الإقلاع</string>

<string lang="ar" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">‮لا يدعم تروكربت حاليا التجهيزات عديدة الإقلاع المنصّب فيها مُحمِّل إقلاع غير الذي يخصُّ ويندوز في سجّل الإقلاع الرئيسي. ‮ ‮الحلول الممكنة: ‮ ‮- إن كنت تستخدم مدير إقلاع لإقلاع كل من ويندوز و لينكس فانقل مدير الإقلاع (عادة هو ‪GRUB‬) من سِجِّل الإقلاع الرئيسي إلى قسمٍ. ثم شغل هذا المرشد مجددا و عمِّ قسم\\سواقة النظام. لاحظ أن مُحمِّل إقلاع تروكربت سيصبح هو مدير الإقلاع الرئيسي و أنه سيسمح لك بتشغيل مدير الإقلاع الأصلي (مثلا: ‪GRUB‬) كمدير إقلاع ثانوي (بضغط ‪Esc‬ في شاشة محمِّل إقلاع تروكربت) و بهذا سيمكنك تشغيل لينكس.</string>

<string lang="ar" key="WINDOWS_BOOT_LOADER_HINTS">‮إن كان نظام التشغيل العامل حاليا منصبا في قسم الإقلاع فسيتوجب عليك بعد تعميته أن تدخل كلمة السر الصحيحة حتى إن أردت تشغيل أي نظام ويندوز آخر غير معمى (لأنها ستتشارك جميعها في مُحمِّل إقلاع وحيد معمى). ‮ ‮على العكس من ذلك إن كان نظام التشغيل العامل حاليا ليس منصبا في قسم الإقلاع (أو إن كان مُحمِّل إقلاع ويندوز لا يستخدمه أي نظام تشغيل آخر) فإنك بعد تعمية هذا النظام لن تضطر إلى إدخال كلمة السر الصحيحة لإقلاع نظم التشغيل الأخرى غير المعماة. لن يكون عليك سوى ضغط مفتاح ‪Esc‬ لبدء النظام غير المعمى (إن وجد أكثر من نظام غير معمّى فسيمكنك اختيار أيها يقلع من قائمة مدير إقلاع تروكربت). ‮ ‮ملاحظة: عادة ما يُنصَّب أوّل نظام ويندوز يُنصَّب في قسم الإقلاع.</string>

<string lang="ar" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">‮تعمية المنطقة المحمية المضيفة</string>

<string lang="ar" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">‮في آخر عديد من السواقات توجد منطقة عادة ما تكون محجوبة عن نظام التشغيل (يشار إليها بالمناطق المحمية من المضيف)، إلا أن بعض البرمجيات يمكنها القراءة و الكتابة في تلك المناطق. ‮ ‮تحذير: يستخدم بعض مصنِّعو الحواسيب تلك المناطق لتخزين أدوات و بيانات لمصفوفات RAID أو لاسترجاع النظام أو لتجهيز النظام أو الفحص أو لأغراض أخرى. إن توجَّب النفاذ إلى أي من تلك الأدوات قبل الإقلاع فإن المنطقة المحجوبة يجب ألا تعمى (اختر 'لا' في الأعلى). ‮ ‮أتريد من تروكربت أن يتحسس و يعميّ تلك المنطقة (إن وجدت) التي في آخر سواقة النظام؟</string>

<string lang="ar" key="SYSENC_TYPE_PAGE_TITLE">‮نوع تعمية النظام</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="be" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Памылка! Немагчыма захаваць усталёўкі сістэмнага шыфравання.</string>

<string lang="be" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Немагчыма ініцыяваць перад-тэст сістэмнага шыфравання.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="be" key="WIPE_MODE_TITLE">Рэжым ачысткі</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="be" key="WIPE_MODE_NONE">Не (самы хуткі)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="be" key="WIPE_MODE_3_DOD_5220">3 праходы (US DoD 5220.22-M)</string>

<string lang="be" key="WIPE_MODE_7_DOD_5220">7 праходаў (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="be" key="SYS_MULTI_BOOT_MODE_TITLE">Лік аперацыйных сістэм</string>

<string lang="be" key="MULTI_BOOT_FOR_ADVANCED_ONLY">УВАГА: Неспрактыкаваным карыстачам не варта спрабаваць шыфраваць Windows у мультызагрузных канфігурацыях.\n\nПрацягнуць?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="be" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Загрузны дыск</string>

<string lang="be" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Запушчаная ў дадзены момант аперацыйная сістэма ўсталяваная на загрузным дыску?\n\nНататка: часам Windows бывае ўсталяваная не на тым дыску, з якога яна грузіцца (дзе знаходзіцца загрузны падзел). Калі гэта ваш выпадак, то абярыце 'Не'.</string>

<string lang="be" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">У дадзены момант VeraCrypt не падтрымлівае шыфраванне аперацыйнай сістэмы, якая загружаецца не з таго ж дыска, на якім яна ўсталяваная.</string>

<string lang="be" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Лік сістэмных дыскаў</string>

<string lang="be" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Колькі дыскаў утрымоўвае аперацыйная сістэма?\n\nНататка: напрыклад, калі ў вас адна аперацыйная сістэма (скажам, Windows, Mac OS X, Linux і г.д.) усталяваная на першасным дыску, а іншая -- на другасным, абярыце '2 ці больш'.</string>

<string lang="be" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">У дадзены момант VeraCrypt не падтрымлівае шыфраванне ўсяго дыска, які ўтрымоўвае некалькі аперацыйных сістэм.\n\nМагчымыя варыянты:\n\n- Вы можаце зашыфраваць адну з сістэм, калі вернецеся назад і абярэце шыфраванне толькі аднаго сістэмнага падзелу (а не ўсяго сістэмнага дыска).\n\n- Вы зможаце зашыфраваць увесь дыск, калі перамесціце некаторыя сістэмы на іншыя дыскі, пакінуўшы толькі адну АС на дыску, якую жадаеце зашыфраваць.</string>

<string lang="be" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Некалькі сістэм на адным дыску</string>

<string lang="be" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">На дыску, дзе ўсталяваная бягучая АС, ёсць іншыя аперацыйныя сістэмы?\n\nНататка: напрыклад, калі бягучая АС усталяваная на дыску #0, які мае некалькі падзелаў, і калі на адным з падзелаў знаходзіцца Windows, а на іншым -- яшчэ адна АС (скажам, Windows, Mac OS X, Linux і г.д.), то абярыце 'Так'.</string>

<string lang="be" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Адрозны ад Windows загрузнік</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="be" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Мультызагрузка</string>

<string lang="be" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">Пакуль VeraCrypt не падтрымлівае мультызагрузныя канфігурацыі, дзе ў галоўным загрузным запісе (MBR) усталяваны не стандартны загрузнік Windows.\n\nМагчымыя варыянты:\n\n- Калі вы выкарыстоўваеце загрузны мэнэджар для загрузкі Windows і Linux, перанясіце яго (звычайна гэта GRUB) з MBR у падзел. Затым запусціце зноў гэты майстар і зашыфруйце сістэмны падзел/дыск. Звярніце ўвагу, што загрузнік VeraCrypt стане асноўным загрузным мэнэджарам і дазволіць вам запускаць зыходны загрузны мэнэджар (скажам, GRUB) як другасны (націскам Esc пры адлюстраванні экрана загрузніка VeraCrypt) і, такім чынам, запускаць Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="bg" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ВНИМАНИЕ: Ако вече сте създали VeraCrypt Спасителен Диск преди време, той не може да се преизползва за това системно устройство/дял, защото е създаден за различен главен ключ! Всеки път когато криптирате системно устройство/дял, трябва да създавате нов VeraCrypt Спасителен Диск за него дори ако използвате същата парола.</string>

<string lang="bg" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Грешка: Настройките на системното криптиране не могат да бъдат записани.</string>

<string lang="bg" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Не може да се стартира предварителния тест на системното криптиране.</string>

<string lang="bg" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Не може да се инициализира процеса на създаване на скритата операционна система.</string>

<string lang="bg" key="WIPE_MODE_TITLE">Режим на заличаване</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="bg" key="WIPE_MODE_NONE">Никакъв (най-бързо)</string>

<string lang="bg" key="WIPE_MODE_1_RAND">1-пасов (случайни данни)</string>

<string lang="bg" key="WIPE_MODE_3_DOD_5220">3-пасов (US DoD 5220.22-M)</string>

<string lang="bg" key="WIPE_MODE_7_DOD_5220">7-пасов (US DoD 5220.22-M)</string>

<string lang="bg" key="WIPE_MODE_35_GUTMANN">35-пасов ("Gutmann")</string>

<string lang="bg" key="SYS_MULTI_BOOT_MODE_TITLE">Брой операционни системи</string>

<string lang="bg" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ВНИМАНИЕ: Начинаещи потребители никога не трябва да опитват да криптират Windows в multi-boot конфигурации.\n\nПродължаване?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot устройство</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Текущо стартираната операционна система на boot устройство ли е инсталирана?\n\nЗабележка: Понякога, Windows не е инсталиран на същото устройство, където е Windows boot loader (boot дял). Ако случаят е такъв, изберете 'Не'.</string>

<string lang="bg" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">За момента VeraCrypt не поддържа криптиране на операционна система, която не стартира от устройството, на което е инсталирана.</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Брой системни устройства</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Колко устройства съдържат операционни системи?\n\nЗабележка: Примерно, ако имате някаква операционна система (например Windows, Mac OS X, Linux, и т.н.) инсталирана на вашето първично устройство и някаква друга операционна система инсталирана на вашето вторично устройство, изберете '2 или повече'.</string>

<string lang="bg" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">За момента VeraCrypt не поддържа криптиране на цяло устройство, което съдържа няколко операционни системи.\n\nВъзможни решения:\n\n- Все още можете да криптирате една от системите, ако се върнете назад и изберете криптиране на системен дял (а не на цялото системно устройство).\n\n- Алтернативно, ще можете да криптирате цялото устройство, ако преместите някои от системите на други устройства, така че да оставите само една система на устройството, което искате да криптирате.</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Няколко системи на едно устройство</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Има ли други операционни системи, инсталирани на устройството, на което стартираната в момента операционна система е инсталирана?\n\nЗабележка: Примерно, ако стартираната в момента операционна система е инсталирана на устройство #0, което съдържа няколко дяла, и ако един от дяловете съдържа Windows и друг дял съдържа някаква друга операционна система (например Windows, Mac OS X, Linux, и т.н.), изберете 'Да'.</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Не-Windows Boot Loader</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Инсталирана ли е не-Windows boot зареждаща програма (или boot мениджър) в главния boot запис (MBR)?\n\nЗабележка: Например, ако първата писта на boot устройството съдържа GRUB, LILO, XOSL, или някой друг не-Windows boot мениджър (или boot зареждаща програма), изберете 'Да'.</string>

<string lang="bg" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="bg" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">За момента VeraCrypt не поддържа multi-boot конфигурации, където не-Windows boot loader е инсталиран в Master Boot Record.\n\nВъзможни решения:\n\n- Ако използвате boot мениджър за да стартирате Windows и Linux, преместете boot мениджъра (най-често, GRUB) от Master Boot Record в дял. След това стартирайте този помощник отново и криптирайте системния дял/устройство. Забележете, че VeraCrypt Boot Loader ще стане вашият първичен boot мениджър и ще ви позволи да стартирате оригиналния boot мениджър (например GRUB), като ваш вторичен boot мениджър (като натиснете Esc в екрана на VeraCrypt Boot Loader) и по този начин ще можете да стартирате Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="ca" key="LAUNCH_WIN_ISOBURN">Engega el gravador de discos de Microsoft Windows</string>

<string lang="ca" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ATENCIÓ: Si ja havia creat un disc de recuperació, aquest no es pot reutilitzar per aquesta partició/unitat de sistema ja que s'ha creat per a una clau mestre diferent! Cada cop que xifri la partició/unitat de sistema haurà de crear un nou disc de recuperació per ella encara que utilitzi la mateixa contrasenya.</string>

<string lang="ca" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: No s'han pogut guardar la configuració de xifrat.</string>

<string lang="ca" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">No s'ha pogut iniciar la prova prèvia de xifrat del sistema</string>

<string lang="ca" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">No s'ha pogut iniciar la creació del sistema operatiu ocult.</string>

<string lang="ca" key="WIPE_MODE_TITLE">Tipus de neteja</string>

<string lang="ca" key="INPLACE_ENC_WIPE_MODE_INFO">En alguns tipus de suports d'emmagatzematge, quan les dades es sobreescriuen amb altres dades és possible recuperar les dades sobreescrites utilitzant tècniques com ara forces magnètiques microscòpiques. Això també s'aplica a les dades que s'han sobreescrit en la seva forma xifrada (cosa que passa quan el VeraCrypt xifra inicialment una partició o unitat no xifrada). Tenint en compte alguns estudis i publicacions gubernamentals, es pot dificultar o impossibilitar la recuperació de dades sobreescrites sobreescribint dades pseudoaleatòries i normals un cert número de vegades. Per tant, si vostè creu que un adversari pot utilitzar aquest tipus de tècniques per recuperar les dades que intenta xifrar, segurament voldrà seleccionar algun dels mètodes de neteja (les dades existens NO s'esborraran). Tingui en compte que la neteja NO es pot dur a terme després de xifrar la partició/unitat. Quan una partició/unitat està xifrada completament no s'hi escriuen dades no xifrades. Totes les dades que s'hi escriuen es xifren al vol a la memòria i només després s'escriuen al disc.</string>

<string lang="ca" key="WIPE_MODE_INFO">En alguns tipus de suports d'emmagatzematge, quan les dades es sobreescriuen amb altres dades és possible recuperar les dades sobreescrites utilitzant tècniques com ara forces magnètiques microscòpiques. Tenint en compte alguns estudis i publicacions gubernamentals, es pot dificultar o impossibilitar la recuperació de dades sobreescrites sobreescribint dades pseudoaleatòries i normals un cert número de vegades. Per tant, si vostè creu que un adversari pot utilitzar aquest tipus de tècniques per recuperar les dades que intenta xifrar, segurament voldrà seleccionar algun dels mètodes de neteja.\n\nNota: Com és passades utilitzi, més estona trigarà a esborrar les dades.</string>

<string lang="ca" key="DEVICE_WIPE_PAGE_TITLE">Netejant</string>

<string lang="ca" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNota: Pot interrompre el procés de neteja, apagar l'ordinador, engegar el sistema oepratiu ocult una altre vegada i reprender el procés (l'assistent s'engegarà automàticament). De totes maneres, si l'interromp s'haurà de tornar a començar des del principi tot el procés de neteja.</string>

<string lang="ca" key="DEVICE_WIPE_PAGE_INFO">\n\nNota: Si intenta interrompre el procés de neteja i reprendre'l haurà de tornar a començar el procés des del principi.</string>

<string lang="ca" key="CONFIRM_WIPE_ABORT">Vol aturar el procés de neteja?</string>

<string lang="ca" key="CONFIRM_WIPE_START">ATENCIÓ: S'esborrarà i es perdrà el contingut de la partició/unitat seleccionada.</string>

<string lang="ca" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">S'esborrarà tot el contingut de la partició on hi ha el sistema original.\n\nNota: Tot el contingut de la partició que s'esborrarà s'ha copiat a la seva partició de sistema oculta.</string>

<string lang="ca" key="WIPE_MODE_WARN">ATENCIÓ: Tingui en compte que si escull, per exemple, una neteja de 3 passades, el temps necessàri per xifrar la partició/unitat serà fins a 4 vegades més llarg. De la mateixa manera, si escull una neteja de 35 passades, serà fins a 36 vegades més gran (podria estar-hi setmanes).\n\nTanmateix, tingui en compte que la neteja no es farà un cop la partició/unitat estigui xifrada. Quan una partició/unitat està xifrada completament no s'hi escriuen dades no xifrades. Totes les dades que s'hi escriuen es xifren al vol a la memòria i només després s'escriuen al disc.\n\nSegur que vol utilitzar la neteja?</string>

<string lang="ca" key="WIPE_MODE_NONE">Cap (el més ràpid)</string>

<string lang="ca" key="WIPE_MODE_1_RAND">1 passada (dades aleatòries)</string>

<string lang="ca" key="WIPE_MODE_3_DOD_5220">3 passades (US DoD 5220.22-M)</string>

<string lang="ca" key="WIPE_MODE_7_DOD_5220">7 passades (US DoD 5220.22-M)</string>

<string lang="ca" key="WIPE_MODE_35_GUTMANN">35 passades ("Gutmann")</string>

<string lang="ca" key="SYS_MULTI_BOOT_MODE_TITLE">Número de sistemes operatius</string>

<string lang="ca" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ATENCIÓ: Els usuaris sense experiència no haurien d'intentar xifrar el Windows en una màquina amb arrencada múltiple.\n\nVol continuar?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Unitat d'arranc</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Aquest sistema operatiu està instal·lat a la partició d'arranc?\n\nNota: A vegades, el Windows no està instal·lat a la mateixa unitat que el gestor d'arranc de Windows (a la partició d'arranc). Si aquest és el cas, seleccioni 'No'.</string>

<string lang="ca" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">Actualment el VeraCrypt no suporta el xifratge de sistemes operatius que no arrenquin des de l'unitat ón estan instal·lats.</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Número d'unitats de sistema</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Quantes unitat contenen sistemes operatius?\n\n:Nota: Per exemple, si té algun sistema operatiu (Windows, Mac OS X, Linux, etc.) instal·lat a la unitat primària i algun altre sistema operatiu instal·lat a una unitat secundaria, seleccioni '2 o més'.</string>

<string lang="ca" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">El VeraCrypt no suporta el xifrat d'un disc sencer que contingui més d'un sistema operatiu.\n\nAlgunes solucions:\n\n- Pot xifrar un dels sitemes si torna enrera i triant l'opció de xifrar només una partició de sistema (en comptes de xifrar tota la unitat de sistema).\n\nTambé pot xifrar tota la unitat si mou alguns dels sistemes cap a altres unitats deixant només un sistema a la unitat que es vol xifrar.</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Diversos sistemes en una unitat</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Hi ha altres sistemes operatius instal·lats a la unitat on hi ha instal·lat el sistema operatiu actual?\n\nNota: Per exemple, si el sistema operatiu actual està instal·lat a la unitat #0, que conté diferents particions, i una de les particions conté un Windows i una altre un altre sistema operatiu (Windows, Mac OS X, Linux, etc.), seleccioni 'Si'.</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Gestor d'arrencada</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Hi ha algún carregador (o gestor) d'arrencada insal·lat al master boot record que no sigui el de Windows?\n\nNota: Per exemple, si la primera pista de l'unitat d'arranc conté GRUB, LILO, XOSL o d'altres gestors d'arranc, seleccioni 'Si'.</string>

<string lang="ca" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Arrencada múltiple</string>

<string lang="ca" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">El VeraCrypt no suporta l'arrencada múltiple quan no hi ha el gestor d'arranc del Windows al Master Boot Record.\n\nPossibles solucions:\n\n- Si utilitza un gestor d'arranc per arrancar Windows i Linux, mogui el gestor d'arranc (normalment el GRUB) des del MBR cap a una partició. Després torni a executar l'assistent i xifri la partició/unitat de sistema. Tingui en compte que el gestor d'arranc del VeraCrypt serà el gestor d'arranc primari i li permetrà executar el gestor d'arranc original com a gestor d'arranc secundari (prement Esc a la pantalla del gestor d'arranc del VeraCrypt) i podrà arrancar el Linux.</string>

<string lang="ca" key="WINDOWS_BOOT_LOADER_HINTS">Si el sistema operatiu actual està instal·lat a la partició d'arrant després de xifrar-la haurà d'introduïr la contrasenya correcta encara que vulgui engegar qualsevol altre sistema Windos sense xifrar (ja que comparteixen el mateix gestor d'arranc de Windows xifrat).\n\nEn canvi, si el sistema operatiu actual no està instal·lat a la partició d'arranc (o si el gestor d'arranc de Windows no s'utilitza per cap altre sistema), no serà necessari introduïr la contrasenya per arrencar altres sistemes operatius sense xifrar un cop xifrat -- haurà de prémer la tecla Esc per engegar el sistema sense xifrar (si hi ha més d'un sistema sense xifrar, l'haurà de triar).\n\nNota: Normalment, les versiones més noves de Windos s'instal·len a la partició d'arranc.</string>

<string lang="ca" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Xifrat de l'àrea protegida</string>

<string lang="ca" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Al final de moltes unitats hi ha una àrea generalment oculta al sistema operatiu (normalment anomenades àrees protegides). Tot i això, alguns programes poden llegir i escriure dades en aquestes arees.\n\nATENCIÓ: Alguns fabricants utilitzen aquestes àrees per emmagatzemar-hi eines i dades pel RAID, la recuperació del sistema, la configuració o el diagnòstic, etc. Si aquestes eines o dades han de ser accessibles abans d'arrencar, l'àrea protegida NO s'ha de xifrar (esculli 'No').\n\nVol que el VeraCrypt detecti i xifri qualsevol àrea oculta que trobi al final de la unitat de sistema?</string>

<string lang="ca" key="SYSENC_TYPE_PAGE_TITLE">Tipus de xifrat del sistema</string>

<string lang="cs" key="RESCUE_DISK_BURN_INFO_NONWIN_ISO_BURNER">DŮLEŽITÉ: Soubor musí být na CD/DVD zapsán jako obraz disku (ne jako jeden soubor). Pro více informací viz dokumentace k vašemu softwaru pro vypalování CD/DVD. Pokud nevlastníte žádný CD/DVD vypalovací software, který umí zapisovat ISO obrazy disku na CD/DVD, klikněte níže na odkaz pro stažení softwaru zadarmo.\n\n</string>

<string lang="cs" key="LAUNCH_WIN_ISOBURN">Spustit Microsoft Windows Disc Image Burner</string>

<string lang="cs" key="RESCUE_DISK_BURN_NO_CHECK_WARN">VAROVÁNÍ: Pokud jste Záchranný disk VeraCrypt vytvořili již v minulosti, nemůže být znovu použit pro tento systémový oddíl/disk, protože byl vytvořen pro odlišný hlavní klíč! Pokaždé když zašifrujete systémový oddíl/disk, musíte pro něj vytvořit nový Záchranný disk VeraCrypt, i když použijete stejné heslo.</string>

<string lang="cs" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Chyba: Nelze uložit nastavení systémového šifrování.</string>

<string lang="cs" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Nelze načíst předtest systémového šifrování.</string>

<string lang="cs" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Nelze spustit proces vytváření skrytého operačního systému.</string>

<string lang="cs" key="WIPE_MODE_TITLE">Čistící mód</string>

<string lang="cs" key="INPLACE_ENC_WIPE_MODE_INFO">Na některých úložných médiích mohou být data, která jsou přepsána jinými daty (např. když jsou data smazána), obnovena - s použitím technik jako např. magnetická mikroskopie. To se týká také dat, která jsou přepsána jejich zašifrovanou formou (což se děje, když VeraCrypt zašifrovává původně nezašifrovaný oddíl nebo disk). Podle některých studií a vládních publikací, obnovení dat se dá předejít (nebo to lze alespoň ztížit) přepsáním dat pseudonáhodnými a určitými ne-náhodnými daty, a to vícekrát. Pokud věříte, že by mohl váš protivník použít takovéto techniky k obnovení dat, která mají být smazána, zvažte použití jednoho z čistících módů (existující data NEBUDOU ztracena). Čištění NEBUDE provedeno po zašifrování oddílu/jednotky. Až bude oddíl/jednotka plně zašifrována, žádná další nezašifrovaná data na ní nebudou zapsána. Jakákoliv data na něj zapsaná, jsou nejprve zašifrována za běhu v paměti, a teprve potom jsou zašifrovaná data zapsána na disk.</string>

<string lang="cs" key="WIPE_MODE_INFO">Na některých úložných médiích mohou být data, která jsou přepsána jinými daty (např. když jsou data smazána), obnovena - s použitím technik jako např. magnetická mikroskopie. Podle některých studií a vládních publikací, obnovení dat se dá předejít (nebo to lze alespoň ztížit) přepsáním dat pseudonáhodnými a určitými ne-náhodnými daty, a to vícekrát. Pokud věříte, že by mohl váš protivník použít takovéto techniky k obnovení dat, která mají být smazána, zvažte použití jednoduchého nebo více-stopého módu mazání.\n\nPoznámka: Čím více stop použijete, tím déle bude vymazání dat trvat.</string>

<string lang="cs" key="DEVICE_WIPE_PAGE_TITLE">Čistím</string>

<string lang="cs" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nPoznámka: Proces čištění můžete přerušit, vypnout počítač, spustit skrytý systém znovu a pak proces obnovit (tento průvodce se spustí automaticky). Pokud ho ale přerušíte, celý proces čištění bude muset začít od začátku.</string>

<string lang="cs" key="DEVICE_WIPE_PAGE_INFO">\n\nPoznámka: Pokud proces čištění přerušte a pak se pokusíte o jeho obnovu, celý proces začne opět od začátku.</string>

<string lang="cs" key="CONFIRM_WIPE_ABORT">Chcete přerušit proces čištění?</string>

<string lang="cs" key="CONFIRM_WIPE_START">Varování: Obsah celého oddílu/zařízení bude vymazán a ztracen.</string>

<string lang="cs" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Obsah celého oddílu, kde je umístěn původní systém, bude vymazán.\n\nPoznámka: Obsah celého oddílu, který má být vymazán, byl zkopírován do tohoto skrytého systémového svazku.</string>

<string lang="cs" key="WIPE_MODE_WARN">VAROVÁNÍ: Pokud zvolíte například 3-stopý mód čištění, čas potřebný k zašifrování oddílu/disku bude 4x delší. Velmi podobně, pokud zvolíte 35-stopý mód čištění, bude 36x delší (to může trvat i několik týdnů).\n\nČištění ale NEBUDE provedeno po plném zašifrování oddílu/disku. Když je oddíl/disk úplně zašifrován, nejsou do něj zapsána žádná nezašifrovaná data. Jakákoliv data na něj zapsaná jsou nejdříve za běhu zašifrována v paměti a teprve pak jsou data (zašifrovaná) zapsána na disk (výkonnost NEBUDE ovlivněna).\n\nJste si jisti, že chcete použít mód čištění?</string>

<string lang="cs" key="WIPE_MODE_NONE">Žádný (nejrychlejší)</string>

<string lang="cs" key="WIPE_MODE_1_RAND">1-stopý (náhodná data)</string>

<string lang="cs" key="WIPE_MODE_3_DOD_5220">3-stopý (US DoD 5220.22-M)</string>

<string lang="cs" key="WIPE_MODE_7_DOD_5220">7-stopý (US DoD 5220.22-M)</string>

<string lang="cs" key="SYS_MULTI_BOOT_MODE_TITLE">Počet operačních systémů</string>

<string lang="cs" key="MULTI_BOOT_FOR_ADVANCED_ONLY">VAROVÁNÍ: Nezkušení uživatelé by se nikdy neměli pokoušet zašifrovat Windows ve vícesystémové bootovací konfiguraci.\n\nPokračovat?</string>

<string lang="cs" key="HIDDEN_OS_MULTI_BOOT">VeraCrypt podporuje vícesystémové bootování při vytvoření/použití skrytého operačního systému pouze za následujících podmínek:\n\n- Operační systém, který aktuálně běží, musí být nainstalován na bootovacím disku, který nesmí obsahovat žádné další operační systémy.\n\n- Operační systémy nainstalované na ostatních discích nesmí používat žádný bootovací zavaděč, který by byl umístěn na disku, kde je nainstalován systém, který nyní běží.\n\nJsou výše uvedené podmínky splněny?</string>

<string lang="cs" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt nepodporuje tuto více-bootovací konfiguraci, pokud vytváříte/používáte skryt operační systém.</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Bootovací disk</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Je momentálně běžící operační systém nainstalován na bootovacím disku?\n\nPoznámka: Někdy Windows nejsou nainstalovány na tom samém disku jako zavaděč Windows (bootovací oddíl). Je-li to tento případ, zvolte 'Ne'.</string>

<string lang="cs" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt momentálně nepodporuje šifrování operačního systému, který nebootuje z disku, kde je nainstalován.</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Počet systémových disků</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Kolik operačních systémů máte na discích?\n\nPoznámka: Např. pokud máte nainstalován libovolný operační systém (Windows, Mac OS X, Linux apod.) na primárním disku a nějaké další operační systémy nainstalované na sekundárním disku, zvolte '2 nebo více'.</string>

<string lang="cs" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt momentálně nepodporuje šifrování celého disku, který obsahuje více operačních systémů.\n\nMožná řešení:\n\n- Stále můžete zašifrovat jeden ze systémů, pokud se vrátíte a vyberete k zašifrování pouze jeden systémový oddíl (oproti šifrování celého systémového disku).\n\n- Eventuálně budete moci zašifrovat celý disk, přesunete-li některé ze systémů na jiné disky a ponecháte jen jeden systém na disku, který chcete zašifrovat.</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Více systémů nebo jeden disk</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Jsou na disku, kde běží momentálně operační systém, nainstalovány další operační systémy?\n\nPoznámka: Například pokud je nyní běžící operační systém nainstalován na disku #0, který obsahuje několik oddílů a pokud jeden z těchto oddílů obsahuje Windows a jiný oddíl obsahuje další operační systém (např. Windows, Mac OS X, Linux apod.), zvolte 'Ano'.</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows bootovací zavaděč</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Je v MBR (hlavní spouštěcí záznam) nainstalován non-Windows bootovací zavaděč (nebo bootovací manažer)?\n\nPoznámka: Například pokud první stopa bootovacího disku obsahuje GRUB, LILO, XOSL nebo jiný non-Windows bootovací manažer (nebo bootovací zavaděč), vyberte 'ANO'.</string>

<string lang="cs" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Vícesystémové bootování</string>

<string lang="cs" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt momentálně nepodporuje konfiguraci vícesystémového bootování, kde je non-Windows bootovací zavaděč nainstalován v hlavním spouštěcím záznamu.\n\nMožná řešení:\n\n- Použijete-li bootovacího manažera pro spuštění Windows a Linux, přesuňte bootovacího manažera (většinou GRUB) z hlavního spouštěcího záznamu do oddílu. Pak spusťte tohoto průvodce znovu a zašifrujte systémový oddíl/disk. Bootovací zavaděč VeraCryptu se stane vaším hlavním bootovacím manažerem a dovolí vám spustit původního bootovacího manažera hned poté (stisknutím klávesy Esc na obrazovce Bootovacího manažera VeraCrypt) a díky tomu budete moci nabootovat z operačního systému Linux.</string>

<string lang="cs" key="WINDOWS_BOOT_LOADER_HINTS">Je-li momentálně běžící systém nainstalován na bootovacím oddílu, po jeho zašifrování budete muset zadat správné heslo, i když budete chtít spustit jakýkoliv nezašifrovaný systém(y) Windows (budou sdílet stejný Bootovací zavaděč/manažer pro Windows).\n\nNaopak, pokud momentálně běžící operační systém není nainstalován na bootovacím oddíle (nebo pokud Bootovací zavaděč/manažer Windows není používán žádným jiným systémem), pak po zašifrování systému nebudete muset zadat správné heslo pro spuštění jiných nezašifrovaných systémů -- budete muset jen zmáčknout klávesu Esc pro spuštění nezašifrovaného systému (pokud je nezašifrovaných systémů více, budete muset také zadat, který se má spustit - v Bootovacím manažerovi VeraCrypt ).\n\nPoznámka: Běžně je na bootovacím oddíle nainstalován takový systém Windows, který byl nainstalován nejdříve.</string>

<string lang="cs" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Šifrování skryté chráněné oblasti</string>

<string lang="cs" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Na konci mnoha disků je oblast, která je běžně skryta operačnímu systému (takovéto oblasti se také říká skrytá chráněná oblast). Některé programy ale umí číst a zapisovat do/z těchto oblastí.\n\nVAROVÁNÍ: Někteří výrobci počítačů mohou tyto oblasti využívat k ukládání nástrojů a dat pro RAID, obnovu systému, nastavení systému, diagnostiku pro jiné účely. Pokud musí být takovéto nástroje nebo data přístupná před bootováním, skrytá oblast by NEMĚLA být zašifrována (výše vyberte 'NE').\n\nChcete, aby VeraCrypt detekoval a zašifroval takovouto skrytou oblast (pokud existuje) na konci systémového disku?</string>

<string lang="cs" key="SYSENC_TYPE_PAGE_TITLE">Typ systémového šifrování</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="da" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ADVARSEL: Hvis du allerede har oprettet en VeraCrypt Nødhjælps Disk tidligere, kan den ikke genbruges til denne system partition/drev fordi den blev oprettet med en anden hoved nøgle! Hver gang du krypterer en system partition/drev, skal du oprette en ny VeraCrypt Nødhjælps Disk for den, selv om du anvender samme kodeord.</string>

<string lang="da" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Fejl: Kan ikke gemme system krypterings indstillinger.</string>

<string lang="da" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Kan ikke påbegynde system krypterings første test.</string>

<string lang="da" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Kan ikke påbegynde processen med at oprette det skjulte operativsystem.</string>

<string lang="da" key="WIPE_MODE_TITLE">Udviske Tilstand</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="da" key="WIPE_MODE_NONE">Ingen (hurtigst)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="da" key="WIPE_MODE_3_DOD_5220">3-passager (US DoD 5220.22-M)</string>

<string lang="da" key="WIPE_MODE_7_DOD_5220">7-passager (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="da" key="SYS_MULTI_BOOT_MODE_TITLE">Antal Operativsystemer</string>

<string lang="da" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ADVARSEL: Uerfarne brugere bør aldrig forsøge at kryptere Windows i multi-boot konfigurationer.\n\nFortsæt?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="da" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drev</string>

<string lang="da" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Er det nuværende kørende operativsystem installeret på boot drevet?\n\nBemærk: Nogle gange er Windows ikke installeret på samme drev som Windows boot loader (boot partition). Hvis dette er tilfældet, vælg 'Nej'.</string>

<string lang="da" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt supporterer for tiden ikke kryptering af operativsystemer der ikke booter fra drevet hvorpå det er installeret.</string>

<string lang="da" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Antal System Drev</string>

<string lang="da" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Hvor mange drev indeholder et operativsystem?\n\nBemærk: For eksempel, hvis du har et operativsystem (f.eks. Windows, Mac OS X, Linux, osv.) installeret på dit primære drev og et andet operativsystem installeret på dit sekundære drev, vælg '2 eller flere'.</string>

<string lang="da" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt supporterer for tiden ikke kryptering af et helt drev der indeholder flere operativsystemer.\n\nMulige løsninger:\n\n- Du kan stadig kryptere et af systemerne hvis du går tilbage og vælger kun at kryptere en enkelt system partition (sat op imod at vælge at kryptere hele system drevet).\n\n- Alternativt, vil du være i stand til at kryptere hele drevet hvis du flytter nogel af systemerne til andre drev og kun beholder et system på det drev du ønsker at kryptere.</string>

<string lang="da" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Flere Systemer på et Drev</string>

<string lang="da" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Er der andre operativsystemer installeret på drevet hvorfra det nu kørende operativsystem er installeret?\n\nBemærk: For eksempel, hvis det nu kørende operativsystem er installeret på drevet #0, som indeholder flere partitioner, og hvis en af partitionerne indeholder Windows og en anden partition indeholder et operativsystem yderligere (f.eks. Windows, Mac OS X, Linux, osv.), vælg 'Ja'.</string>

<string lang="da" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Ikke-Windows Boot Loader</string>

<string lang="da" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Er der installeret en ikke-Windows boot loader (eller boot manager) i master boot record (MBR)?\n\nBemærk: For eksempel, hvis det første spor på boot drevet indeholder GRUB, LILO, XOSL, eller en anden ikke-Windows boot manager (eller boot loader), vælg 'Ja'.</string>

<string lang="da" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="da" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt supporterer for tiden ikke multi-boot konfigurationer hvor en ikke-Windows boot loader er installeret i Master Boot Record.\n\nMulige løsninger:\n\n- Hvis du anvender en boot manager til at boote Windows og Linux, flyt da boot manageren (typisk, GRUB) fra Master Boot Record til en partition. Start da dette hjælpeprogram igen og krypter system partition/drev. Bemærk at VeraCrypt Boot Loader vil blive din primære boot manager og det vil tillade dig at opstarte den originale boot manager (f.eks. GRUB) som din sekundære boot manager (ved at trykke på Esc i VeraCrypt Boot Loader skærmbilledet) og således vil du være i stand til at boote Linux.</string>

<string lang="da" key="WINDOWS_BOOT_LOADER_HINTS">Hvis det nuværende kørende operativsystem er installeret på boot partitionen, så vil du efter at have krypteret det, være nødt til at indtaste korrekt kodeord selv om du ønsker at starte et andet ukrypteret Windows system(er) (da de vil dele en krypteret Windows boot loader/manager).\n\nDerimod, hvis det nuværende kørende operativsystem ikke er installeret på boot partitionen (eller hvis Windows boot loader/manager ikke bliver brugt at noget andet system), så vil du efter at have krypteret dette system, ikke skulle indtaste korrekt kodeord for at boote det andet ukrypterede system(er) -- du vil kun skulle trykke på Esc tasten for at starte det ukrypterede system (hvis der er flere ukrypterede systemer, vil du også skulle vælge hvilket system der skal startes i VeraCrypt Boot Manager menuen).\n\nBemærk: Typisk er det tidligst installerede Windows system installeret på boot partitionen.</string>

<string lang="da" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Kryptering af værts beskyttet område</string>

<string lang="da" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Sidst på mange drev er der et område der normalt er skjult for operativsystemet (sådanne områder kaldes normalt Værts Beskyttede Områder). Det er dog muligt for nogle programmer at læse og skrive data til/fra disse områder.\n\nADVARSEL: Nogle computer fabrikanter kan bruge disse områder til at gemme værktøjer og data til RAID, system gendannelse, system setup, diagnostisering, eller andre formål. Hvis sådanne værtøjer eller data skal være tilgængelige før boot, bør det skjulte område IKKE krypteres (vælg 'Nej' ovenfor).\n\nØnsker du at VeraCrypt skal detektere og kryptere sådan et skjult område (hvis det findes) sidst på system drevet?</string>

<string lang="da" key="SYSENC_TYPE_PAGE_TITLE">Type af System Kryptering</string>

<string lang="de" key="LAUNCH_WIN_ISOBURN">Microsoft Windows ISO-Brennprogramm starten</string>

<string lang="de" key="RESCUE_DISK_BURN_NO_CHECK_WARN">Warnung: Wenn Sie bereits einen VeraCrypt Rettungsdatenträger in der Vergangenheit erstellt haben, dieser kann für dieses Systempartition/Laufwerk nicht wiederverwendet werden, da er für einen anderen Hauptschlüssel erstellt wurde! Sie müssen jedes mal wenn Sie eine Systempartition/ ein Systemlaufwerk verschlüsseln dafür einen neuen Rettungsdatenträger erstellen selbst wenn Sie das selbe Kennwort verwenden.</string>

<string lang="de" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Fehler: Es können die Einstellungen für die Systemverschlüsselung nicht gespeichert werden.</string>

<string lang="de" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Der Pre-Test für die Systemverschlüsselung konnte nicht initiiert werden.</string>

<string lang="de" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Der Vorgang für die Erstellung des Versteckten Betriebssystems kann nicht initiiert werden.</string>

<string lang="de" key="WIPE_MODE_TITLE">Sicher Löschen</string>

<string lang="de" key="INPLACE_ENC_WIPE_MODE_INFO">Bei einigen Typen von Speichermedien könnten Daten, die über- schrieben wurden, mithilfe der Magnetkraftmikroskopie wieder- hergestellt werden. Dies gilt auch für Daten, die in Ihrer verschlüs- selten Form überschrieben wurden (was passiert, wenn VeraCrypt erstmals unverschlüsselte Partitionen oder Laufwerke verschlüsselt). Einige Studien und öffentliche Publikationen geben an, dass die Wiederherstellung von überschriebenen Daten verhindert (oder zumindest erschwert) werden kann, indem die Daten mit pseudo- zufälligen und bestimmten nicht zufälligen Daten überschrieben werden. Wenn Sie glauben, dass ein Angreifer möglicherweise solche Techniken verwenden könnte um Ihre verschlüsselten Daten wieder- herzustellen, dann sollten Sie einen der Lösch-Modi wählen (vorhan- dene Daten gehen NICHT verloren). Das Löschen kann NICHT ausgeführt werden nachdem die Partition/ das Laufwerk verschlüsselt wurde. Dann werden alle Daten nämlich zuerst im Speicher verschlüsselt und erst dann auf den Datenträger geschrieben.</string>

<string lang="de" key="WIPE_MODE_INFO">Bei einigen Typen von Speichermedien kann mithilfe der Magnetkraftmikroskopie Daten, die von anderen Daten (z.B. wenn die Daten gelöscht sind) überschrieben wurden, wiederhergestellt werden. Einige Studien und öffentliche Publikationen geben an, dass die Wiederherstellung von überschrieben Daten verhindert werden kann (oder zumindest erschwert werden) in dem die Daten mit pseudozufälligen und bestimmten nicht zufälligen Daten überschrieben werden. Daher, wenn Sie der Meinung sind das ein Angreifer möglicherweise solche Techniken verwenden könnte um Ihre Daten wiederherzustellen die Sie verschlüsseln wollen, dann könnten Sie einen der Lösch-Modi wählen.\n\nHinweis: Je mehr Durchläufe Sie wählen, desto länger dauert das löschen der Daten.</string>

<string lang="de" key="DEVICE_WIPE_PAGE_TITLE">Löschen</string>

<string lang="de" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nHinweis: Sie können den Löschvorgang unterbrechen, fahren Sie den Computer herunter, starten Sie das versteckte System wieder und setzen dann den Vorgang fort (dieser Assistent wird automatisch gestartet). Wenn Sie ihn jedoch unterbrechen, dann muss der gesamte Löschvorgang von vorn beginnen.</string>

<string lang="de" key="DEVICE_WIPE_PAGE_INFO">\n\nHinweis: Wenn Sie den Löschvorgang unterbrechen und dann versuchen ihn fortzusetzen, so muss der gesamte Löschvorgang von vorn beginnen.</string>

<string lang="de" key="CONFIRM_WIPE_ABORT">Möchten Sie den Löschvorgang abbrechen?</string>

<string lang="de" key="CONFIRM_WIPE_START">Warnung: Der gesamte Inhalt der ausgewählten Partition/ des Laufwerkes wird gelöscht und geht verloren.</string>

<string lang="de" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Der gesamte Inhalt der Partition, auf der sich das Original System befindet, wird gelöscht.\n\nHinweis: Der gesamte Inhalt der Partition (der gelöscht werden soll) wurde auf diese Versteckte Systempartition kopiert.</string>

<string lang="de" key="WIPE_MODE_WARN">Warnung: Beachten Sie, wenn Sie z.B. 3 Durchgänge im Lösch-Modus auswählen, dass die erforderliche Zeit zum Verschlüsseln des Laufwerkes/ der Partition bis zu 4 mal länger werden kann. Wenn Sie den Modus mit 35 Durchgängen wählen, so kann es bis zu 36 Mal länger dauern (es könnte Wochen dauern).\n\nBeachten Sie jedoch, der Löschvorgang kann NICHT nicht ausgeführt werden, nachdem die Partition/ das Laufwerk vollständig verschlüsselt wurde. Wenn die Partition/ das Laufwerk vollständig verschlüsselt ist, dann werden keine unverschlüsselten Daten jemals darauf geschrieben. Alle die darauf zu schreibende Daten werden zuerst 'on-the-fly' im Speicher verschlüsselt und nur dann werden die (verschlüsselten) Daten auf den Datenträger geschrieben (damit wird die Leistung nicht beeinflusst).\n\nMöchten Sie den Lösch-Modus trotzdem verwenden?</string>

<string lang="de" key="WIPE_MODE_NONE">Ohne (am schnellsten)</string>

<string lang="de" key="WIPE_MODE_1_RAND">1-Durchgang (Zufalls Daten)</string>

<string lang="de" key="WIPE_MODE_3_DOD_5220">3-Durchgänge (US DoD 5220.22-M)</string>

<string lang="de" key="WIPE_MODE_7_DOD_5220">7-Durchgänge (US DoD 5220.22-M)</string>

<string lang="de" key="WIPE_MODE_35_GUTMANN">35-Durchgänge ("Gutmann")</string>

<string lang="de" key="SYS_MULTI_BOOT_MODE_TITLE">Anzahl der Betriebssysteme</string>

<string lang="de" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNUNG: Unerfahrene Benutzer sollten niemals versuchen Windows in einer Multiboot-Konfigurationen verschlüsseln.\n\nFortfahren?</string>

<string lang="de" key="HIDDEN_OS_MULTI_BOOT">Wenn Sie ein verstecktes Betriebsystem erstellen oder nutzen unterstützt VeraCrypt Mulit-Boot-Konfigurationen nur wenn die folgenden Bedingungen erfüllt sind:\n\n- Das derzeit laufende Betriebssystem muss auf dem Bootlaufwerk installiert sein welches keine weitere Betriebssysteme enthalten darf.\n\n- Betriebssysteme auf anderen Laufwerken dürfen keine Bootloader nutzen die auf dem selben Laufwerk liegen auf dem das derzeit aktive Betriebssystem installiert ist.\n\nSind die obigen Bedingungen erfüllt?</string>

<string lang="de" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt unterstützt diese Multi-Boot-Konfiguration nicht wenn ein verstecktes Betriebssystem erstellt/genutzt wird.</string>

<string lang="de" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Startlaufwerk</string>

<string lang="de" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Ist das zurzeit laufende Betriebssystem auf dem Boot-Laufwerk installiert?\n\nHinweis: Manchmal ist Windows nicht auf demselben Laufwerk installiert, auf den der Windows-Bootloader (Boot-Partition) installiert ist. Wenn das der Fall ist, wählen Sie 'Nein'.</string>

<string lang="de" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt unterstützt momentan das Verschlüsseln eines Betriebssystems, welches nicht von dem Laufwerk gestartet wird auf dem es installiert ist, nicht.</string>

<string lang="de" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Anzahl der Systemlaufwerke</string>

<string lang="de" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Wie viele Laufwerke enthalten ein Betriebssystem?\n\nHinweis: Beispielsweise, wenn Sie irgendein Betriebssystem (z.B. Windows, Mac OS X, Linux, etc.) auf dem primären Laufwerk und ein zusätzliches Betriebssystem auf einem sekundären Laufwerk installiert haben dann wählen Sie '2 oder mehr ' aus.</string>

<string lang="de" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt unterstützt derzeit nicht die Verschlüsselung eines ganzen Laufwerkes auf dem mehrere Betriebssysteme sind.\n\nMögliche Lösungen:\n\n- Sie können eines der Systeme verschlüsseln wenn Sie zurückgehen und sich für das verschlüsseln einer einzelnen Partition entscheiden (im Gegensatz zur Auswahl für das Verschlüsseln des gesamten Systemlaufwerkes).\n\n- Alternativ können Sie das ganze Laufwerk verschlüsseln wenn Sie einige der Systeme, bis auf das welches Sie verschlüsseln wollen, auf ein anderes Laufwerk verschieben. </string>

<string lang="de" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Mehrere Systeme auf einem Laufwerk</string>

<string lang="de" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Sind noch andere Betriebssysteme auf dem Laufwerk installiert, auf dem das z.Z. laufende Betriebssystem Installiert ist?\n\nHinweis: Beispielsweise wenn das aktuell laufende Betriebssystem auf dem Laufwerk #0 installiert ist, welches mehrere Partitionen enthält und eine dieser Partitionen enthält Windows, eine andere Partition enthält ein weiteres Betriebssystem (z. B. Windows, Mac OS X, Linux usw.), dann wählen Sie 'Ja'.</string>

<string lang="de" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Nicht-Windows Bootloader</string>

<string lang="de" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Ist statt dem Windows Bootloader ein anderer Bootloader (oder Bootmanager) im Master Boot Record (MBR) installiert?\n\nHinweis: Beispielsweise, wenn die erste Spur des Startlaufwerkes GRUB, LILO, XOSL, oder einen anderen Nicht-Windows Boot Manager (oder Bootloader) enthält, dann wählen Sie 'Ja'.</string>

<string lang="de" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="de" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt unterstützt momentan keine Multiboot - Konfigurationen auf dem ein Nicht-Windows-Bootloader im Master Boot Record installiert ist.\n\nMögliche Lösungen:\n\n- Wenn Sie einen Boot-Manager nutzen um Windows und Linux zu booten, dann verschieben Sie den Boot-Manager (normalerweise GRUB) vom Master Boot Record auf eine Partition. Dann starten Sie diesen Assistenten erneut und verschlüsseln die Systempartition/ das Laufwerk. HINWEIS: Der VeraCrypt Bootloader wird Ihr Primärer Boot-Manager werden, welcher es Ihnen erlaubt den originalen Boot-Manager (z.B. GRUB) als Sekundären Boot-Manager zu starten (ESC im VeraCrypt Bootloader-Bildschirm drücken), was es Ihnen ermöglicht Linux zu booten.</string>

<string lang="de" key="WINDOWS_BOOT_LOADER_HINTS">Wenn das aktuell ausgeführte Betriebssystem auf der Startpartition installiert ist, dann müssen Sie, nachdem Sie es verschlüsselt haben, immer das richtige Kennwort eingeben auch wenn Sie ein anderes unverschlüsseltes Windows System starten möchten(da diese sich einen einzigen verschlüsselten Windows Bootloader/Manager teilen).\n\nWenn im Gegensatz dazu das derzeit laufende Betriebssystem nicht auf der Startpartition installiert ist (oder wenn der Windows Bootloader/Manager nicht von allen anderen Systemen verwendet wird), dann müssen Sie nicht das korrekte Kennwort zum Starten der anderen unverschlüsselten Systeme eingeben, nachdem Sie dieses System verschlüsselt haben -- Sie müssen nur die ESC-Taste drücken um das unverschlüsselte System zu starten (wenn es mehrere unverschlüsselte Systeme gibt, dann müssen Sie im VeraCrypt Bootmanager wählen welches der Systeme gestartet werden soll).\n(Hinweis: Normalerweise ist das erste installierte Windows System auf der Startpartition installiert.)</string>

<string lang="de" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Verschl. des Host-geschützten Bereichs</string>

<string lang="de" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Am Ende vieler Laufwerke gibt es ein Bereich der normalerweise vom Betriebssystem versteckt wird (solche Bereiche werden als Host- geschützte Bereiche bezeichnet). Allerdings können manche Programme von/auf solche(n) Bereiche(n) lesen und schreiben.\n\nWARNUNG: Einige Computerhersteller verwenden möglicherweise solche Bereiche, um Tools und Daten für RAID, Systemwiederherstellung, Systeminstallation, Diagnose oder andere Zwecke zu speichern. Wenn solche Tools oder Daten vor dem Starten zugänglich sein müssen, dann sollte der versteckte Bereich nicht verschlüsselt werden (wählen Sie oben 'Nein').\n\nMöchten Sie das VeraCrypt einen solchen Bereich (falls vorhanden) am Ende des Systemlaufwerkes ermittelt und verschlüsselt?</string>

<string lang="de" key="SYSENC_TYPE_PAGE_TITLE">Art der System-Verschlüsselung</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO_NONWIN_ISO_BURNER">IMPORTANT: Note that the file must be written to the CD/DVD as an ISO disk image (not as an individual file). For information on how to do so, please refer to the documentation of your CD/DVD recording software. If you do not have any CD/DVD recording software that can write the ISO disk image to a CD/DVD, click the link below to download such free software.\n\n</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="el" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Σφάλμα: Αδυναμία αποθήκευσης ρυθμίσεων κρυπτογράφησης συστήματος.</string>

<string lang="el" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Αδυναμία αρχικοποίησης προεξέτασης κρυπτογράφησης συστήματος.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="el" key="WIPE_MODE_TITLE">Μέθοδος ασφαλούς διαγραφής</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="el" key="WIPE_MODE_NONE">Κανένα (γρηγορότερο)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="el" key="WIPE_MODE_3_DOD_5220">3 περάσματα (US DoD 5220.22-M)</string>

<string lang="el" key="WIPE_MODE_7_DOD_5220">7 περάσματα (US DoD 5220.22-M)</string>

<string lang="el" key="SYS_MULTI_BOOT_MODE_TITLE">Αριθμός λειτουργικών συστημάτων</string>

<string lang="el" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ΠΡΟΣΟΧΗ: Άπειροι χρήστες δεν πρέπει να επιχειρούν να κρυπτογραφήσουν τα Windows σε διαμορφώσεις πολλαπλής εκκίνησης.\n\nΣυνέχεια;</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="el" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Οδηγός εκκίνησης</string>

<string lang="el" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Είναι το τρέχων λειτουργικό σύστημα εγκατεστημένο στον οδηγό εκκίνησης;\n\nΣημείωση: Μερικές φορές τα Windows δεν είναι εγκατεστημένα στον ίδιο οδηγό με τον εκκινητή των Windows (διαμέρισμα εκκίνησης). Αν ισχύει αυτό, επιλέξτε 'Όχι'.</string>

<string lang="el" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">Το VeraCrypt προς το παρόν δεν υποστηρίζει κρυπτογράφηση λειτουργικού συστήματος που δεν εκκινεί απ'τον οδηγό που είναι εγκατεστημένο.</string>

<string lang="el" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Αριθμός οδηγών συστήματος</string>

<string lang="el" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Πόσοι οδηγοί περιέχουν λειτουργικό σύστημα;\n\nΣημείωση: Π.χ. αν έχετε ένα λειτουργικό (Windows, Mac OS X, Linux κλπ.) εγκατεστημένο στον πρωτεύοντα οδηγό και πρόσθετο λειτουργικό στον δευτερεύοντα, επιλέξτε '2 ή περισσότερα'.</string>

<string lang="el" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">Το VeraCrypt προς το παρόν δεν υποστηρίζει κρυπτογράφηση ολόκληρου οδηγού που περιέχει πολλά λειτουργικά συστήματα.\n\nΔυνατές λύσεις:\n\n- Μπορείτε να κρυπτογραφήσετε ένα από τα συστήματα αν πάτε πίσω και επιλέξετε να κρυπτογραφήσετε μόνο ένα διαμέρισμα συστήματος (αντί να επιλέξετε κρυπτογράφηση όλου του οδηγού συστήματος).\n\n- Εναλλακτικά, μπορείτε να κρυπτογραφήσετε όλον τον οδηγό αν μετακινήσετε μερικά από τα συστήματα του σε άλλους οδηγούς και αφήσετε μόνο ένα.</string>

<string lang="el" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Πολλά συστήματα σε έναν οδηγό</string>

<string lang="el" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Υπάρχουν άλλα λειτουργικά συστήματα εγκατεστημένα στον οδηγό που είναι εγκατεστημένο το τρέχον λειτουργικό;\n\nΣημείωση: Π.χ. αν το τρέχων λειτουργικό είναι εγκατεστημένο στον οδηγό #0, που περιέχει διαμερίσματα και αν ένα από αυτά περιέχει τα Windows και ένα άλλο περιέχει άλλο λειτουργικό (Windows, Mac OS X, Linux κλπ.), επιλέξτε 'Ναι'.</string>

<string lang="el" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Μη-Windows εκκινητής</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="el" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Πολλαπλής εκκίνησης</string>

<string lang="el" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">Το VeraCrypt προς το παρόν δεν υποστηρίζει διαμορφώσεις πολλαπλής εκκίνησης στις οποίες μη-Windows εκκινητής είναι εγκατεστημένος στο Βασικό Αρχείο Εκκίνησης (MBR).\n\nΔυνατές λύσεις:\n\n- Αν χρησιμοποιείτε διαχειριστή εκκίνησης για τα Windows και το Linux, μετακινήστε τον (συνήθως τον GRUB) απ'το MBR σε ένα διαμέρισμα. Έπειτα ξαναεκκινήστε αυτόν τον Οδηγό και κρυπτογραφήστε το διαμέρισμα/οδηγό του συστήματος. Σημειώστε ότι ο Εκκινητής VeraCrypt θα γίνει ο πρωτεύων διαχειριστής εκκίνησης σας και θα σας επιτρέπει να εκκινήσετε τον πρωταρχικό διαχειριστή (π.χ. GRUB) ως δευτερεύοντα (πιέζοντας Esc στην οθόνη του Εκκινητή VeraCrypt) και έτσι να εκκινήσετε το Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="es" key="LAUNCH_WIN_ISOBURN">Lanzar el Grabador de Imágenes de Disco de Windows</string>

<string lang="es" key="RESCUE_DISK_BURN_NO_CHECK_WARN">AVISO: ¡Si ya ha creado un Disco de Rescate VeraCrypt en el pasado, no debe ser reutilizado para esta partición/unidad del sistema porque fue creado para una clave maestra diferente! Cada vez que cifre una partición/unidad del sistema, debe crear un nuevo Disco de Rescate VeraCrypt incluso si ha usado la misma contraseña.</string>

<string lang="es" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: No se puede guardar la configuración del cifrado del sistema.</string>

<string lang="es" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">No se puede iniciar la prueba del cifrado del sistema.</string>

<string lang="es" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">No se puede iniciar el proceso de creación del sistema operativo oculto.</string>

<string lang="es" key="WIPE_MODE_TITLE">Modo de borrado</string>

<string lang="es" key="INPLACE_ENC_WIPE_MODE_INFO">En algunos medios de almacenamiento, cuando los datos son sobreescritos por otros datos, es posible recuperar la información sobreescrita con técnicas como el microscopio de fuerza magnética. Esto también se aplica a datos sobreescritos por su versión cifrada (lo que ocurre cuando VeraCrypt inicialmente cifra una partición o unidad no cifrada). Según estudios y publicaciones gubernamentales, se puede evitar (o dificultar) la recuperación de esos datos sobreescribiéndolos con datos no aleatorios y pseudoaleatorios un número suficiente de veces. Por tanto, si cree que un adversario podría usar estas técnicas para recuperar los datos que pretende cifrar, puede seleccionar uno de los modos de borrado (los datos existentes NO se perderán). Tenga en cuenta que el borrado NO se hará después de que la partición/unidad esté cifrada. Cuando lo esté, no se escribirá en ella ningún dato sin cifrar. Cualquier dato que se vaya a escribir se cifra al vuelo en memoria primero, y sólo entonces (ya cifrado) es escrito al disco.</string>

<string lang="es" key="WIPE_MODE_INFO">En algunos tipos de medios de almacenamiento, cuando los datos son sobreescritos por otros datos (p.e. cuando los datos son eliminados), es posible recuperar la información sobreescrita usando técnicas como el microscopio de fuerza magnética. Según algunos estudios y publicaciones gubernamentales, se puede evitar (o dificultar) la recuperación de datos sobreescritos sobreescribiendo los datos con datos no aleatorios seguros y pseudoaleatorios un número suficiente de veces. Por tanto, si cree que un adversario podría usar estas técnicas para recuperar los datos que van a ser borrados, puede seleccionar uno de los modos de borrado multi-pasada.\n\nNota: Cuantas más pasadas de borrado utilize, más se alargará el borrado de datos.</string>

<string lang="es" key="DEVICE_WIPE_PAGE_TITLE">Borrando</string>

<string lang="es" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNota: Puede interruptir el proceso de borrado, apagar su ordenador, iniciar el sistema operativo oculto de nuevo y reanudar el proceso (este asistente se lanzará automáticamente). Sin embargo, si lo interrumpe, el proceso de borrado tendrá que comenzar desde el principio.</string>

<string lang="es" key="DEVICE_WIPE_PAGE_INFO">\n\nNota: Si interrumpe el proceso de borrado y luego intenta reanudarlo, el proceso entero tendrá que comenzar desde el principio.</string>

<string lang="es" key="CONFIRM_WIPE_ABORT">¿Desea abortar el proceso de borrado?</string>

<string lang="es" key="CONFIRM_WIPE_START">Aviso: El contenido entero de la partición/dispositivo seleccionado será borrado y se perderá.</string>

<string lang="es" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">El contenido entero de la partición donde reside el sistema original será borrado.\n\nNota: El contenido entero de la partición que va a ser borrada ha sido copiado a la partición de este sistema oculto.</string>

<string lang="es" key="WIPE_MODE_WARN">AVISO: Tenga en cuenta que cuando elige p.e. el modo de borrado de 3 pasadas, el tiempo necesario para cifrar la partición/unidad será unas 4 veces mayor. Asimismo, si elige el modo de 35 pasadas, tardará unas 36 veces más (podría incluso tardar varias semanas).\n\nSin embargo, recuerde que el borrado NO se realizará después de que la partición/unidad esté cifrada por completo. Cuando la partición/unidad esté cifrada por completo, no se escribirá en ella ningún dato. Cualquier dato que se escriba será cifrado al vuelo en memoria primero, y sólo entonces el dato (cifrado) será escrito en el disco (por lo tanto el rendimiento NO será afectado).\n\n¿Seguro que desea usar el modo de borrado?</string>

<string lang="es" key="WIPE_MODE_NONE">Ninguno (El más rápido)</string>

<string lang="es" key="WIPE_MODE_1_RAND">1 pasada (datos aleatorios)</string>

<string lang="es" key="WIPE_MODE_3_DOD_5220">3 pasadas (US DoD 5220.22-M)</string>

<string lang="es" key="WIPE_MODE_7_DOD_5220">7 pasadas (US DoD 5220.22-M)</string>

<string lang="es" key="WIPE_MODE_35_GUTMANN">35 pasadas ("Gutmann")</string>

<string lang="es" key="SYS_MULTI_BOOT_MODE_TITLE">Número de Sistemas Operativos</string>

<string lang="es" key="MULTI_BOOT_FOR_ADVANCED_ONLY">AVISO: Los usuarios sin experiencia nunca deberían intentar cifrar Windows en configuraciones multi-arranque.\n\n¿Continuar?</string>

<string lang="es" key="HIDDEN_OS_MULTI_BOOT">Al crear/usar un sistema operativo oculto, VeraCrypt soporta configuraciones multi-arranque sólo cuando se cumplen las siguientes condiciones:\n\n- El sistema operativo en ejecución debe estar instalado en la unidad de arranque, la cual no debe contener ningún otro sistema operativo.\n\n- Los sistemas operativos instalados en otras unidades no deben usar ningún cargador de arranque residente en la unidad en la que está instalado el sistema operativo en ejecución.\n\n¿Se cumplen las condiciones mencionadas?</string>

<string lang="es" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt no soporta esta configuración multi-arranque al crear/usar un sistema operativo oculto.</string>

<string lang="es" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Unidad de Arranque</string>

<string lang="es" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">¿El sistema operativo en ejecución está instalado en la unidad de arranque?\n\nNota: A veces, Windows no está instalado en la misma unidad que el cargador de arranque de Windows (partición de arranque). Si ese es el caso, seleccione 'No'.</string>

<string lang="es" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt actualmente no soporta cifrar un sistema operativo que no arranque desde la unidad donde está instalado.</string>

<string lang="es" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Número de Unidades de Sistema</string>

<string lang="es" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">¿Cuántas unidades contienen un sistema operativo?\n\nNota: Por ejemplo, si tiene cualquier sistema operativo (Windows, Mac OS X, Linux, etc.) instalado en su unidad primaria y cualquier sistema operativo adicional instalado en su unidad secundaria, seleccione '2 o más'.</string>

<string lang="es" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt actualmente no soporta cifrar una unidad entera que contiene varios sistemas operativos.\n\nPosibles soluciones:\n\n- Puede cifrar uno de los sistemas si vuelve atrás y elige cifrar sólo una partición de sistema (en lugar de elegir el cifrado de la unidad del sistema entera).\n\n- Alternativamente, puede cifrar la unidad entera si mueve algunos de los sistemas a otras unidades dejando sólo un sistema en la unidad que quiere cifrar.</string>

<string lang="es" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Varios sistemas en una única unidad</string>

<string lang="es" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">¿Hay algún otro sistema operativo instalado en la unidad en la que el sistema operativo en ejecución está instalado?\n\nNota: Por ejemplo, si el sistema operativo en ejecución está instalado en la unidad #0, que contiene varias particiones, y si una de las particiones contiene Windows y otra contiene cualquier sistema operativo adicional (Windows, Mac OS X, Linux, etc.), seleccione 'Sí'.</string>

<string lang="es" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Cargador de Arranque No-Windows</string>

<string lang="es" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">¿Hay un cargador de arranque no-Windows (o administrador de arranque Windows) instalado en el Master Boot Record (MBR)?\n\nNota: Por ejemplo, si la primera pista de la unidad de arranque contiene GRUB, LILO, XOSL, o algún otro administrador de arranque (o cargador de arranque) no-Windows, seleccione 'Sí'.</string>

<string lang="es" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Arranque</string>

<string lang="es" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt actualmente no soporta configuraciones multi-arranque cuando un cargador de arranque no-Windows está instalado en el MBR.\n\nSoluciones posibles:\n\n- Si usa un administrador de arranque para arrancar Windows y Linux, mueva el administrador (normalmente GRUB) desde el MBR a una partición. Luego inicie este asistente otra vez y cifre la partición/unidad del sistema. Recuerde que el Cargador de Arranque VeraCrypt se convertirá en su administrador de arranque primario y le permitirá lanzar el administrador original (p.e. GRUB) como su administrador de arranque secundario (pulsando Esc en la pantalla del Cargador de Arranque VeraCrypt) y así podrá arrancar Linux.</string>

<string lang="es" key="WINDOWS_BOOT_LOADER_HINTS">Si el sistema operativo en ejecución está instalado en la partición de arranque, después de cifrarlo necesitará introducir la contraseña correcta incluso para iniciar cualquier otro sistema Windows no cifrado (ya que ambos compartirán un único cargador/administrador de arranque cifrado).\n\nPor el contrario, si el sistema operativo en ejecución no está instalado en la partición de arranque (o si el cargador/administrador de arranque de Windows no es usado por ningún otro sistema), después de cifrarlo no necesitará introducir la contraseña correcta para arrancar otros sistemas no cifrados -- sólo tendrá que pulsar Esc para iniciar el sistema no cifrado (si hay más de uno, tendrá que elegir cuál desea iniciar desde el menú del Administrador de Arranque VeraCrypt).\n\nNota: Normalmente, el primer sistema Windows instalado es el que está instalado en la partición de arranque.</string>

<string lang="es" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Cifrado del Área Protegida del Anfitrión</string>

<string lang="es" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Al final de muchos dispositivos existe un área que normalmente está oculta al sistema operativo (estas áreas son llamadas Áreas Protegidas del Anfitrión, o Host Protected Areas). Sin embargo, algunos programas pueden leer y escribir datos de/a estas áreas.\n\nAVISO: Algunos fabricantes de ordenadores pueden usar estas áreas para almacenar herramientas y datos para RAID, recuperación del sistema, instalación del sistema, diagnóstico u otros propósitos. Si estas herramientas o datos deben ser accesibles antes de arrancar, el área oculta NO debería ser cifrada (elija 'No' a continuación).\n\n¿Desea que VeraCrypt detecte y cifre ese área oculta (si existe) al final de la unidad del sistema?</string>

<string lang="es" key="SYSENC_TYPE_PAGE_TITLE">Tipo de Cifrado del Sistema</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="eu" key="LAUNCH_WIN_ISOBURN">Micrsoft Windows-en Disko Irudien Grabatzailea abiatu</string>

<string lang="eu" key="RESCUE_DISK_BURN_NO_CHECK_WARN">KONTUZ: Dagoeneko VeraCrypt Salbatze Diska bat sortu baduzu, ezin da sistemaren partizio/diska honetan berrerabili gako nagusi ezberdin batentzako sortu zelako. Sistemaren partizio/unitate bat zifratzen duzun bakoitzean, VeraCrypt Salbatze Diska berria sortu behar duzu pasahitz berdina badute ere.</string>

<string lang="eu" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Errorea: Sistemaren zifratze ezaugarriak ezin dira gorde.</string>

<string lang="eu" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Ezin da sistemaren zifratzeko aurreproba hasi.</string>

<string lang="eu" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Ezin izan da ezkutuko sistema eragilearen prozesua hasi.</string>

<string lang="eu" key="WIPE_MODE_TITLE">Ezabatze modua</string>

<string lang="eu" key="INPLACE_ENC_WIPE_MODE_INFO">Zeinbait memoria gailuetan, datu batzuk beste batzuen gainetik idazten direnean, posiblea da datu zaharrak berreskuratzea indar magnetikoen mirkoskopia erabiliz. Hau ere aplikatzen da euren datu zifratuengatik ordezkatutako datuei (hau gertatzen da VeraCrypt hasieran zifratu gabeko unitatea edo partizioa zifratzen duenean). Zenbait ikerketa eta gobernuaren txosten batzuen arabera, gainetik idatzitako datuen berreskuratzea eragotzi (edo asko zaildu) daiteke datua originalak ausazko datuekin eta ausazkoak ez diren datu batzuekin zenbait alditan berridazten baldin badira. Horregatik, arerio batek zure datuak berreskuratzeko teknika horiek erabili ditzakela uste baldin baduzu, pasatze anitzeko ezabatze moduetako bat aukeratu nahi izango duzu (dauden datuak EZ dira galduko). Ohartu zaitez ezabatze prozesua EZ dela egingo partizioa/unitatea zifratu eta gero. Partizio/unitatea guztiz zifratuta dagoenean, ez da bertan zifratu gabeko daturik idatziko. Idazten diren datu guztiak, lehendabizi memorian bertan zifratuko dira eta gero datuak (zifraturik) diskan idatziko dira.</string>

<string lang="eu" key="WIPE_MODE_INFO">Zeinbait memoria gailuetan, datu batzuk beste batzuen gainetik idazten direnean (hau da, datuak ezabatzen direnean), posiblea da datu zaharrak berreskuratzea indar magnetikoen mirkoskopia erabiliz. Zenbait ikerketa eta gobernuaren txosten batzuen arabera, gainetik idatzitako datuen berreskuratzea eragotzi (edo asko zaildu) daiteke datua originalak ausazko datuekin eta ausazkoak ez diren datu batzuekin zenbait alditan berridazten baldin badira. Horregatik, arerio batek zure datuak berreskuratzeko teknika horiek erabili ditzakela uste baldin baduzu, pasatze anitzeko ezabatze moduetako bat aukeratu nahi izango duzu.\n\nOharra: Kontutan izan ezazu zenbat eta pasatze gehiago, orduan eta denbora gehiago behar izango duzula datuak ezabatzeko.</string>

<string lang="eu" key="DEVICE_WIPE_PAGE_TITLE">Ezabatzen</string>

<string lang="eu" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nOharra: Ezabatze prozesua eten dezakezu, zure ordenagailua itzali, ezkutuko sistema berriro abiatu eta prozesua jarraitu (laguntzaile hau automatikoki hasiko da). Hala ere, eteten baduzu, ezabatze prozesu guztia berriro hasieratik hasi beharko da.</string>

<string lang="eu" key="DEVICE_WIPE_PAGE_INFO">\n\nOharra: Ezabatze prozesua eten egiten baduzu eta gero hura jarraitzen saiatzen bazara, prozesu guztia berriz hasieratik hasiko da.</string>

<string lang="eu" key="CONFIRM_WIPE_ABORT">Ezabatze prozesua bertan behera uzti nahi al duzu?</string>

<string lang="eu" key="CONFIRM_WIPE_START">Kontuz: Aukeratutako partizioaren/gailuaren edukia ezabatu eta galdu egingo da.</string>

<string lang="eu" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Jatorrizko sistema dagoen partizioaren eduki osoa ezabatuko da.\n\nOharra: Ezabatuko den partizioaren eduki guztiak ezkutuko sistemaren partziora kopiatu dira.</string>

<string lang="eu" key="WIPE_MODE_WARN">KONTUZ: Ohartu zaitez, adibidez, 3 pasatzeko ezabatze modua aukeratzen baduzu, partizioa/unitatea zifratzeko behar den denbora 4 aldiz luzeagoa izango da. Beste adibide bat, 35 pasatzeko ezabatze modua aukeratzen baduzu 36 aldiz denbora gehiago behar izango du (asteak eman ditzake).\n\nHala ere, kontutan izan ezazu ezabatze prozesua EZ dela egingo partizioa/unitatea guztiz zifratuta egon eta gero. Partizio/unitatea guztiz zifratuta dagoenean, ez da bertan zifratu gabeko daturik idatziko. Idazten diren datu guztiak, lehendabizi memorian bertan zifratuko dira eta gero zifratutako datuak diskan idatziko dira (beraz errendimenduan EZ du eraginik izango).\n\nZiur zaude ezabatze modu hori erabili nahi duzula?</string>

<string lang="eu" key="WIPE_MODE_NONE">Ezer (azkarrena)</string>

<string lang="eu" key="WIPE_MODE_1_RAND">pasatze-1 (ausazko datuak)</string>

<string lang="eu" key="WIPE_MODE_3_DOD_5220">3-pasatze (US DoD 5220.22-M)</string>

<string lang="eu" key="WIPE_MODE_7_DOD_5220">7-pasatze (US DoD 5220.22-M)</string>

<string lang="eu" key="WIPE_MODE_35_GUTMANN">35-pasatze ("Gutmann")</string>

<string lang="eu" key="SYS_MULTI_BOOT_MODE_TITLE">Sistema Eragile Kopurua</string>

<string lang="eu" key="MULTI_BOOT_FOR_ADVANCED_ONLY">KONTUZ: Esperientziarik gabeko erabiltzaileek ez lirateke Windows zifratzen saiatu behar hasieraketa-anitzeko konfigurazioekin.\n\nJarraitu?</string>

<string lang="eu" key="HIDDEN_OS_MULTI_BOOT">Ezkutuko sistema eragile bat sortu/erabiltzerakoan, VeraCrypt-ek abiaketa-anitza hurrengo kasuetan onartzen du bakarrik :\n\n- Orain martxan dagoen sistema eragilea abiatze unitatean instalatuta egon behar du, eta bertan dagoen sistema eragile bakarra izan behar du.\n\n- Beste unitateetan dauden sistema eragileek ezin dute martxan dagoen sistema eragilearen unitatean dagoen hasieraketa kargatzailea erabili.\n\nGoiko kondizioak betetzen al dira?</string>

<string lang="eu" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">TryeCrypt-ek ezu du abiatze anitz konfigurazio hau onartzen ezkutuko sistema eragilea sortu edo erabiltzerakoan.</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Abiatze Unitatea</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Orain martxan datoen sistema eregilea hasieraketa unitatean instalatuta al dago?\n\nOharra: batzuetan Windows ez dago Windows hasieraketa kargatzailearen partizio berean instalatuta (hasieraketa partizioa). Kasu hori gertatzen bada, 'Ez' aukeratu.</string>

<string lang="eu" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">Momentuz VeraCrypt-ek ez du onartzen abiatzen den unitatean instalatuta ez dagoen sistema eragile bat zifratzea.</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Sistemaren Unitate Kopurua</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Zenbat unitate sistema eragilea daukate?\n\nOharra: Adibidez, unitate nagusian edozein sistema eragile (adib.: Windows, Mac OS X, Linux e.a.) instalatuta baduzu eta beste edozein unitate batean sistema eragile bat instalatuta badago, '2 edo gehiago' aukeratu ezazu.</string>

<string lang="eu" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt-ek ez du onartzen unitate osoa zifratzea sistema eragile bat baino gehiago dituzten unitateetan.\n\nKonpoketak:\n\n- Sistemetako bat zifratu dezakezu atzera bazoaz eta sistemaren partizioa zifratzea aukeratzen baduzu (sistemaren unitate osoa zifratu ordez).\n\n- Unitate osoa zifratu ahal izango duzu sistema batzuk beste unitate batzuetara mugitu eta sistema bakarra uzten baduzu zifratu nahi duzun unitatean.</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Sistema Anitzak Unitate Bakarrean</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Beste sistema eragilerik instalatuta al dago orain martxan dagoen sistema eragilea instalatuta dagoen unitatean?\n\nOharra:Adibidez, orain martxan dagoen sistema eragilea #0 unitatean instalatuta badago, zein partizio bat baino gehiago daukan, eta partizio horietako bat Windows badauka eta beste partizio bat beste edozein sistema eragilea badauka (adib. Windows, Mac OS X, Linux, etc.), 'Bai' aukeratu ezazu.</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Windows ez den Hasieraketa Kargatzailea</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Windowsekoa ez den hasieraketa kargatzailea (edo kudeatzailea) hasieraketa erregistro nagusian (MBR) instalatuta al dago?\n\nAdibidez, hasieraketa unitatearen hasieran GRUB, LILO, XOSL edo bestelako Windowsekoak ez diren hasieraketa kudeatzailerik (edo kargatzailerik) badago, 'Bai' aukeratu ezazu.</string>

<string lang="eu" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Abiatze-Anitza</string>

<string lang="eu" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt-ek ez ditu onartzen hasieraketa anitzeko konfigugurazioak hasieraketa erregistro nagusian (MBR) Windowsekoa ez den hasieraketa kargatzaile bat instalatuta badago.\n\nIrtenbideak:\n\n- Hasieraketa kudeatzaile bat erabiltzen baduzu Windows eta Linux habiatzeko, hasieraketa kudeatzailea (normalean, GRUB) hasieraketa erregistro nagusitik (MBR) partizio batera mugitu ezazu. Ondoren laguntzaile hau berriz abiatu ezazu eta sistemaren partizio/unitatea zifratu ezazu. Ohartu zaitez VeraCrypt Hasieraketa Kargatzailea lehen mailako hasieraketa kudeatzailea bihurtuko dela eta hasieraketa kudeatzaile originala (adib. GRUB) abiatzen utziko dizula bigarren mailako hasieraketa kudeatzaile bat bezala (Esc salatuz VeraCrypt Hasieraketa Kargatzailearen lehioan) eta hortik Linux abiatu ahal izango duzu..</string>

<string lang="eu" key="WINDOWS_BOOT_LOADER_HINTS">Martxan dagoen sistema eragilea hasieraketa partizioan instalatuta badago, orduan, zifratu eta gero, pasahitz zuzena sartu behar izango duzu nahiz eta zifratu gabeko beste edozein Windows sistema abiatu nahi izan (zifratutako Windows hasieraketa kargatzaile/kudeatzaile bera erabiltzen dutelako).\n\nBeste aldetik, martxan dagoen sistema eragilea hasieraketa partizioan instalatuta ez badago (edo Windows hasieraketa kargatzaile/kudeatzailea hark bakarrik erabiltzen badu), orduan, sistema hau zifratu eta gero, zifratu gabeko beste sistemetara sartzeko ez duzu pasahitz zuzena sartu behar izango. Bakarrik 'Esc' tekla sakatuz zifratu gabeko sistema abiatuko da (zifratu gabeko sistema anitz badaude, baita ze sistema abiatu nahi duzun aukeratu behar izango duzu VeraCrypt Hasieraketa Kudeatzailearen menuan).\n\nOharra: Ohikoena, lehendabizi instalatu zen Windows sistema hasieraketa partizioan instalatuta dagoena izaten da.</string>

<string lang="eu" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Ostalariak Babestutako Gunea-ren Zifraketa</string>

<string lang="eu" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Unitate askoren bukaeran, normalean sistema eragilearentzat ezkutuan dagoen gune bat egoten da (gune horiei Ostalariak Babestutako Guneak deritze). Hala ere, programa batzuk gune horietan datuak idatzi eta irakurri ditzakete.\n\nKONTUZ: Zenbait ordenagailu ekoizleek gune horiek RAID-arentzat, sistema leheneratzeko, sistema konfiguratzeko, diagnosia egiteko eta beste asmoetarako datu eta tresnak gordetzeko erabiltzen dituzte. Datu edo tresna horiek abiatu aurretik eskuragarri egon behar badira, ezkutuko gunea EZ da zifratuko (goian 'Ez' aukeratu ezazu).\n\nVeraCrypt-ek unitatearen bukaeran dagoen ezkutuko gune hori aurkitu eta (baldin badago) zifratzea nahi al duzu??</string>

<string lang="eu" key="SYSENC_TYPE_PAGE_TITLE">Sistemaren Zifratze Mota</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="fi" key="LAUNCH_WIN_ISOBURN">Käynnistä Microsoft Windows Levy Imagen Poltto</string>

<string lang="fi" key="RESCUE_DISK_BURN_NO_CHECK_WARN">VAROITUS: Jos olet jo luonut VeraCrypt Pelastuslevyn aiemmin, sitä ei voida uudelleen käyttää tälle järjestelmäosiolle/asemalle koska se on luotu eri pääavaimelle! Joka kerta kun salaat osion/levyn, sinun täytyy luoda uusi VeraCrypt Pelastuslevy vaikka käyttäisitkin samaa salasanaa.</string>

<string lang="fi" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Virhe: Järjestelmän salauksen asetuksia ei voitu tallentaa.</string>

<string lang="fi" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Järjestelmä salauksen esitestiä ei voitu aloittaa.</string>

<string lang="fi" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Ei voida tunnistaa piilotetun käyttöjärjestelmän tapahtumaa.</string>

<string lang="fi" key="WIPE_MODE_TITLE">Tyhjennys Tila</string>

<string lang="fi" key="INPLACE_ENC_WIPE_MODE_INFO">Joissakin tyypeissä tallennus medioita, kun dataa ylikirjoitetaan toisella datalla, on mahdollista palauttaa ylikirjoitettu data käyttäen sellaisia tekniikoita kuin magneettisesti pakotettu mikrokopiointi. Tämä myös sallii data ylikirjoituksen salatussa muodossa (mikä tapahtuu kun VeraCrypt alustaessa salakirjoittaa salaamattoman osion tai aseman). Joiden ohjeiden ja julkaisujen mukaan, palautus ylikirjoitetulle datalle voidaan estää (tai tehdä hyvin vaikeaksi) ylikirjoittamalla dataa epäaitosatunnaisesti ja tietyllä ei-satunnaisdataa useamman kerran. Siksi, jos uskot että vastustaja saattaisi mahdollisesti käyttää tällaisia tekniikoita palauttaakseen datan jonka aiot salata, sinun tulee valita pyyhintä tila (olemassa oleva data EI häviä). Huomioi että pyyhintää EI suoriteta osion/aseman salauksen jälkeen. Kun osio/asema on täysin salattu, salaamaton data kirjoitetaan sille. Mikä tahansa kirjoitettu data ensiksi salataan lennossa muistissa ja ainoastaan sitten se (salattu) data kirjoitetaan levylle.</string>

<string lang="fi" key="WIPE_MODE_INFO">Joissakin tyypeissä tallennus medioita, kun dataa ylikirjoitetaan toisella datalla, (esim. kun data pyyhitään pois), on mahdollista palauttaa ylikirjoitettu data käyttäen sellaisia tekniikoita kuin magneettisesti pakotettu mikrokopiointi. Joiden ohjeiden ja julkaisujen mukaan, palautus ylikirjoitetulle datalle voidaan estää (tai tehdä hyvin vaikeaksi) ylikirjoittamalla dataa epäaitosatunnaisesti ja tietyllä ei-satunnaisdataa useamman kerran. Siksi, jos uskot että vastustaja saattaisi mahdollisesti käyttää tällaisia tekniikoita palauttaakseen datan jonka olet poistamassa, sinä voit haluta valita jonkin moniohitus (multi-pass) pyyhintä tilan.\n\nHuomioi: Mitä enemmin pyyhintä ohitusta käytät, sitä kauemmin kestää datan pyyhintä.</string>

<string lang="fi" key="DEVICE_WIPE_PAGE_TITLE">Pyyhi</string>

<string lang="fi" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nHuomioi: Voit keskeyttää pyyhintä tehtävän, sulkemalla tietokoneesi, käynnistämällä piilotetun järjestelmän uudelleen ja sitten uudelleen käynnistämällä tehtävän (tämä opastus käynnistetään automaattisesti). Kuitenkin, jos keskeytät sen, koko pyyhintä tehtävä käynnistetään alusta asti.</string>

<string lang="fi" key="DEVICE_WIPE_PAGE_INFO">\n\nHuomioi: Jos keskeytät pyyhintä tehtävän ja sitten yrität uudelleen käynnistää sitä, koko tehtävä aloitetaan alusta asti.</string>

<string lang="fi" key="CONFIRM_WIPE_ABORT">Haluatko keskeyttää pyyhinnän?</string>

<string lang="fi" key="CONFIRM_WIPE_START">Varoitus: Koko sisältö valitulta osiolta/asemalta tyhjennetään ja se katoaa.</string>

<string lang="fi" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Koko osion sisältö missä alkuperäinen järjestelmä sijaitsee tyhjennetään.\n\nHuomioi: Koko osion sisältö joka halutaan poistaa on kopioitu tälle piilotetulle osiolle.</string>

<string lang="fi" key="WIPE_MODE_WARN">VAROITUS: Huomioi että kun valitset esim. 3-ohitus pyyhintä tilan, kuluva tarvittu aika salatakseen osion/aseman kestää 4 kertaa kauemmin. Samoin kuin, jos valitset 35-ohitus pyyhintä tilan, se kestää 36 kertaa kauemmin (saattaa kestää useita viikkoja).\n\nKuitenkin, huomioi että pyyhintää EI suoriteta sen jälkeen kun osio/asema on täysin salattu. Kun osio/asema on täysin salattu, salaamatonta tietoa ei kirjoiteta sille. Mitä tahansa kirjoitetaan sille se ensin salataan lennossa muistissa ja ainoastaan sitten se (salattu) tieto kirjoitetaan levylle (siten se EI vaikuta suorituskykyyn).\n\nOletko varma että haluat käyttää pyyhintä tilaa?</string>

<string lang="fi" key="WIPE_MODE_NONE">Ei mitään (nopein)</string>

<string lang="fi" key="WIPE_MODE_1_RAND">1-läpi (satunnaistieto)</string>

<string lang="fi" key="WIPE_MODE_3_DOD_5220">3-läpi (US DoD 5220.22-M)</string>

<string lang="fi" key="WIPE_MODE_7_DOD_5220">7-läpi (US DoD 5220.22-M)</string>

<string lang="fi" key="WIPE_MODE_35_GUTMANN">35-läpi ("Gutmann")</string>

<string lang="fi" key="SYS_MULTI_BOOT_MODE_TITLE">Käyttöjärjestelmän numero</string>

<string lang="fi" key="MULTI_BOOT_FOR_ADVANCED_ONLY">VAROITUS: Aloittelevan käyttäjän ei koskaan pidä yrittää salata Windows monikäynnistys (multi-boot) konfiguraatioita.\n\nJatkatko?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Käynnistys Asema</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Onko nykyinen käytössä oleva käyttöjärjestelmä asennettuna käynnistys asemalle?\n\nTiedotus: Joskus Windows ei ole asennettu samalle asemalle kuin käynnistys lataaja (käynnistys osiolle). Tässä tapauksessa valitse 'Ei'.</string>

<string lang="fi" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt nykyisin ei tue salattua käyttöjärjestelmää joka ei käynnisty asemalta jonne sitä ei ole asennettu.</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Järjestelmälevyjen Määrä</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Kuinka monta asemaa käyttöjärjestelmäsi sisältää?\n\nTiedotus: esimerkiksi, jos käyttöjärjestelmäsi on (esim. Windows, Mac OS X, Linux, jne.) asennettu ensisijaiselle asemalle ja jokin lisä käyttöjärjestelmä on asennettu toissijaiselle asemalle, valitse '2 tai enemmin'.</string>

<string lang="fi" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt ei nykyisin tue salattua kokonaista asemaa joka sisältää useamman käyttöjärjestelmän.\n\nMahdollinen ratkaisu:\n\n- Voit vielä salata yhden järjestelmän jos menet takaisin ja valitset salaa vain yksi järjestelmäosio (vastakohta valittaessa salaukseen kokonainen järjestelmälevy).\n\n- Vaihtoehto, on mahdollista salata kokonainen asema jos siirrät järjestelmän toiselle asemalle jättäen ainoastaan yhden järjestelmän asemalle jonka haluat salata.</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Useampi järjestelmä yhdellä levyllä</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Onko jotakin muuta käyttöjärjestelmää asennettuna asemalle kuin nykyisin ajettava ja asennettu järjestelmä?\n\nTiedotus: Esimerkiksi, jos nykyinen ajettava käyttöjärjestelmä on asennettu asemalle #0, mikä sisältää useita osioita. ja jos yksi osioista sisältää Windowsin ja toiset osiot jonkin muun toisen käyttöjärjestelmän (esim. Windows, Mac OS X, Linux, jne.), valitse 'Kyllä'.</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Ei-Windows Käynnistyslataaja</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Onko ei-Windows käynnistys lataaja (tai käynnistys manageri) asennettuna isäntä käynnistys rekisteriin (MBR)?\n\nHuomioi: Esimerkiksi, jos ensimmäinen käynnistys aseman polku sisältää GRUB, LILO, XOSL, tai muun ei-Windows käynnistys managerin (tai käynnistys lataajan), valitse 'Kyllä'.</string>

<string lang="fi" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Bootti</string>

<string lang="fi" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt ei nykyisellään tue multi-käynnistys asetuksia jonne Ei-Windows käynnistys lataaja on asennettuna Master Boot Recordiin (MBS).\n\nMahdollinen Ratkaisu:\n\n- Jos käytät käynnistys manageria käynnistääksesi Windows ja Linux järjestelmiä, siirrä käynnistys manageri (tyypillisesti, GRUB) Master Boot Record osiolta. Sitten käynnistä opastus uudelleen ja salaa järjestelmäosio/levy. Huomioi, että VeraCrypt Käynnistyslataajasta tulee sinun ensisijainen käynnistys manageri ja se mahdollistaa sinua ajamasta alkuperäistä käynnistys manageria (esim. GRUB) kuten toissijaisena käynnistys managerina (painamalla Esc näppäintä VeraCrypt Käynnistyslataajan ikkunassa) ja siten mahdollista ladata Linux.</string>

<string lang="fi" key="WINDOWS_BOOT_LOADER_HINTS">Jos nykyinen käytössäsi oleva käyttöjärjestelmä on asennettu lataavalle osiolle ,sitten, kun olet salannut sen, sinun tulee antaa oikea salasana vaikka jos haluat käynnistää jonkin toisen salaamattoman Windows järjestelmän(t) (kuten ne jakavat yhden salatun Windows käynnistys lataajan/managerin).\n\nVastakohtana, jos nykyinen käyttöjärjestelmä ei ole asennettuna käynnistyvälle osiolle (tai jos Windows käynnistys lataaja/manageri ei ole käytetty toista muuta järjestelmää), sitten, kun olet salannut tämän järjestelmän, sinun ei tarvitse antaa oikeaa salasanaa käynnistääksesi salaamatonta järjestelmää(t) -- sinun tulee ainoastaan painaa Esc näppäintä aloittaaksesi salaamattoman järjestelmän (jos on useampia salaamattomia järjestelmiä, sinun tulee myös valita minkä järjestelmän käynnistät VeraCrypt Käynnistys Manageri valikosta).\n\nTiedote: Tavallisesti, aiemmin asennettu Windows järjestelmä on asennettu käynnistys osiolle.</string>

<string lang="fi" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Isäntä Suojattu alue Salattu</string>

<string lang="fi" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Monen asemien lopussa on alue, joka on tavallisesti piilotettu käyttöjärjestelmältä (tällaiset alueet ovat tavallisesti mainittuina Isäntä Suojatuissa Alueissa). Kuitenkin, jotkin ohjelmat voivat lukea ja kirjoittaa dataa siitä/siihen alueeseen.\n\nVAROITUS: Jotkin tietokoneen valmistajat voivat käyttää tällaista aluetta tallentaakseen työkaluja ja dataa RAID:lle, järjestelmän toipuminen, järjestelmän asetukset, diagnostiikka, tai muu tarkoitus. Jos tällainen työkalu tai data täytyy olla saatavilla ennen käynnistymistä, piilotettua aluetta EI tule salata (valitse 'Ei' yllä).\n\nHaluatko VeraCrypt havaita ja salata tällainen piilotettu alue (jos on) järjestelmä aseman lopusta?</string>

<string lang="fi" key="SYSENC_TYPE_PAGE_TITLE">Järjestelmä Salauksen tyyppi</string>

<string lang="en" key="RESCUE_DISK_WIN_ISOBURN_PRELAUNCH_NOTE">After you click OK, Microsoft Windows Disc Image Burner will be launched. Please use it to burn the VeraCrypt Rescue Disk ISO image to a CD or DVD.\n\nAfter you do so, return to the VeraCrypt Volume Creation Wizard and follow its instructions.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO">The Rescue Disk image has been created and stored in this file:\n%hs\n\nNow you need to burn it to a CD or DVD.\n\n%lsAfter you burn the Rescue Disk, click Next to verify that it has been correctly burned.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO_NO_CHECK">The Rescue Disk image has been created and stored in this file:\n%hs\n\nNow you should either burn the image to a CD/DVD or move it to a safe location for later use.\n\n%lsClick Next to continue.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO_NONWIN_ISO_BURNER">IMPORTANT: Note that the file must be written to the CD/DVD as an ISO disk image (not as an individual file). For information on how to do so, please refer to the documentation of your CD/DVD recording software. If you do not have any CD/DVD recording software that can write the ISO disk image to a CD/DVD, click the link below to download such free software.\n\n</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="fr" key="RESCUE_DISK_BURN_NO_CHECK_WARN">AVERTISSEMENT : Si vous avez déjà créé un disque de secours VeraCrypt dans le passé, il ne peut pas être utilisé à nouveau pour cette partition/ce disque système car il a été créé pour une clé principale différente ! Chaque fois que vous chiffrez une partition/un disque système, vous devez créer un disque de secours VeraCrypt même si vous utilisez le même mot de passe.</string>

<string lang="fr" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Erreur : Impossible de sauvegarder les paramètres de chiffrement système.</string>

<string lang="fr" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Impossible d'initialiser le pré-test du chiffrement système.</string>

<string lang="fr" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Impossible d'initier le processus de création du système d'exploitation caché.</string>

<string lang="fr" key="WIPE_MODE_TITLE">Mode de nettoyage</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="fr" key="WIPE_MODE_NONE">Aucun (le plus rapide)</string>

<string lang="fr" key="WIPE_MODE_3_DOD_5220">3 passages (US DoD 5220.22-M)</string>

<string lang="fr" key="WIPE_MODE_7_DOD_5220">7 passages (US DoD 5220.22-M)</string>

<string lang="fr" key="SYS_MULTI_BOOT_MODE_TITLE">Nombre de système d'exploitation</string>

<string lang="fr" key="MULTI_BOOT_FOR_ADVANCED_ONLY">AVERTISSEMENT : Les utilisateurs novices ne devraient pas essayer de chiffrer Windows dans des configurations à amorçages multiples.\n\nContinuer ?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Disque d'amorçage</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Le système d'exploitation en cours est-il installé sur le disque d'amorçage.\n\nNote : Parfois Windows n'est pas installé sur le même disque que le chargeur d'amorçage de Windows (partition d'amorçage). Si c'est le cas cliquez sur 'Non'.</string>

<string lang="fr" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt ne supporte pas encore le chiffrement d'un système d'exploitation qui ne démarre pas depuis le disque sur lequel il est installé.</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Nombre de disques système</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Combien de disques contiennent un système d'exploitation ?\n\nNote : Par exemple si vous avez un système d'exploitation (ex : Windows, Mac OS X, Linux; etc.) installé sur votre disque principal et un autre installé sur un disque secondaire, alors sélectionnez '2 ou plus'.</string>

<string lang="fr" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt ne supporte pas encore le chiffrement de la totalité d'un disque qui contient plusieurs systèmes d'exploitation.\n\nSolutions possibles :\n\n- Vous pouvez toujours chiffrer l'un des systèmes si vous revenez en arrière et que vous choisissez de ne chiffrer qu'une partition système (au lieu de choisir de chiffrer l'intégralité du disque système).\n\n- Alternativement vous pourrez chiffrer la totalité du disque si vous déplacez certains systèmes sur d'autres disques pour ne laisser qu'un seul système sur le disque que vous voulez chiffrer.</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Systèmes multiples sur un seul disque</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Y a-t-il d'autres systèmes d'exploitation installés sur le disque sur lequel est installé le système d'exploitation actuel ?\n\nNote : Par exemple, si le système d'exploitation en cours est installé sur le disque #0, qui contient plusieurs partitions, et si l'une d'elles contient Windows et qu'une autre contient un autre système d'exploitation (ex : Windows, Mac OS X, Linux, etc.), sélectionnez 'Oui'.</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Chargeur d'amorçage non-Windows</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Un chargeur d'amorçage (ou un gestionnaire d'amorçage) non-Windows est-il installé dans le MBR ?\n\nNote : Par exemple si la première piste du disque de démarrage contient GRUB, LILO, XOSL ou un autre gestionnaire d'amorçage (ou chargeur d'amorçage non-Windows), sélectionnez 'Oui'.</string>

<string lang="fr" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Amorçage multiple</string>

<string lang="fr" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt ne supporte pas encore les configurations à amorçage multiple où un chargeur d'amorçage non-Windows est installé dans le MBR.\n\nSolutions possibles :\n\n- Si vous utilisez un gestionnaire d'amorçage pour démarrer Windows et Linux, déplacez le gestionnaire d'amorçage (généralement, GRUB) du MBR vers une partition. Puis démarrer à nouveau l'assistant et chiffrez la partition/le disque système. Notez que le chargeur d'amorçage de VeraCrypt deviendra votre gestionnaire d'amorçage principal et qu'il vous permettra de lancer le gestionnaire d'amorçage d'origine (ex : GRUB) comme second gestionnaire d'amorçage (en appuyant sur le touche Echap lors de l'écran du chargeur d'amorçage de VeraCrypt) et ainsi vous pourrez charger Linux.</string>

<string lang="fr" key="WINDOWS_BOOT_LOADER_HINTS">Si le système d'exploitation en cours est installé sur la partition d'amorçage, alors après l'avoir chiffrée, vous devrez saisir le bon mot de passe même si vous désirez lancer l(es) autre(s) système(s) Windows non-chiffré(s).\n\nSi le système d'exploitation en cours n'est pas installé sur la partition d'amorçage de Windows (ou si le gestionnaire/chargeur d'amorçage de Windows n'est utilisé par aucun autre système), alors après avoir chiffré ce système, vous n'aurez pas à saisir de mot de passe pour lancer le(s) système(s) non-chiffré(s) -- Vous n'aurez qu'à appuyer sur la touche Echap pour lancer le système non-chiffré (s'il y a plusieurs systèmes non-chiffrés, vous devrez aussi choisir lequel lancer dans le menu du gestionnaire d'amorçage de VeraCrypt).\n\nNote : Typiquement, le système d'exploitation installé en premier l'est sur la partition d'amorçage.</string>

<string lang="fr" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Chiffrement de la zone protégée hôte (Host Protected Area)</string>

<string lang="fr" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">A la fin de nombreux disques, il y a une zone qui est normalement cachée du système d'exploitation (de telles zones sont généralement appelées 'Zones protégées hôtes' - Host Protected Area). Cependant certains programmes peuvent lire et écrire des données dans ces zones.\n\nAVERTISSEMENT : Certains constructeurs d'ordinateurs peuvent utiliser à dessein ces zones pour y stocker des outils et des données pour le RAID, des outils de récupération système, des outils de diagnostic, etc. Si de tels outils ou si des données doivent être accessibles avant l'amorçage, la zone cachée ne doit PAS être chiffrée (choisir 'Non' ci-dessus).\n\nVoulez-vous que VeraCrypt détecte et chiffre un telle zone cachée (si elle existe) à la fin de votre disque système ?</string>

<string lang="fr" key="SYSENC_TYPE_PAGE_TITLE">Type du chiffrement du système</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="it" key="LAUNCH_WIN_ISOBURN">Lancia Microsoft Windows Disc Image Burner</string>

<string lang="it" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ATTENZIONE: Se avete già creato in passato un disco di ripristino di VeraCrypt non lo potete riutilizzare per questa partizione/disco di sistema perché è stato creato con una chiave master differente! Ogni volta che codificate una partizione/disco di sistema, dovete creare un nuovo disco di ripristino di VeraCrypt per esso, anche se usate la stessa password.</string>

<string lang="it" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">ERRORE: Impossibile salvare le impostazioni di codifica del sistema.</string>

<string lang="it" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Impossibile d'iniziarizzare il pre-test codifica di sistema.</string>

<string lang="it" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Impossibile inizializzare il processo di creazione del sistema operativo nascosto.</string>

<string lang="it" key="WIPE_MODE_TITLE">Modo pulizia</string>

<string lang="it" key="INPLACE_ENC_WIPE_MODE_INFO">In alcuni tipi di periferiche di memoria, quando i dati vengono soprascritti da altri dati, può essere possibile recuperare i dati soprascritti usando delle tecniche come forza magnetica microscopica. Questo viene applicato pure ai dati che vengono soprascritti con la loro forma Crittata (questo avviene quando VeraCrypt codifica inizialmente codifica una partizione o disco decriptato). In accordo ad alcuni studi e pubblicazioni governative, il recupero dei dati soprascritti può essere evitato (o reso molto difficile) soprascrivendo i dati con certi dati pseudo casuali e non casuali per un certo numero di volte. Pertanto, se voi credete che un avversario possa essere capace di usare tali tecniche per recuperare i dati che intendete codificare, potete voler selezionare una delle modalità di pulizia (i dati esistenti NON saranno distrutti). Notate che questa modalità di pulizia NON può essere eseguita dopo la codifica della partizione/disco. Quando la partizione/disco è totalmente criptato, non viene scritto nessun dato non criptato in esso. Qualsiasi dato da scrivere in esso viene prima criptato al volo nella memoria, e solo quando esso viene criptato viene scritto sul disco.</string>

<string lang="it" key="WIPE_MODE_INFO">In alcuni tipi di periferiche di memoria, quando i dati vengono soprascritti da altri dati, (cioè quando i dati vengono cancellati), può essere possibile recuperare i dati soprascritti usando delle tecniche come forza magnetica microscopica. In accordo ad alcuni studi e pubblicazioni governative, il recupero dei dati soprascritti può essere evitato (o reso molto difficile) soprascrivendo i dati con certi dati pseudo casuali e non casuali per un certo numero di volte. Pertanto, se voi credete che un avversario possa essere capace di usare tali tecniche per recuperare i dati cancellati, potete voler selezionare una delle modalità di pulizia a passaggi multipli.\n\nNota: Più passaggi di pulizia utilizzate, più tempo si impiega per cancellare i dati.</string>

<string lang="it" key="DEVICE_WIPE_PAGE_TITLE">Pulizia</string>

<string lang="it" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNota: Potete interrompere il processo di pulizia, spegnere il vostro computer, avviare il sistema nascosto nuovamente e riprendere il processo interrotto (questa procedura sarà lanciata automaticamente). Pertanto, se voi lo interrompete, l’intero processo di pulizia ripartirà dall’inizio.</string>

<string lang="it" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: Se interrompete il processo di pulizia e quindi tentate di riprenderlo, l’intero processo di pulizia ripartirà dall’inizio.</string>

<string lang="it" key="CONFIRM_WIPE_ABORT">Volete interrompere il processo di pulizia?</string>

<string lang="it" key="CONFIRM_WIPE_START">ATTENZIONE: L’intero contenuto della parizione/unità selezionata sarà cancellato e distrutto.</string>

<string lang="it" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">L’intero contenuto della partizione dove il sistema originale risiede sarà cancellato.\n\nNota: L’intero contenuto della partizione che è stato cancellato è stato copiato nella partizione del sistema nascosto.</string>

<string lang="it" key="WIPE_MODE_WARN">AVVERTENZA: Notate che se scegliete ad esempio una modalità di pulizia a 3 passaggi, il tempo necessario a codificare la partizione/unità sarà più di 4 volte superiore. Allo stesso modo, se scegliete una modalità di pulizia a 35 passaggi, ci vorrà un tempo superiore di 36 volte (può essere anche alcune settimane).\n\nNotate, comunque, che la pulizia NON può essere eseguita dopo che la partizione/unità sia totalmente Crittata. Quando la partizione/unità è totalmente Crittata, nessun dato non criptato viene scritto in esso. Qualsiasi dato da scrivere viene prima criptato al volo nella memoria e solo quando viene criptato esso viene scritto su disco (così le prestazioni NON saranno influenzate).\n\nSiete sicuri di voler usare la modalità di pulizia?</string>

<string lang="it" key="WIPE_MODE_NONE">Nessuno (il più veloce)</string>

<string lang="it" key="WIPE_MODE_1_RAND">1-passaggio (dati casuali)</string>

<string lang="it" key="WIPE_MODE_3_DOD_5220">3-passaggi (US DoD 5220.22-M)</string>

<string lang="it" key="WIPE_MODE_7_DOD_5220">7-passaggi (US DoD 5220.22-M)</string>

<string lang="it" key="WIPE_MODE_35_GUTMANN">35-passaggi ("Gutmann")</string>

<string lang="it" key="SYS_MULTI_BOOT_MODE_TITLE">Numero di sistemi operativi</string>

<string lang="it" key="MULTI_BOOT_FOR_ADVANCED_ONLY">AVVERTENZA: Gli utenti non esperti non devono mai tentare di codificare Windows in configurazione di multi-avvio.\n\nContinuare?</string>

<string lang="it" key="HIDDEN_OS_MULTI_BOOT">Quando si usa o si crea un sistema operativo nascosto, VeraCrypt supporta una configurazione multi-avvio solo quando si verificano le seguenti condizioni:\n\n- Il sistema operativo attualmente in uso deve essere installato sul disco d'avvio (di boot), il quale non deve contenere altri sistemi operativi.\n\n- Sistemi operativi installati su altri drive non devono usare boot d'avvio residenti sul disco nel quale è installato l'attuale sistema operativo in uso.\n\nSi sono verificate le condizioni di cui sopra?</string>

<string lang="it" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt non supporta questa configurazione multi-avvio quando si crea o si utilizza un sistema operativo nascosto.</string>

<string lang="it" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Disco di avvio</string>

<string lang="it" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Il sistema operativo attualmente in esecuzione è installato nel disco di avvio?\n\nNota: Qualche volta, Windows non è installato sullo stesso percorso come il loader di avvio di Windows (partizione di avvio). Se siete in questa situazione, selezionate 'No'.</string>

<string lang="it" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">Attualmente, VeraCrypt non supporta la codifica di un sistema operativo che non si avvia dal drive dove è installato.</string>

<string lang="it" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Numero dischi di sistema</string>

<string lang="it" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Quanti dischi contengono un sistema operativo?\n\nNota: Per esempio, se avete uno qualsiasi dei sistemi operativi (esempio Windows, Mac OS X, Linux, ecc.) installato sul vostro drive primario ed uno dei sistemi operativi installati sul vostro disco secondario, selezionare '2 o più'.</string>

<string lang="it" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">Attualmente VeraCrypt non supporta la codifica dell’intero drive contenente sistemi operativi multipli.\n\nPossibili soluzioni:\n\n- Potete ancora codificare uno dei sistemi se voi andate indietro e scegliete la codifica di una singola partizione di sistema (in opposizione alla scelta di codifica dell’intero disco di sistema).\n\n- In alternativa, potete codificare l’intero drive se spostate alcuni dei sistemi in altre unità, lasciando solo un sistema sul drive che volete codificare.</string>

<string lang="it" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Sistemi multipli su un drive singolo</string>

<string lang="it" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Esiste un qualsiasi altro sistema operativo installato sul drive nel quale il sistema operativo attualmente in esecuzione è installato?\n\nNota: per esempio, se il sistema operativo attualmente in esecuzione è installato sul drive #0, che contene diverse partizioni, e se una delle partizioni contiene Windows ed un’altra partizione contiene qualsiasi sistema operativo aggiuntivo (cioè Windows, Mac OS X, Linux, ecc.), selezionare 'Sì'.</string>

<string lang="it" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Loader di avvio non di Windows</string>

<string lang="it" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Un loader o manager di avvio di Windows è installato nel manager di avvio principale (MBR)?\n\nNota: Per esempio, se la prima traccia del disco di avvio contiene GRUB, LILO, XOSL, o alcuni altri manager o loader di avvio non di Windows, selezionare 'Si'.</string>

<string lang="it" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Avvio multiplo</string>

<string lang="it" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">Attualmente VeraCrypt non supporta ancora le configurazioni avvio multiplo dove un loader di avvio non di Windows è installato nel record di avvio principale.\n\nSoluzioni possibili:\n\n - Se usate un manager di avvio per avviare Windows e Linux, spostare il manager di avvio (chiamato tipicamente GRUB) dal record di avvio master ad una partizione, quindi avviate nuovamente questa procedura e Codificate la partizione/disco di sistema. Notate che il loader di avvio di VeraCrypt diventerà il vostro manager di avvio principale e vi consentirà di lanciare il manager di avvio originale (cioè GRUB) come il vostro manager di avvio secondario (premendo il tasto Esc nello schermo del loader di avvio di VeraCrypt) e quindi potrete lanciare Linux.</string>

<string lang="it" key="WINDOWS_BOOT_LOADER_HINTS">Se il sistema operativo in esecuzione è installato sulla partizione di avvio, dopo averla criptato, avrete bisogno di digitare la password corretta anche se volete avviare un altro sistema Windows non decriptato (siccome essi condividono una singolo loader/manager di avvio di Windows non criptato).\n\nA contrario, se il sistema operativo attualmente in esecuzione sulla partizione di avvio (o se il loader/manager di avvio di Windows non è utilizzato da nessun altro sistema), aver criptato sistema, non avrete bisogno di digitare la password corretta per avviare l'altro sistema decriptato. Dovrete solamente premere il tasto ESC per avviare il sistema decriptato (se ci sono sistemi DeCodificati multipli, avrete bisogno di selezionare pure quale sistema da avviare nel manager di avvio di VeraCrypt).\n\nNote: Tipicamente, il primo sistema di Windows è installato nella partizione di avvio.</string>

<string lang="it" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Codifica dell’area ospite protetta</string>

<string lang="it" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Alla fine di molti dischi, c'è un'area che è normalmente nascosta dal sistema operativo (tali aree sono chiamate di solito come Aree ospiti protette). Comunque, alcuni programmi possono leggere e possono scrivere dei dati da/in tali aree. n ATTENZIONE: Alcuni fabbricanti di computer possono usare tali aree per memorizzare degli strumenti e dei dati per il recupero di sistema RAID, per le impostazioni del sistema, per scopi diagnostici o altro. Se tali strumenti o dati devono essere accessibili prima dell’avvio, l'area ignota NON dovrebbe essere Crittata (scegliere NO sopra).\n\nVolete che VeraCrypt scopra e cifri tale area ignota (se esiste) alla fine del disco?</string>

<string lang="it" key="SYSENC_TYPE_PAGE_TITLE">Tipo di codifica di sistema</string>

<string lang="ja" key="LAUNCH_WIN_ISOBURN">Windowsディスクイメージ書き込みツールを起動</string>

<string lang="ja" key="RESCUE_DISK_BURN_NO_CHECK_WARN">警告：もし以前にVeraCryptレスキューディスクをすでに作成していたのであれば、異なるマスターキーが作成されたため、このシステムパーティション/ドライブ用には使えなくなります！ システムパーティション/ドライブを暗号化するときは常に、たとえ以前と同じパスワードを使うのであっても、新しいVeraCryptレスキューディスクを作成する必要があります。</string>

<string lang="ja" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">エラー：システムの暗号化設定を保存できません。</string>

<string lang="ja" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">システム暗号化の予備検査を開始できません。</string>

<string lang="ja" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">隠しOSの作成プロセスが初期化できません。</string>

<string lang="ja" key="WIPE_MODE_TITLE">ワイプモード</string>

<string lang="ja" key="INPLACE_ENC_WIPE_MODE_INFO">ある種の記録メディアでは、データが他のデータで上書きされた場合でも、磁力顕微鏡のような手法で上書きされたデータを復活することができます。これは元データを暗号化したデータで上書きした場合であっても当てはまります。VeraCryptでそのドライブ/パーティションを初めて暗号化した場合でも同様です。いくつかの研究や政府の発行物によれば、ランダムデータとある種のランダムでないデータで一定回数上書きすることによって、元データの復活を不可能あるいは極端に困難にすることが可能です。したがって敵対者が磁力顕微鏡のような手法で暗号化したデータを復活させてくると想定されるならば、以下に実装されたワイプモードを選択してください（既存のデータは失われません）。なおパーティションやドライブが暗号化された後ではワイプは機能しません。パーティションやドライブがすべて暗号化されているときは、暗号化されていないデータが書き込まれることがないからです。書き込もうとするすべてのデータは、メモリ上で即時に暗号化されてからディスクに書き込まれます。</string>

<string lang="ja" key="WIPE_MODE_INFO">ある種の記録メディアでは、データが他のデータで上書きされた場合でも、磁力顕微鏡のような手法で上書きされたデータを復活することができます。いくつかの研究や政府の発行物によれば、ランダムデータとある種のランダムでないデータで一定回数上書きすることによって、元データの復活を不可能あるいは極端に困難にすることが可能です。したがって敵対者が磁力顕微鏡のような手法で暗号化したデータを復活させてくると想定されるならば、以下に実装されたワイプモードを選択してください。\n\n注：ワイプの回数を増やすと、データ抹消にも時間がかかるようになります。</string>

<string lang="ja" key="DEVICE_WIPE_PAGE_TITLE">ワイプ処理</string>

<string lang="ja" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n注：この抹消処理は、中断し、コンピュータをシャットダウンして、隠しOSを起動してから処理を再開できます（このウィザードが自動的に起動します）。ただし中断した場合は、抹消処理全体を最初からやり直す必要があります。</string>

<string lang="ja" key="DEVICE_WIPE_PAGE_INFO">\n\n注：抹消処理を中断して後で再開する場合、抹消処理全体を最初からやり直す必要があります。</string>

<string lang="ja" key="CONFIRM_WIPE_ABORT">ワイプ処理を中断しますか？</string>

<string lang="ja" key="CONFIRM_WIPE_START">警告：選択されたパーティション/デバイス上のすべてのデータは削除され、失われます。</string>

<string lang="ja" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">元のシステムがあったパーティション上のすべてのデータは削除されます。\n\n注：削除されるこのパーティション上のすべてのデータは、隠しシステムパーティションにコピーされます。</string>

<string lang="ja" key="WIPE_MODE_WARN">警告：もしたとえば3パスワイプモードを選択した場合、ドライブ/パーティションの暗号化にかかる時間は最大で4倍必要となります。同様にもし35パスワイプモードを選択した場合は最大で36倍の時間がかかります（おそらく数週間かかるでしょう）。\n\nただし、パーティションやドライブがすべて暗号化された後ではワイプは機能しないことに注意してください。パーティションやドライブがすべて暗号化されているときは、暗号化されていないデータが書き込まれることがないからです。書き込もうとするすべてのデータは、メモリ上で即時に暗号化されてからディスクに書き込まれるため、ワイプが有効に機能しません。\n\n本当にワイプモードを使用しますか？</string>

<string lang="ja" key="WIPE_MODE_NONE">なし（最速）</string>

<string lang="ja" key="WIPE_MODE_1_RAND">1パス (ランダムデータ)</string>

<string lang="ja" key="WIPE_MODE_3_DOD_5220">3パス(US DoD 5220.22-M)</string>

<string lang="ja" key="WIPE_MODE_7_DOD_5220">7パス(US DoD 5220.22-M)</string>

<string lang="ja" key="WIPE_MODE_35_GUTMANN">35パス ("Gutmann")</string>

<string lang="ja" key="SYS_MULTI_BOOT_MODE_TITLE">OSの数</string>

<string lang="ja" key="MULTI_BOOT_FOR_ADVANCED_ONLY">警告：慣れているユーザー以外はマルチブート設定のWindowsを暗号化しないでください。\n\n続けますか？</string>

<string lang="ja" key="HIDDEN_OS_MULTI_BOOT">隠しOSを作成あるいは使用する場合、VeraCryptは次の条件を満たすときのみ、マルチブート設定に対応します：\n\n-現在起動中のOSが起動用ドライブにインストールされており、かつそのドライブに他のOSが一切含まれていないこと\n\n-起動用以外のドライブにインストールされているOSが、現在起動中のOSがインストールされているドライブに置かれたブートローダーを使用していないこと\n\n以上の条件を満たしていますか？</string>

<string lang="ja" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCryptは、このマルチブート設定において、隠しOSの作成/使用に対応していません。</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">起動ドライブ</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">現在動作中のオペレーティングシステムは起動ドライブにインストールされているものですか？\n\n注：場合によってはWindowsシステムがWindowsブートローダーのあるドライブ（起動パーティション）とは別のドライブにインストールされているケースがあります。もしそのようなケースに該当する場合は「いいえ」を選択してください。</string>

<string lang="ja" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCryptは起動ドライブ以外にインストールされているオペレーティングシステムの暗号化には現在対応していません。</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">システムドライブの数</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">オペレーティングシステムの入ったドライブはいくつありますか？\n\n注：たとえばいずれかのOS（たとえばWindows, Mac OS X, Linuxなど）がプライマリドライブにインストールされており、セカンダリドライブに追加のOSがインストールされているなら「2以上」を選択してください。</string>

<string lang="ja" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCryptは複数のオペレーティングシステムを含むドライブ全体の暗号化には現在対応していません。\n\n対策として次の方法があります：\n\n- 前に戻ってから、システムドライブ全体ではなく、単一のシステムパーティションを暗号化する方法を選択できます。\n\n- 別の方法として、複数のうちの一つのシステムを他のドライブに移動し、このドライブを単一のシステムだけにしてからドライブ全体を暗号化することもできます。</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">単一のドライブに複数のシステム</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">現在動作中のオペレーティングシステムがインストールされているドライブに、他のオペレーティングシステムもインストールされていますか？\n\n注：たとえば現在動作中のOSがドライブ#0にインストールされており、このドライブには他のパーティションがあってそこに別のOS（Windows, Mac OS X, Linuxなど）がインストールされている場合は「はい」を選択してください。</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Windows以外のブートローダー</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Windows以外のブートローダー（あるいはブートマネージャー）がマスターブートレコード(MBR)にインストールされていますか？\n\nたとえば起動ドライブの第一トラックにGRUB, LILO, XOSL等のWindows以外のブートローダー（ブートマネージャー）が存在するなら「はい」を選択してください。</string>

<string lang="ja" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">マルチブート</string>

<string lang="ja" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCryptはマスターブートレコード(MBR)にWindows以外のブートローダーがインストールされているマルチブート環境には現在対応していません。\n\n対策として次の方法があります：\n\n- もしWindowsとLinuxのためにブートマネージャーを使用しているなら、MBRからパーティションにブートマネージャー（一般的にはGRUB）を移動してください。その後再度ウィザードを実行してシステムパーティション/ドライブを暗号化してください。なおVeraCryptブートローダーはプライマリブートマネージャーとなり、元のブートマネージャー(GRUBなど)をセカンダリブートマネージャーとして呼び出せるようになります（VeraCryptブートローダー画面でESCキーを押してください）。そうすればLinuxを起動できます。</string>

<string lang="ja" key="WINDOWS_BOOT_LOADER_HINTS">もし現在動作中のOSがこの起動パーティションにインストールされているのであれば、それを暗号化した後は、他の暗号化されていないWindowsを起動しようとするときにも、正しいパスワードを入力する必要があります（それらは一つの暗号化されたブートローダー/マネージャーを共有しています）。\n\n対照的に、もし現在動作中のOSがWindowsの起動パーティションにインストールされているのでなければ（あるいはWindowsブートローダー/マネージャーが他のシステムから使用されていない場合）、それを暗号化した後は、暗号化されていないシステムを起動する際にはパスワードは要求されません。非暗号化システムを起動するときはESCキーを押すだけです。もし非暗号化システムが複数あるときは、VeraCryptブートマネージャーメニューで起動するシステムを選択できます。\n\n注：一般的には、一番最初にインストールされたWindowsが起動パーティションにインストールされます。</string>

<string lang="ja" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">HPA(ホスト保護領域)の暗号化</string>

<string lang="ja" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">多くのドライブの終端には、OSから隠された領域（一般にHPA(Host Protected Area)として知られています）が存在しています。ただしいくつかのプログラムはこの領域を読み書き可能です。\n\n警告：一部のコンピュータメーカーは、たとえばRAID・システムリカバリ・システムセットアップ・システム診断等の目的で、この領域に何らかのツールやデータを保持しています。これらのツールやデータに、システムの起動前にアクセスできる必要がある場合は、この隠し領域は暗号化してはいけません（上で「いいえ」を選択してください）。\n\nシステムドライブの終端にあるこのような隠し領域についても検出し、暗号化しますか？</string>

<string lang="ja" key="SYSENC_TYPE_PAGE_TITLE">システム暗号化タイプ</string>

<string lang="en" key="RESCUE_DISK_WIN_ISOBURN_PRELAUNCH_NOTE">After you click OK, Microsoft Windows Disc Image Burner will be launched. Please use it to burn the VeraCrypt Rescue Disk ISO image to a CD or DVD.\n\nAfter you do so, return to the VeraCrypt Volume Creation Wizard and follow its instructions.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO">The Rescue Disk image has been created and stored in this file:\n%hs\n\nNow you need to burn it to a CD or DVD.\n\n%lsAfter you burn the Rescue Disk, click Next to verify that it has been correctly burned.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO_NO_CHECK">The Rescue Disk image has been created and stored in this file:\n%hs\n\nNow you should either burn the image to a CD/DVD or move it to a safe location for later use.\n\n%lsClick Next to continue.</string>

<string lang="en" key="RESCUE_DISK_BURN_INFO_NONWIN_ISO_BURNER">IMPORTANT: Note that the file must be written to the CD/DVD as an ISO disk image (not as an individual file). For information on how to do so, please refer to the documentation of your CD/DVD recording software. If you do not have any CD/DVD recording software that can write the ISO disk image to a CD/DVD, click the link below to download such free software.\n\n</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="ka" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">შეცდომა: სისტემის შიფრაციის პარამეტრების შენახვა შეუძლებელია.</string>

<string lang="ka" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">სისტემის შიფრაციისწინა ტესტის ინიციირება შეუძლებელია.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="ka" key="WIPE_MODE_TITLE">წაშლის რეჟიმი</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="ka" key="WIPE_MODE_NONE">არანაირი (უსწრაფესი)</string>

<string lang="ka" key="WIPE_MODE_3_DOD_5220">3-გზის (US DoD 5220.22-M)</string>

<string lang="ka" key="WIPE_MODE_7_DOD_5220">7-გზის (US DoD 5220.22-M)</string>

<string lang="ka" key="SYS_MULTI_BOOT_MODE_TITLE">ოპერაციული სისტემების რაოდენობა</string>

<string lang="ka" key="MULTI_BOOT_FOR_ADVANCED_ONLY">გაფრთხილება: გამოუცდელი მომხმარებლისათვის არარეკომენდებულია Windows-ის შიფრაცია მრავალ-ჩატვირთვად კონფიგურაციაში.\n\nგავაგრძელოთ?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">ჩამტვირთი დისკი</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">მიმდინარე ოპერაციული სისტემა ინსტალირებულია ჩამტვირთ დისკზე?\n\nშენიშვნა:ზოგჯერ Windows არ არის ინსტალირებული იმავე დისკზე, საიდანაც იტვირთება. თუ ეს ის შემთხვევაა, აირჩიეთ "არა".</string>

<string lang="ka" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt-ს ამჟამად არ აქვს იმ ოპერაციული სისტემების შიფრაციის მხარდაჭერა, რომლებიც ინსტალირებულია არაჩამტვირთავ დისკზე.</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">სისტემური დისკების რაოდენობა</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">რამდენი დისკი მოიცავს ოპერაციულ სისტემას?\n\nშენიშვნა: მაგ., თუ გაქვთ რომელიმე ოპერაციული სისტემა (Windows, Mac OS X, Linux, ა.შ.) ინსტალირებული პირველად დისკზე, და დამატებით ოპერაციული სისტემა ინსტალირებული მეორად დისკზე, აირჩიეთ "2 ან მეტი".</string>

<string lang="ka" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt-ს არ აქვს მხარდაჭერა დისკებისა, რომლებიც მოიცავენ რამდენიმე ოპერაციულ სისტემას.\n\nშესაძლო გამოსავალი:\n\n- შეგიძლიათ დაშიფროთ რომელიმე სისტემა, თუ დაბრუნდებიტ უკან და აირჩევთ მხოლოდ ერთ სისტემურ განაყოფს (მთელი დისკის დაშიფვრის ნაცვლად).\n\n- შეგიძლიათ დაშიფროთ მთელი დისკი, თუ დისკზე დატოვებთ მხოლოდ ერთ ოპერაციულ სისტემას, ხოლო დანარჩენებს სხვაგან გადაიტანთ.</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">რამდენიმე ოპერაციული სისტემა ერთ დისკზე</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">იმავე დისკზე, რომელზეც მიმდინარე ოპერაციული სისტემაა ინსტალირებული, არის თუ არა სხვა ოპერაციული სისტემები?\n\nშენიშვნა: თუ მაგ. მიმდინარე ოპერაციული სისტემა ინსტალირებულია დისკზე #0, რომელიც მოიცავს რამდენიმე განაყოფს, და რომელიმე განაყოფზე ინსტალირებულია სხვა ოპერაციული სისტემა (Windows, Mac OS X, Linux, ა.შ.), დაწკაპეთ "დიახ".</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">არა-Windows-ის საწყისი ჩამტვირთი</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="ka" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">მრავალ-ჩამტვირთი</string>

<string lang="ka" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt-ს არ აქვს მრავალ-ჩამტვირთი კონფუგურაციის მხარდაჭერა, როდესაც MBR-ზე ინსტალირებულია არა-Windows-ის ჩამტვირთი მოდული.\n\nშესაძლო გამოსავალი:\n\n- თუ იყენებთ ჩატვირთვის მენეჯერს Windows-ის და Linux-ის ჩასატვირთად, ჩატვირთვის მენეჯერი (GRUB) გადაიტანეთ MBR-დან განაყოფში. შემდეგ გაუშვით ეს ოსტატი ხელახლა და დაშიფრეტ სისტემური განაყოფი/დისკი. VeraCrypt-ის ჩამტვირთი მოდული გახდება მთავარი ჩამტვირთი მოდული და იგი მოგცემთ საშუალებას გაუშვათ ორიგინალი ჩამტვირთი (GRUB) როგორც მეორადი ჩატვირთვის მენეჯერი (Esc დაჭერით VeraCrypt-ის ჩამტვირთის ეკრანზე) და ამდენად ჩატვირთოთ Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="ko" key="LAUNCH_WIN_ISOBURN">Microsoft Windows Disc Image Burner 실행</string>

<string lang="ko" key="RESCUE_DISK_BURN_NO_CHECK_WARN">주의: 과거에 VeraCrypt 응급복구 디스크를 이미 만든 경우, 이 디스크를 현재 시스템 파티션/드라이브에 다시 사용할 수 없습니다. 왜냐하면 서로 다른 마스터 키로 디스크가 생성되었기 때문입니다. 시스템 파티션/드라이브를 암호화할 때마다, 비록 동일한 비밀번호를 사용할지라도, 새로운 VeraCrypt 응급복구 디스크를 만들어야 합니다.</string>

<string lang="ko" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">오류: 시스템 암호화 설정을 저장할 수 없습니다.</string>

<string lang="ko" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">시스템 암호화 예비테스트를 시작할 수 없습니다.</string>

<string lang="ko" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">숨긴 운영체제의 생성 과정을 시작할 수 없습니다.</string>

<string lang="ko" key="WIPE_MODE_TITLE">지움 방식</string>

<string lang="ko" key="INPLACE_ENC_WIPE_MODE_INFO">일부 형식의 저장 매체에서, 데이터를 다른 데이터로 덮어쓰게 되면, Magnetic Force Microscopy 같은 기술을 이용해서 덮어쓰여진 데이터를 복구할 수 있습니다. 이것은 암호화된 형태로 덮어쓰여진 데이터에만 적용됩니다(→ 이는 VeraCrypt가 암호화되지 않은 파티션 또는 드라이브를 초기에 암호화한 경우에 발생합니다). 일부 연구와 정부 발표에 따르면, (의사무작위 및 비무작위 데이터로 여러번 데이터를 덮어쓰는 방법으로) 덮어쓰여진 데이터의 복구를 방지하거나 또는 매우 어렵게 할 수 있습니다. 그래서 만약 암호화할 데이터를 “적대적인 사람이 그러한 기술을 이용해서 복구할 수 있다”고 믿고 있다면, 여러분은 지움(wipe) 방식 중의 하나를 선택하고자 할 것입니다(→ 기존 데이터의 손실 없음). 지움(wiping)은 파티션/드라이브가 암호화된 후에는 실행되지 않습니다. 파티션/드라이브가 완전히 암호화되었을 때, 암호화되지 않은 모든 데이터는 쓰여질 수 없게 됩니다. 암호화된 파티션/드라이브에 쓰여지는 데이터는 먼저 실시간으로 메모리에서 암호화되고 그 후 (암호화된) 데이터가 디스크에 쓰여집니다.</string>

<string lang="ko" key="WIPE_MODE_INFO">일부 형식의 저장 매체에서, 데이터를 다른 데이터로 덮어쓰게 되면(예: 데이터가 지워진 경우), Magnetic Force Microscopy 같은 기술을 이용해서 덮어쓰여진 데이터를 복구할 수 있습니다. 일부 연구와 정부 발표에 따르면, (의사무작위 및 비무작위 데이터로 여러번 데이터를 덮어쓰는 방법으로) 덮어쓰여진 데이터의 복구를 방지하거나 또는 매우 어렵게 할 수 있습니다. 그래서 만약 지워진 데이터를 “적대적인 사람이 그러한 기술을 이용해서 복구할 수 있다”고 믿고 있다면, 여러분은 다중-지움 방식 중의 하나를 선택하고자 할 것입니다.\n\n참고: 지움 횟수가 많은 방식을 이용할수록 데이터를 지우는 시간은 더욱 길어지게 됩니다.</string>

<string lang="ko" key="DEVICE_WIPE_PAGE_TITLE">지우기</string>

<string lang="ko" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n참고: 사용자는 지우기 작업을 중단할 수 있고, 컴퓨터를 종료해서 숨긴 시스템을 다시 시작한 후 작업을 재개할 수 있습니다(* 이 마법사는 자동으로 실행됩니다). 그러나 사용자가 이를 중단하면, 지움 작업은 처음부터 다시 진행됩니다.</string>

<string lang="ko" key="DEVICE_WIPE_PAGE_INFO">\n\n참고: 사용자가 지움 작업을 중단하고 이 작업을 다시 시작하면, 지움 작업은 처음부터 다시 진행됩니다.</string>

<string lang="ko" key="CONFIRM_WIPE_ABORT">지움 작업을 중단하시겠습니까?</string>

<string lang="ko" key="CONFIRM_WIPE_START">주의: 선택한 파티션/장치의 모든 데이터는 지워지고 이를 잃게 됩니다.</string>

<string lang="ko" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">원래의 시스템이 존재했던 파티션의 모든 데이터는 지워지게 됩니다.\n\n참고: 지워질 파티션의 모든 데이터는 이 숨긴 시스템 파티션으로 복사되었습니다.</string>

<string lang="ko" key="WIPE_MODE_WARN">주의: 예컨대 3번 지움 방식을 선택하게 되면 파티션/드라이브를 암호화하는 데 필요한 시간은 최대 4배가 길어집니다. 마찬가지로 35번 지움 방식을 선택하면, 최대 36배의 시간이 더 걸립니다(→ 이는 수주일이 걸릴 것입니다).\n\n그러나 지움(wiping)은 파티션/드라이브가 완전히 암호화된 후에는 실행되지 않습니다. 파티션/드라이브가 완전히 암호화되었을 때, 암호화되지 않은 모든 데이터는 쓰여질 수 없게 됩니다. 암호화된 파티션/드라이브에 쓰여지는 데이터는 먼저 실시간으로 메모리에서 암호화되고 그 후 (암호화된) 데이터가 디스크에 쓰여집니다(→ 그래서 실행에는 영향을 미치지 않습니다).\n\n지움 방식을 사용하시겠습니까?</string>

<string lang="ko" key="WIPE_MODE_NONE">없음 (가장 빠름)</string>

<string lang="ko" key="WIPE_MODE_1_RAND">1-번 (무작위 데이터)</string>

<string lang="ko" key="WIPE_MODE_3_DOD_5220">3-번 (US DoD 5220.22-M)</string>

<string lang="ko" key="WIPE_MODE_7_DOD_5220">7-번 (US DoD 5220.22-M)</string>

<string lang="ko" key="WIPE_MODE_35_GUTMANN">35-번 (“GUtmann”)</string>

<string lang="ko" key="SYS_MULTI_BOOT_MODE_TITLE">운영체제 개수</string>

<string lang="ko" key="MULTI_BOOT_FOR_ADVANCED_ONLY">주의: 경험이 없는 사용자는 “멀티-부트 설정의 윈도우”를 암호화하려고 시도해서는 안됩니다.\n\n계속하시겠습니까?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">부트 드라이브</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">현재 실행 중인 운영체제가 부트 드라이브에 설치되어 있습니까?\n\n참고: 때로 윈도우가 윈도우 부트 로더 (부트 파티션)와 동일한 드라이브에 설치되지 않은 경우도 있습니다. 이 경우에 “아니오”를 선택합니다.</string>

<string lang="ko" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt는 운영체제가 설치되어 있는 드라이브에서 부팅을 하지 않는 운영체제의 암호화를 현재 지원하지 않고 있습니다.</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">시스템 드라이브 수</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">운영체제에 몇 개의 드라이브가 있습니까?\n\n참고: 예컨대 사용자가 특정 운영체제(Windows, Mac OS X, Linux 등)를 첫번째(Primary) 드라이브에 설치하고, 다른 운영체제를 두번째(Secondary) 드라이브에 설치한 상태라면, “2 또는 그 이상”을 선택합니다.</string>

<string lang="ko" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt는 다수의 운영체제를 포함하고 있는 전체 드라이브의 암호화를 현재 지원하지 않습니다.\n\n가능한 해결책:\n\n- 뒤로 가서 단일 시스템 파티션만을 암호화하는 것을 선택한다면(→ 이는 전체 시스템 드라이브를 암호화하는 것을 선택하는 것과 반대개념), 그 시스템 중 하나를 암호화할 수 있습니다.\n\n- 대체방법으로 사용자가 (암호화할 드라이브에 한 개의 시스템만 남겨둔 채) 시스템의 일부를 다른 드라이브로 옮긴 경우라면 전체 드라이브를 암호화할 수 있습니다.</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">한 개 드라이브에 다중 시스템</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">현재 실행 중인 운영체제가 설치되어 있는 드라이브에 설치된 다른 운영체제가 있습니까?\n\n참고: 예컨대 현재 실행되고 있는 운영체제가 드라이브 #0에 설치된 경우, 이 드라이브엔 여러 개의 파티션이 있고, 그 중 하나의 파티션이 윈도우를 포함하고 있고, 다른 파티션이 또다른 운영체제를 포함하고 있는 경우라면(예: Windows, Mac OS X, Linux 등), “예”를 선택합니다.</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">비-윈도우 부트 로더</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">비-윈도우 부트 로드(또는 부트 관리자)가 마스터 부트 레코드(MBR)에 설치되어 있습니까?\n\n참고: 예컨대 부트 드라이브의 첫번째 트랙에 GRUB, LILO, XOS 또는 다른 비-윈도우 부트 관리자(또는 부트 로더)가 있는 경우, “예”를 선택합니다.</string>

<string lang="ko" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">멀티-부트</string>

<string lang="ko" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt는 MBR에 비-윈도우 부트 로더가 설치되어 있는 멀티-부트 설정을 현재 지원하지 않고 있습니다.\n\n가능한 해결책:\n\n- 윈도우와 리눅스를 부팅하기 위해 부트 관리자(보통 GRUB)를 사용 중이라면, 부트 관리자를 MBR에서 특정 파티션으로 이동시킵니다. 그런 다음 이 마법사를 다시 시작하고 시스템 파티션/드라이브를 암호화합니다. VeraCrypt 부트 로더는 사용자의 주요한 부트 관리자가 될 것이고, 원래의 부트 관리자(보통 GRUB)는 (VeraCrypt 부트 로더 화면에서 Esc를 눌러) 부차적으로 사용할 수 있습니다. 이런 방법으로 리눅스를 부팅할 수 있게 됩니다.</string>

<string lang="ko" key="WINDOWS_BOOT_LOADER_HINTS">현재 실행 중인 운영체제가 부트 파티션에 설치된 경우, 시스템을 암호화 후에는 (비록 사용자가 암호화되지 않은 다른 시스템을 시작하기를 원할 경우일지라도) 사용자는 올바른 비밀번호를 입력할 필요가 있습니다.\n\n반대로 현재 실행 중인 운영체제가 윈도우 부트 파티션에 설치되어 있지 않은 경우 (또는 윈도우 부트 로더/관리자가 다른 시스템에 의해 사용되지 않고 있는 경우), 시스템을 암호화한 후에는 암호화되지 않은 시스템을 부팅하기 위해 올바른 비밀번호를 입력할 필요가 없습니다. -- 암호화되지 않은 시스템을 시작하려면 Esc 키만 누르면 됩니다. (만약 다수의 암호화되지 않은 시스템이 있는 경우라면, VeraCrypt Boot Manager 메뉴에서 시작할 시스템을 선택할 필요가 있습니다.)\n\n참고: 보통 가장 초기에 설치된 윈도우 시스템은 부트 파티션에 설치되어 있습니다.</string>

<string lang="ko" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">호스트로 보호된 영역의 암호화</string>

<string lang="ko" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">많은 드라이브의 끝에는 이른바 “호스트로 보호된 영역(Host Protected Area)”이라 불리며 대개 운영체제로부터 숨겨진 영역이 있습니다. 그러나 일부 프로그램은 그러한 영역의 데이터를 읽고 쓸 수 있습니다.\n\n주의: 일부 컴퓨터 제작자들은 그러한 영역에 RAID, 시스템 복구, 시스템 설정, 진단 또는 다른 목적을 위한 도구 및 데이터를 저장하기도 합니다. 만약 부팅-전에 그러한 도구 또는 데이터에 접근할 수 있는 경우라면, 숨긴 영역을 암호화해서는 안됩니다(→ 위에서 “아니오” 선택).\n\n시스템 드라이브의 끝에 있는 그러한 숨긴 영역이 존재하는 경우에 VeraCrypt가 이를 발견해서 암호화하도록 하시겠습니까?</string>

<string lang="ko" key="SYSENC_TYPE_PAGE_TITLE">시스템 암호화 형식</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="my" key="LAUNCH_WIN_ISOBURN">မိုက်ခရိုဆော့ဗ်ဝဲ ၀င်းဒိုး Disc Image Burner ကို ဖွင့်ရန်</string>

<string lang="my" key="RESCUE_DISK_BURN_NO_CHECK_WARN">သတိပေးချက် - ယခင်က VeraCrypt ဆယ်တင်ရေး အခွေကို ဖန်တီးခဲ့ပြီး ဖြစ်ပါက၊ ၄င်းကို ကွန်ပျူတာစနစ် အခန်းကန့်/drive အတွက် ပြန်သုံး၍ ရမည် မဟုတ်ပါ၊ အဘယ့်ကြောင့် ဆိုသော်၊ ၄င်းကို အခြား မာစတာကီးအတွက် ဖန်တီးထားသောကြောင့် ဖြစ်သည်။ ကွန်ပျူတာစနစ် အခန်းကန့်/drive ကို သင် စာဝှက်သည့်အချိန်တိုင်း၊ စကားဝှက် တစ်ခုတည်းကို သင် အသုံးပြုလျှင်လည်း VeraCrypt ဆယ်တင်ရေး အခွေ တစ်ခုကို သင် ဖန်တီးရမည် ဖြစ်သည်။</string>

<string lang="my" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">ချို့ယွင်းချက် - ကွန်ပျူတာစနစ် စာဝှက်ခြင်း ချိန်ညှိချက်များကို သိမ်းဆည်း၍ မရပါ။</string>

<string lang="my" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">ကွန်ပျူတာစနစ် စာဝှက်ခြင်း အကြိုစစ်ဆေးချက်ကို မစတင်နိုင်ပါ။</string>

<string lang="my" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">လျှို့ဝှက် OS စနစ် ဖန်တီးမှု လုပ်ငန်းစဉ် မစတင်နိုင်ပါ။</string>

<string lang="my" key="WIPE_MODE_TITLE">ရှင်းလင်းမှု စနစ်</string>

<string lang="my" key="INPLACE_ENC_WIPE_MODE_INFO">အချို့ သိုလှောင်ရေး မီဒီယာ အမျိုးအစားများ၌၊ ဒေတာကို အခြား ဒေတာများနှင့် ​အစားထိုးသည့်အခါ၊ magnetic force microscopy ကဲ့သို့သော နည်းပညာကို သုံးပြီး အစားထိုးလိုက်သော ဒေတာများကို ပြန်လည် ဆယ်တင်နိုင်သည်။ ဤနေရာ၌ ၄င်းတို့ (VeraCrypt အနေဖြင့် စာဝှက်မထားသော အခန်းကန့် သို့မဟုတ် drive ကို စတင် စာဝှက်သည့်အခါ ပေါ်ပေါက်လာသော) စာဝှက်ထားသည့် ဖြည့်စွတ်ပုံစံဖြင့် အစားထိုးလိုက်သော ဒေတာများလည်း အကျုံး၀င်သည်။ ထို့ကြောင့်၊ အကယ်၍ ရန်သူ တစ်ဦးတစ်ယောက်က သင် စာဝှက်ရန် ရည်ရွယ်ထားသော ဒေတာများကို ဆယ်တင်နိုင်​သည့် နည်းလမ်းများကို အသုံးပြုနိုင်လျှင်၊ ရှင်းလင်းသော စနစ် (လက်ရှိ ဒေတာများ ပျောက်သွားမည် မဟုတ်ပါ) တစ်ခုခုကို သင် ရွေးချယ်နိုင်သည်။ အခန်းကန့်/drive ကို စာဝှက်ပြီးသည့်အခါ ရှင်းလင်းမှု ပြုလုပ်တော့မည် မဟုတ်ပါ။ အခန်းကန့်/drive ကို အပြည့်အ၀ စာဝှက်သည့်အခါ၊ ၄င်းအထဲ၌ စာဝှက်မထားသော ဒေတာများကို ရေးသားခြင်း မပြုပါ။ ၄င်းအထဲ၌ ပထမဦးဆုံး ရေးသားလိုက်သော ဒေတာများကို မှတ်ဉာဏ်ထဲ၌ ချက်ခြင်း စာဝှက်လိုက်ပြီးနောက် (စာဝှက်ထားသော) ဒေတာများကို disk ထဲ၌ ရေးထည့်လိုက်သည်။</string>

<string lang="my" key="WIPE_MODE_INFO">အချို့ သိုလှောင်ရေး မီဒီယာ အမျိုးအစားများ၌၊ ဒေတာကို (ဒေတာများကို ပယ်ဖျက်သည့်အခါ) အခြား ဒေတာများနှင့် ​အစားထိုးသည့်အခါ၊ magnetic force microscopy ကဲ့သို့သော နည်းပညာကို သုံးပြီး အစားထိုးလိုက်သော ဒေတာများကို ပြန်လည် ဆယ်တင်နိုင်သည်။ အချို့သော လေ့လာ ဆန်းစစ်ချက်များနှင့် အစိုးရ ထုတ်ပြန်ချက်များအရ၊ ဒေတာများကို pseudorandom စနစ်နှင့် အချို့ ကျပန်း မဟုတ်သော ဒေတာများကို အကြိမ်ကြိမ် အစားထိုးခြင်းဖြင့် ဒေတာများ ပြန်လည်ဆယ်တင်နိုင်မှုကို တားဆီး (ခက်ခဲစေ) နိုင်သည်။ ထို့ကြောင့်၊ အကယ်၍ ရန်သူ တစ်ဉီးတစ်ယောက်သည် ပယ်ဖျက်​မည့် ဒေတာများကို ဆယ်တင်နိုင်သည့် နည်းလမ်းများကို သုံးစွဲနိုင်လျှင်၊ အကြိမ်ပေါင်း များစွာ ရှင်းလင်းပေးသည့် စနစ် တစ်ခုခုကို ရွေးချယ်ရမည် ဖြစ်သည်။\n\nမှတ်ချက် - အကြိမ်များများ ရွေးလေ၊ ဒေတာ ရှင်းလင်းမှု ကြာလေ ဖြစ်သည်။</string>

<string lang="my" key="DEVICE_WIPE_PAGE_TITLE">ရှင်းလင်းနေသည်</string>

<string lang="my" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n မှတ်ချက် - ရှင်းလင်းသည့် လုပ်ငန်းစဉ်ကို သင် ရပ်ဆိုင်းနိုင်သည်၊ ကွန်ပျူတာကို ပိတ်နိုင်သည်၊ လျှို့ဝှက် ကွန်ပျူတာစနစ်ကို နောက်တစ်ခါ ပြန်​ဖွင့်ပြီး လုပ်ငန်းစဉ် (ဤအညွှန်းကို အလိုအလျောက် စတင်နိုင်သည်) ကို ပြန်စတင်နိုင်သည်။ သို့သော်၊ အကယ်၍ ၄င်းကို ရပ်လိုက်ပါက၊ ရှင်းလင်းသော လုပ်ငန်းစဉ် တစ်ခုလုံး အစမှ ပြန်လည် စတင်မည် ဖြစ်သည်။</string>

<string lang="my" key="DEVICE_WIPE_PAGE_INFO">\n\n မှတ်ချက် - အကယ်၍ ရှင်းလင်းသော လုပ်ငန်းစဉ်ကို သင် ရပ်တန့်ပါက၊ ၄င်းကို ပြန်စပါ။ လုပ်ငန်းစဉ် တစ်ခုလုံးကို အစမှ ပြန်လည် စတင်ရမည် ဖြစ်သည်။</string>

<string lang="my" key="CONFIRM_WIPE_ABORT">ရှင်းလင်းခြင်း လုပ်ငန်းစဉ်ကို ရပ်ဆိုင်းမည်လား?</string>

<string lang="my" key="CONFIRM_WIPE_START">သတိပေးချက် - ရွေးချယ်ထားသော အခန်းကန့်/device တစ်ခုလုံးကို ပယ်ဖျက်သွားမည် ဖြစ်ပြီး ပျောက်ဆုံးသွားမည် ဖြစ်သည်။</string>

<string lang="my" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">မူရင်း ကွန်ပျူတာစနစ် တည်ရှိသော အခန်းကန့်ထဲရှိ အကြောင်းအရာ တစ်ခုလုံးကို ပယ်ဖျက်သွားမည် ဖြစ်သည်။\n\n မှတ်ချက် - ပယ်ဖျက်သွားမည့် အခန်းကန့်ထဲရှိ အကြောင်းအရာ တစ်ခုလုံးကို လျှို့ဝှက် ကွန်ပျူတာစနစ်ထဲသို့ ကော်ပီကူးသွားမည် ဖြစ်သည်။</string>

<string lang="my" key="WIPE_MODE_WARN">သတိပေးချက် - ရှင်းလင်းမှု စနစ် 3-pass (ခေါ် သုံးကြိမ်) ကို ရွေးချယ်လိုက်ပါက၊ အခန်းကန့်/drive ကို စာဝှက်ရန် အချိန် ၄ ဆ ပိုကြာမည် ဖြစ်သည်။ ထိုနည်းတူ၊ အကယ်၍ 35-pass ကို ရွေးပါက ၃၆ ဆ ပိုကြာသွားမည် ဖြစ်သည်။\n\n သို့သော်၊ အခန်းကန့်/drive ကို အပြည့်အ၀ စာဝှက်ပြီးသည့်အခါ ရှင်းလင်းသည့် လုပ်ငန်းကို လုပ်ဆောင်မည် မဟုတ်ပါ။ အခန်းကန့်/drive ကို အပြည့်အ၀ စာဝှက်ပြီးသည့်အခါ၊ ၄င်းအထဲ၌ စာဝှက်မထားသေးသော ဒေတာများကို ရေးသားမည် မဟုတ်ပါ။ ၄င်းအထဲ၌ ရေးသားလိုက်သော ဒေတာ အားလုံးကို ချက်ခြင်း စာဝှက်သွားမည် ဖြစ်ပြီး၊ ထို့နောက်မှ (စာဝှက်ထားသော) ဒေတာများကို disk ထဲ၌ ရေးသားမည် ဖြစ်သည် (ဤနည်းဖြင့် စွမ်းဆောင်ရည်ကို ထိခိုက်မည် မဟုတ်ပါ)။\n\n ရှင်းလင်းမှု စနစ်ကို သုံးစွဲလိုသလား?</string>

<string lang="my" key="WIPE_MODE_NONE">ဘာမျှမရွေး (အမြန်ဆုံး)</string>

<string lang="my" key="WIPE_MODE_1_RAND">၁-ကြိမ် (ကျပန်း ဒေတာ)</string>

<string lang="my" key="WIPE_MODE_3_DOD_5220">၃-ကြိမ် (US DoD 5220.22-M)</string>

<string lang="my" key="WIPE_MODE_7_DOD_5220">၇-ကြိမ် (US DoD 5220.22-M)</string>

<string lang="my" key="WIPE_MODE_35_GUTMANN">၃၅-ကြိမ် ("Gutmann")</string>

<string lang="my" key="SYS_MULTI_BOOT_MODE_TITLE">OS စနစ် အရေအတွက်</string>

<string lang="my" key="MULTI_BOOT_FOR_ADVANCED_ONLY">သတိပေးချက် - အတွေ့အကြုံမရှိသေးသော သုံးစွဲသူများသည် ၀င်းဒိုးကို Multi-boot ပြုပြင်ဖန်တီးစနစ်ဖြင့် စာဝှက်ရန် မကြိုးစားသင့်ပါ။\n\n ဆက်လုပ်မည်လား?</string>

<string lang="my" key="HIDDEN_OS_MULTI_BOOT">လျှို့ဝှက် OS စနစ်ကို ဖန်တီး/သုံးစွဲသည့်အခါ၊ VeraCrypt သည် အောက်ပါ အခြေအနေများနှင့် ကိုက်ညီမှ multi-boot ပြုပြင်ဖန်တီးမှုကကို ထောက်ပံ့ပေးသည် -\n\n- လောလောဆယ် အသုံးပြုနေသော OS စနစ်ကို boot drive ထဲတွင် ထည့်သွင်းရမည် ဖြစ်သည်၊ ၄င်း၌ အခြား OS စနစ်များ ရှိမည် မဟုတ်ပါ။\n\n အခြား drives များ၌ ထည့်သွင်းထားသော OS စနစ်များသည် လောလောဆယ် အသုံးပြုနေသော OS စနစ် ထည့်သွင်းထားသည့် drive ထဲတွင် ရှိသော မည်သည့် boot loader ကို အသုံးမပြုရပါ။\n\n အထက်မှ အခြေအနေများနှင့် ကိုက်ညီသလား?</string>

<string lang="my" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt သည် လျှို့ဝှက် OS စနစ်ကို ဖန်တီး/သုံးစွဲသည့်အခါ ဤ multi-boot ပြုပြင်ဖန်တီးမှုကို လက်မခံပါ။</string>

<string lang="my" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="my" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">လက်ရှိ အသုံးပြုနေသော OS စနစ်ကို boot drive ပေါ်တွင် ထည့်သွင်းထားသလား?\n\nမှတ်ချက် - တစ်ခါတစ်ရံ၊ Windows ကို Windows boot loader (boot အခန်းကန့်) ကဲ့သို့ drive တစ်ခုထဲ၌ ထည့်သွင်းမထားပါ။ အကယ်၍ ပြဿနာ ရှိပါက၊ 'မဟုတ်ဘူး' ကို ရွေးပါ။</string>

<string lang="my" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">လော​လောဆယ်၌ VeraCrypt သည် OS စနစ် ထည့်သွင်းထားသော drive မှ boot မလုပ်သော OS စနစ်ကို စာဝှက်ရန် ထောက်ပံ့​မပေးပါ။</string>

<string lang="my" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">ကွန်ပျူတာစနစ် Drives အရေအတွက်</string>

<string lang="my" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">OS စနစ် တစ်ခု၌ drives မည်မျှ ပါရှိသနည်း?\n\n မှတ်ချက် - ဥပမာ- ဥပမာ အားဖြင့်၊ သင့် primary drive နှင့် အခြား OS စနစ်ကို secondary drive ထဲ၌ OS စနစ် (Windows, Mac OS X, Linux နှင့်အခြား) ကို ထည့်သွင်းထားလျှင်၊ '၂ (သို့) အထက်' ကို ရွေးချယ်ပါ။</string>

<string lang="my" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt သည် OS စနစ် အများ ပါရှိသော drive တစ်ခုလုံးကို စာဝှက်ရန် ထောက်ပံ့မှု မပေးပါ။\n\nဖြစ်နိုင်သော ဖြေရှင်းချက်များ -\n\n အကယ်၍ နောက် ပြန်သွားပြီး ကွန်ပျူတာစနစ် အခန်းကန့် တစ်ခုကို သာ စာဝှက်ရန် ရွေးချယ်ပါက ကွန်ပျူတာ စနစ်ထဲက တစ်ခုကို သင် စာဝှက်နိုင်မည် ဖြစ်သည်။\n\n နောက်တနည်းဖြင့်၊ သင် စာဝှက်လိုသော drive ထဲ၌ ကွန်ပျူတာစနစ် တစ်ခုကိုသာ ချန်ထားပြီး အချို့ ကွန်ပျူတာစနစ်ကို အခြား drives ထဲ၌ ရွေ့သွားပါက၊ drive တစ်ခုလုံးကို သင် စာဝှက်နိုင်မည် ဖြစ်သည်။</string>

<string lang="my" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Drive တစ်ခုထဲ၌ ကွန်ပျူတာစနစ် မျိုးစုံ</string>

<string lang="my" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">လက်ရှိ အသုံးပြုနေသော OS စနစ်ကို ထည့်သွင်းထားသော drive ၌ OS စနစ် ဘယ်နှစ်ခု ထည့်သွင်းထားသနည်း။\n\nမှတ်ချက် - ဥပမာ အားဖြင့်၊ အကယ်၍ လက်ရှိ အသုံးပြုနေသော OS စနစ်ကို အခန်းကန့် တချို့ ပါရှိသော drive #0 ထဲ၌ ထည့်သွင်းပါက၊ နောက်ပြီး အကယ်၍ အခန်းကန့် တစ်ခု၌ Windows နှင့် အခြား အခန်းကန့်၌ နောက်ထပ် OS စနစ် (ဥပမာ -Windows, Mac OS X, Linux, စသဖြင့်) ပါရှိပါက၊ ​'ဟုတ်ကဲ့' ကို ရွေးပါ။</string>

<string lang="my" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">ဝင်းဒိုးမဟုတ်သည့် Boot Loader</string>

<string lang="my" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">The master boot record (MBR) ထဲတွင် (boot manager မဟုတ်သော) non-Windows boot loader ကို ထည့်သွင်းထားသလား?\n\n မှတ်ချက် - ဥပမာ အားဖြင့်၊ ပထမ boot drive လမ်းကြောင့်၌ GRUB, LILO, XOSL ၊ (သို့) အခြား non-Windows boot manager (boot loader) ပါရှိပါက၊ 'ဟုတ်ကဲ့' ကို နှိပ်ပါ။ </string>

<string lang="my" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="my" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt သည် လောလောဆယ် Master Boot Record ၌ ထည့်သွင်းထားသော non-Windows boot loader တစ်ခု ရှိသည့်နေရာ၌ multi-boot ပြုပြင်ဖန်တီးခြင်းကို အထောက်အပံ့ ​မပေးပါ။\n\n ဖြစ်နိုင်ချေ ဖြေရှင်းချက်များ -\n\n - အကယ်၍ Windows နှင့် Linux တို့ကို ဖွင့်ရန် boot manager တစ်ခုကို အသုံးပြုပါက၊ boot manager(GRUB) ကို Master Boot Record မှ အခန်းကန့် တစ်ခုသို့ ရွေ့ပြောင်းပါ။ ​ထို့နောက် ဒီအညွှန်းကို စဖွင့်ပြီး ကွန်ပျူတာစနစ် အခန်းကန့်/driveကို စာဝှက်လိုက်ပါ။ VeraCrypt Boot Loader သည် သင့် primary boot manager ဖြစ်လာမည် ဖြစ်ပြီး ၄င်းမှ မူရင်း boot manager (ဥပမာ - GRUB) ကို secondary boot manager အဖြစ် (VeraCrypt Boot Loader မျက်နှာပြင်မှ Esc ကို နှိပ်ခြင်းပြီး) ဖွင့်ပေးနိုင်မည် ဖြစ်သည်။ ထို့နောက် Linux ကို boot လုပ်နိုင်မည် ဖြစ်သည်။</string>

<string lang="my" key="WINDOWS_BOOT_LOADER_HINTS">အကယ်၍ လက်ရှိ သုံးစွဲနေသော OS စနစ်သည် boot အခန်းကန့်ပေါ်တွင် ထည့်သွင်းထားပါက၊ ၄င်းကို စာဝှက်ပြီးသောအခါ၊ အခြား စာဝှက်မထားသော Windows စနစ်(များ)ကို စတင်လိုလျှင်လည်း စကားဝှက်အမှန်ကို ရေးထည့်ရမည် ဖြစ်သည် (၄င်းတို့သည် စာဝှက်ထားသော Windows boot loader/manager တစ်ခုတည်းကို ဝေမျှကြမည် ဖြစ်သောကြောင့် ဖြစ်သည်)။\n\n နောက်တစ်မျိုး အနေနဲ့၊ အကယ်၍ သင် လက်ရှိ သုံးစွဲနေသော OS စနစ်ကို boot အခန်းကန့် (သို့မဟုတ် အကယ်၍ Windows boot loader/manager ကို အခြား ကွန်ပျူတာ စနစ်က အသုံးမပြုပါက) တွင် ထည့်သွင်းမထားပါက၊ ဤကွန်ပျူတာစနစ်ကို စာဝှက်ပြီးနောက်၊ အခြား စာဝှက်မထားသော ကွန်ပျူတာစနစ်(များ)ကို ဖွင့်သည့်အခါ စကားဝှက် အမှန်ကို ​ရေးထည့် မလိုပါ -- စာဝှက်မထားသော ကွန်ပျူတာစနစ်ကို စဖွင့်ရန် Esc ကီးကိုသာ နှိပ်ရမည် ဖြစ်သည် (အကယ်၍ စာဝှက်မထားသော ကွန်ပျူတာစနစ် အများအပြား ရှိပါက၊ VeraCrypt Boot Manager မီနူးမှ သင် ဖွင့်လိုသော ကွန်ပျူတာ စနစ်ကို ရွေးချယ်ရမည် ဖြစ်သည်)။\n\nမှတ်ချက် - ပုံမှန်အားဖြင့်၊ အစောဆုံး ထည့်သွင်းထားသော OS စနစ်ကို boot အခန်းကန့်တွင် ထည့်သွင်းထားသည်။</string>

<string lang="my" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Host Protected Area ကို စာဝှက်ခြင်း</string>

<string lang="my" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Drives များ၏ အဆုံး၌၊ OS စနစ်မှ ဖျောက်ထားသော နေရာ တစ်ခု ရှိသည် (ယင်းနေရာမျိုးကို Host Protected Areas ဟု​ ခေါ်သည်)။ သို့သော်၊ ယင်းနေရာများမှ ဒေတာများကို အခြား ပရိုဂရမ်များက ဖတ်နိုင်၊ ရေးနိုင်သည်။\n\n သတိပေးချက် - အချို့ ကွန်ပျူတာ ထုတ်လုပ်သူများသည် ယင်းနေရာများကို ​ကိရိယာများနှင့် RAID ဒေတာများ၊ ကွန်ပျူတာစနစ် ဆယ်တင်ရေး၊ ကွန်ပျူတာစနစ် တည်ဆောက်ခြင်း၊ ပြဿနာ ရှာဖွေခြင်း၊ (သို့) အခြား ​ရည်ရွယ်ချက်များ သိမ်းဆည်းရန်အတွက် သုံးစွဲနိုင်သည်။ ​ယင်းကဲ့သို့ ကိရိယာများ (သို့) ဒေတာများကို boot မလုပ်ခင်၊ လျှို့ဝှက် နေရာကို စာဝှက်မည် မဟုတ်ပါ (အထက်မှ 'မဟုတ်ဘူး' ကို ရွေးပါ)။\n\n VeraCrypt သည် ကွန်ပျူတာစနစ် drive ၏ အဆုံး၌ လျှို့ဝှက် နေရာ တစ်ခုကို ရှာဖွေပြီး စာဝှက်လိုသလား?</string>

<string lang="my" key="SYSENC_TYPE_PAGE_TITLE">ကွန်ပျူတာ စာဝှက်စနစ် အမျိုးအစား</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="nl" key="RESCUE_DISK_BURN_NO_CHECK_WARN">LET OP: Indien u een VeraCrypt Reddingsschijf heeft kan deze niet gebruikt worden voor deze systeem partitie/schijf omdat hij is gemaakt voor een andere master key! Na iedere codering van een systeem partitie/schijf moet een nieuwe reddingsschijf worden aangemaakt, zelfs als u hetzelfde wachtwoord gebruikt.</string>

<string lang="nl" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Fout: Kan de systeem codering settings niet opslaan.</string>

<string lang="nl" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Kan de systeem codering pre-test niet initiëren.</string>

<string lang="nl" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Voorbereiding tot aanmaak van verborgen operating system mislukt.</string>

<string lang="nl" key="WIPE_MODE_TITLE">Wis Modus</string>

<string lang="nl" key="INPLACE_ENC_WIPE_MODE_INFO">Op sommige typen opslagmedia is het mogelijk oorspronkelijke data, die overschreven zijn door andere data, weer te herstellen met geavanceerde technieken. Dit geldt ook voor data die worden overschreven door hun gecodeerde variant. (Dit gebeurt als VeraCrypt een ongecodeerde partitie of schijf codeert.) Volgens studies en overheidspublicaties kan deze hersteltechniek voorkomen worden (of zeer bemoeilijkt) door de data eerst een aantal malen met pseudo-random en niet-random data te overschrijven. Indien u gelooft dat een vijand mogelijk uw originele data met een dergelijke techniek zou kunnen herstellen, kunt u één van de volgende wismethoden kiezen (let op bestaande data gaan NIET verloren). Merk op dat het wissen NIET zal plaatsvinden na de codering van de partitie/schijf. Als de partie/schijf geheel is gecodeerd worden er geen ongecodeerde data meer op geschreven, deze data worden in het interne geheugen “on the fly” gecodeerd en daarna pas weggeschreven naar de schijf.</string>

<string lang="nl" key="WIPE_MODE_INFO">Op sommige typen opslagmedia is het mogelijk oorspronkelijke data, die overschreven zijn door andere data, weer te herstellen met geavanceerde technieken. Volgens studies en overheidspublicaties kan deze hersteltechniek voorkomen worden (of zeer bemoeilijkt) door de data eerst een aantal malen met pseudo-random en niet-random data te overschrijven. Indien u gelooft dat een vijand mogelijk uw originele data die gewist gaat worden met een dergelijke techniek zou kunnen herstellen, kunt u één van de volgende cyclische wismethoden kiezen.\n\nNoot:Hoe meer wis cycli u kiest, des te langer zal het proces duren.</string>

<string lang="nl" key="DEVICE_WIPE_PAGE_TITLE">Wissen</string>

<string lang="nl" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNoot: U kunt het wisproces onderbreken, de computer afsluiten, het verborgen systeem opnieuw starten en het proces weer hervatten (deze wizard zal automatisch weer worden gestart). Echter, het wisproces zal dan weer van voren af beginnnen.</string>

<string lang="nl" key="DEVICE_WIPE_PAGE_INFO">\n\nNoot: Als u het wisproces onderbreekt en het probeert te hervatten, zal het gehele wisproces van voren af beginnen.</string>

<string lang="nl" key="CONFIRM_WIPE_ABORT">Wilt u het wisproces afbreken?</string>

<string lang="nl" key="CONFIRM_WIPE_START">LET OP: De gehele inhoud van deze partitie/apparaat zal worden gewist.</string>

<string lang="nl" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">De gehele inhoud van de partitie waar het originele system staat wordt gewist.\n\nNoot: De gehele inhoud van de te wissen partitie is reeds gekopieerd naar de verborgen systeem partitie.</string>

<string lang="nl" key="WIPE_MODE_WARN">WAARSCHUWING: indien u bijv. de 3-cycli wismodus kiest, zal de tijd die nodig is om de partitie/schijf te coderen tot 4 maal langer duren. Zo ook zal, indien u de 35-cycli modus kiest, de benodigde tijd tot 36 maal langer duren. Dit kan zelfs oplopen tot enkele weken.\n\nEchter, merk op dat wissen niet zal geschieden na volledige codering van de partitie/schijf. Wanneer deze codering voltooid is zullen alle data die er naartoe geschreven worden eerst volledig in het interne geheugen gecodeerd worden alvorens geschreven te worden. Dan wordt de performance dus NIET aangetast.\n\nBent u er zeker van dat u de wismodus wilt kiezen?</string>

<string lang="nl" key="WIPE_MODE_NONE">Geen (snelst)</string>

<string lang="nl" key="WIPE_MODE_1_RAND">1-maal (random data)</string>

<string lang="nl" key="WIPE_MODE_3_DOD_5220">3-maal (US DoD 5220.22-M)</string>

<string lang="nl" key="WIPE_MODE_7_DOD_5220">7-maal (US DoD 5220.22-M)</string>

<string lang="nl" key="WIPE_MODE_35_GUTMANN">35-maal ("Gutmann")</string>

<string lang="nl" key="SYS_MULTI_BOOT_MODE_TITLE">Aantal Operating Systemen</string>

<string lang="nl" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WAARSCHUWING: Onervaren gebruikers wordt het dringend afgeraden Windows te coderen in een multi-boot configuratie.\n\nDoorgaan?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Schijf</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is het nu actieve operating systeem geïnstalleerd op de boot-schijf?\n\nNoot: Soms is Windows niet geïnstalleerd op dezelfde schijf als de Windows Boot Lader (boot partitie). Indien dit het geval is, kies 'Nee'.</string>

<string lang="nl" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt ondersteunt momenteel niet het coderen van een operating systeem dat niet opstart vanaf de schijf waarop het is geïnstalleerd.</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Aantal Systeem Schijven</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Hoeveel schijven bevatten een operating systeem?\n\nNoot: Bijvoorbeeld, als u een operating systeem (bijv. Windows, Mac OS X, Linux, etc.) heeft geïnstalleerd op de primaire schijf en enig toegevoegd operating systeem geïnstalleerd op een secundair schijf, selecteer dan '2 of meer'.</string>

<string lang="nl" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt ondersteunt momenteel geen codering van een gehele schijf die meerdere operating systemen bevat.\n\nMogelijke oplossingen:\n\n- U kunt nog steeds één van de systemen coderen als u terug gaat en kiest voor codering van een enkele systeem partitie (in tegenstelling tot het coderen van een gehele systeem schijf).\n\n- Als een alternatief kunt u de gehele schijf coderen als u enkele van de systemen verplaatst naar een andere schijf zodat er maar één systeem achterblijft op de schijf die u wilt coderen.</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Meerdere Systemen op Enkele Schijf</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Zijn er andere operating systemen geïnstalleerd op de schijf waarop het huidige actieve operating systeem is geïnstalleerd?\n\nNoot: Bijvoorbeeld, als het huidige actieve operating systeem is geïnstalleerd op schijf #0, dat meerdere partities bevat, en indien één van deze partities Windows bevat en een andere partitie bevat een ander operating systeem (bijv. Windows, Mac OS X, Linux, etc.), selecteer dan 'Ja'.</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Niet-Windows Boot Lader</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is een niet-Windows boot lader (of boot manager) geïnstalleerd in het Master Boot Record (MBR)?\n\nNoot: Als de eerste track van de boot schijf bijv. GRUB, LILO, XOSL of een andere niet-Windows boot manager (of boot lader) bevat, klik dan op ‘Ja’.</string>

<string lang="nl" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="nl" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt ondersteunt momenteel geen multi-boot configuraties waar een niet-Windows boot lader is geïnstalleerd in het Master Boot Record.\n\nMogelijke oplossingen:\n\n- Als u een boot manager gebruikt om Windows en Linux te starten, verplaats de boot manager (meestal GRUB) van het Master Boot Record naar een partitie. Start dan deze wizard nogmaals en codeer de systeem partitie/schijf. Merk op dat de VeraCrypt Boot Lader uw primaire boot manager zal worden en u zal toestaan de originele boot manager (bijv. GRUB) te starten als een secundaire boot manager (door op ESC te drukken in het VeraCrypt Boot Lader scherm). Aldus zult u Linux kunnen starten.</string>

<string lang="nl" key="WINDOWS_BOOT_LOADER_HINTS">Als het nu draaiende operating system (OS) is geïnstalleerd op de boot partitie zult u na codering ervan het wachtwoord dienen op te geven, zelfs als u een ander ongecodeerd Windows systeem wilt starten. Dit omdat ze dezelfde gecodeerde Windows boot lader/manager delen.\n\nIn contrast hiermee: als het nu draaiende OS NIET geïnstalleerd is op de boot partitie (of als de Windows boot lader/manager niet door een ander systeem wordt gebruikt) dan zal, na codering van dit systeem het ingeven van een wachtwoord voor andere ongecodeerde syste(e)m(en) niet nodig zijn. Dan zal alleen het indrukken van de ESC toets voldoende zijn om het ongecodeerde systeem te starten. (Indien er meerdere van deze ongecodeerde systemen zijn zult u in het VeraCrypt Boot Manager Menu moeten aangeven welk systeem te starten).\n\nNoot: Kenmerkend is dat het éérst geïnstalleerde Windows systeem op de boot partitie staat.</string>

<string lang="nl" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Codering van "Host Protected Area"</string>

<string lang="nl" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Aan het einde van veel harde schijven bestaat een gebied dat normaal gesproken verborgen is voor het operating systeem, het ‘Hort Protected Area’ (HPA). Sommige programma’s kunnen echter data lezen en schrijven naar dit gebied.\n\nWAARSCHUWING: Sommige computerfabrikanten gebruiken dit gebied voor de opslag van tools, data voor RAID, systeemherstel, systeem setup, diagnostiek enz. Indien deze data toegankelijk moeten zijn vóór het opstarten, mag de HPA NIET gecodeerd worden. (Kies boven ‘Nee’)\n\nWilt u dat VeraCrypt een HPA opzoekt en codeert?</string>

<string lang="nl" key="SYSENC_TYPE_PAGE_TITLE">Type Systeem Codering</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="pl" key="LAUNCH_WIN_ISOBURN">Załaduj Nagrywanie Płyt (obrazów) Microsoft Windows</string>

<string lang="pl" key="RESCUE_DISK_BURN_NO_CHECK_WARN">UWAGA: Stworzona Płyta Ratunkowa VeraCrypt, nie może być odtąd użyta do tego systemu partycji/dysku bo został stworzony z innym kluczem głównym! Za każdym razem gdy szyfrujesz system partycję/dysk musisz stworzyć nową Płytę Ratunkową VeraCrypt nawet jeśli użyjesz tego samego hasła.</string>

<string lang="pl" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Błąd: Nie można zapisać systemowych ustawień szyfrowania.</string>

<string lang="pl" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Nie można zainicjować testu szyfrowania systemu.</string>

<string lang="pl" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Proces tworzenia ukrytego systemu operacyjnego nie może zostać zainicjowany.</string>

<string lang="pl" key="WIPE_MODE_TITLE">Tryb wymazywania</string>

<string lang="pl" key="INPLACE_ENC_WIPE_MODE_INFO">Na niektórych typach urządzeń, jeżeli dane są nadpisywane, może być możliwe odtworzenie ich. Stosuje się również metodę nadpisania danych ich zaszyfrowaną zawartością (co ma miejsce podczas rozpoczęcia szyfrowania w VeraCrypt niezaszyfrowanej partycji lub dysku). Zgodnie z nauką i rządowymi publikacjami, odtworzenie nadpisanych danych może być niemożliwe (lub może być bardzo trudne) przez nadpisanie danych losowymi danymi i pewną nie losową kombinacją liczb kilka razy. Dlatego, jeżeli chcesz wierzyć że przeciwnik nie będzie mógł odzyskać skasowanych danych, powinieneś wybrać jeden z trybów czyszczenia/wymazywania z wieloprzebiegowych. Notka czyszczenie/wymazywanie NIE może być wykonane zaszyfrowania partycji/dysku. Kiedy partycja/dysk jest w pełni zaszyfrowana, niezaszyfrowane dane są zapisane jako zaszyfrowane. Wiele danych zapisanych jest najpierw do pamięci, szyfowanych "w locie" i zapisywanych zaszyfrowanych na dysku (tak aby nie obniżyć wydajności).</string>

<string lang="pl" key="WIPE_MODE_INFO">Na niektórych typach urządzeń, jeżeli dane są nadpisywane, może być możliwe odtworzenie ich używając specjalnych technik, np. mikroskopu sił magnetycznych. Zgodnie z nauką i rządowymi publikacjami, odtworzenie nadpisanych danych może być niemożliwe (lub może być bardzo trudne) przez nadpisanie danych losowymi danymi i pewną nielosową kombinacją liczb kilka razy. Dlatego, jeżeli obawiasz się że przeciwnik będzie mógł odzyskać skasowane dane, powinieneś wybrać jeden z trybów czyszczenia/wymazywania z wieloprzebiegowych.\n\nNotka: Im więcej przebiegów użyjesz, tym dłużej będzie trwało kasowanie danych.</string>

<string lang="pl" key="DEVICE_WIPE_PAGE_TITLE">Wymazywanie</string>

<string lang="pl" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNotka: Możesz przerwać proces czyszczenia/wymazywania, wyłączyć komputer, uruchomić ponownie ukryty system i wznowić proces (ten kreator włączy się automatycznie). Jednakże, jeżeli przerwiesz proces czyszczenia/wymazywania i później go wznowisz, cały proces wystartuje od początku.</string>

<string lang="pl" key="DEVICE_WIPE_PAGE_INFO">\n\nNotka: Jeżeli przerwiesz proces czyszczenia/wymazywania i później go wznowisz, cały proces wystartuje od początku.</string>

<string lang="pl" key="CONFIRM_WIPE_ABORT">Czy chcesz przerwać proces wymazywania?</string>

<string lang="pl" key="CONFIRM_WIPE_START">UWAGA: Cała zawartość zaznaczonej partycji/urządzenia zostanie skasowana i utracona.</string>

<string lang="pl" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Cała zawartość partycji gdzie jest oryginalny system operacyjny zostanie skasowana.\n\nUwaga: Cała zawartość partycji, która ma być skasowana została skopiowana do ukrytej partycji systemowej.</string>

<string lang="pl" key="WIPE_MODE_WARN">OSTRZEŻENIE: Pamiętaj, że jeżeli wybrałeś tryb 3-przebiegowego czyszczenia, czas niezbędny do zaszyfrowania partycji/dysku wydłuży się 4-ro krotnie. Podobnie, jeżeli wybierzesz tryb 35-przebiegowego czyszczenia, czas wydłuży 36-cio krotnie (może potrwać kilka tygodni).\n\nJednakże, proszę pamiętać, że czyszczenie NIE musi być wykonane po pełnym zaszyfrowaniu partycji/dysku. Jeżeli partycja/dysk jest w pełni zaszyfrowana, niezaszyfrowane dane są zapisane jako zaszyfrowane. Wiele danych zapisanych jest najpierw do pamięci, szyfrowanych "w locie" i zapisywanych zaszyfrowanych na dysku (tak aby nie obniżyć wydajności).\n\nCzy jesteś pewien, że chcesz użyć trybu czyszczenia/wymazywania?</string>

<string lang="pl" key="WIPE_MODE_NONE">Brak (najszybszy)</string>

<string lang="pl" key="WIPE_MODE_1_RAND">1-przebieg (dane losowe)</string>

<string lang="pl" key="WIPE_MODE_3_DOD_5220">3-przebiegowy (US DoD 5220.22-M)</string>

<string lang="pl" key="WIPE_MODE_7_DOD_5220">7-przebiegowy (US DoD 5220.22-M)</string>

<string lang="pl" key="WIPE_MODE_35_GUTMANN">35-przebiegowy ("Gutmann")</string>

<string lang="pl" key="SYS_MULTI_BOOT_MODE_TITLE">Liczba systemów operacyjnych</string>

<string lang="pl" key="MULTI_BOOT_FOR_ADVANCED_ONLY">OSTRZEŻENIE: Niedoświadczeni użytkownicy nie powinni nigdy próbować szyfrować systemu Windows w konfiguracji z wieloma uruchamianymi systemami.\n\nCzy kontynuować?</string>

<string lang="pl" key="HIDDEN_OS_MULTI_BOOT">Podczas tworzenia/używania ukrytego systemu operacyjnego, VeraCrypt obsługuje konfigurację uruchamiania wielu systemów tylko gdy zostaną spełnione następujące warunki:\n\n- Obecnie działający system operacyjny musi być zainstalowany na napędzie rozruchowym, który nie może zawieraćżadnych innych systemów operacyjnych.\n\n- Systemy operacyjne zainstalowane na innych dyskach nie mogą używać żadnego programu startowego znajdującego się na dysku, na którym zainstalowany jest obecnie działający system operacyjny.\n\nCzy powyższe wymagania są spełnione?</string>

<string lang="pl" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt nie obsługuje takiej konfiguracji uruchamiania wielu systemów gdy jest tworzony/używany ukryty system operacyjny.</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Dysk startowy</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Czy aktualnie uruchomiony system jest uruchamiany z dysku, na którym jest zainstalowany?\n\nWyjaśnienie: Czasami system Windows nie jest instalowany na tym samym dysku, co program startowy Windows (na partycji startowej). W takim przypadku wybierz 'Nie'.</string>

<string lang="pl" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">Program VeraCrypt obecnie nie obsługuje szyfrowania systemu operacyjnego, który nie jest uruchamiany z dysku, na którym jest zainstalowany.</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Liczba dysków systemowych</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Ile dysków zawiera system operacyjny?\n\nNa przykład, jeśli używanych jest wiele systemów operacyjnych (np. Windows, Mac OS X, Linux, itp. zainstalowany na pierwszym dysku i dodatkowy system zainstalowany na drugim dysku), wybierz opcję '2 lub więcej'.</string>

<string lang="pl" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">Program VeraCrypt obecnie nie obsługuje szyfrowania całego dysku, który zawiera wiele systemów operacyjnych.\n\nMożliwe rozwiązania:\n\n- Można na poprzednim panelu wybrać opcję zaszyfrowania jednego systemu na jednej partycji systemowej (w przeciwieństwie do szyfrowania całego dysku).\n\n- Można zaszyfrować cały dysk, jeśli inne systemy operacyjne zostaną przeniesione na inne dyski, pozostawiając ten dysk tylko dla jednego systemu operacyjnego. </string>

<string lang="pl" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Wiele systemów na jednym dysku</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Czy inne systemy operacyjne zostały zainstalowane na dysku, na którym jest zainstalowany aktualnie uruchomiony system operacyjny?\n\nNa przykład, jeśli aktualnie uruchomiony system operacyjny jest zainstalowany na dysku 0 (zawierającym kilka partycji), którego jedna z partycji zawiera Windows, a inna zawiera dodatkowy system operacyjny (np. Windows, Mac OS X, Linux, itp.), wybierz opcję 'Tak'.</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Program startowy z innego systemu</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">W MBR jest wpis pochodzący od boot loadera nie Windowsowego?\n\nNotka: Na przykład, jeżeli pierwsza ścieżka dysku zawiera GRUB, LILO, XOSL, lub inny nie-Windowsowy boot manager (lub boot loader), wybierz 'Tak'.</string>

<string lang="pl" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Wiele systemów</string>

<string lang="pl" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">Program VeraCrypt obecnie nie obsługuje konfiguracji wielosystemowej, w której w głównym rekordzie startowym (MBR) jest zainstalowany program startowy z systemu innego niż Windows.\n\nMożliwe rozwiązania:\n\n- Jeśli używasz menedżera uruchamiania do uruchamiania systemów Windows i Linux, przenieś menedżera uruchamiania (np. GRUB lub LILO) z MBR do partycji. Następnie uruchom ponownie kreator i zaszyfruj partycję/dysk systemowy. Program startowy VeraCrypt stanie się podstawowym menedżerem uruchamiania i będzie pozwalał na uruchamianie oryginalnego menedżera uruchamiania (np. GRUB lub LILO) jako drugiego menedżera uruchamiania (przez naciśnięcie klawisza Esc na ekranie programu startowego VeraCrypt), co umożliwi uruchamianie systemu Linux.</string>

<string lang="pl" key="WINDOWS_BOOT_LOADER_HINTS">Jeżeli obecnie uruchomiony system operacyjny jest zainstalowany na boot partycji, wówczas po zaszyfrowaniu jej, będziesz musiał wprowadzić poprawne hasło za każdym razem kiedy będziesz uruchamiał system (nawet ten niezaszyfrowany).\n\nNatomiast, jeżeli obecnie uruchomiony system operacyjny nie jest zainstalowany na boot partycji (lub jeżeli boot loader Windows nie jest używany przez inny system), wówczas, po zaszyfrowaniu systemu nie będziesz musiał wprowadzać hasła do uruchomienia innych systemów (również tych niezaszyfrowanych) -- będziesz musiał wcisnąć tylko klawisz Esc aby uruchomić niezaszyfrowany system (jeżeli jest wiele niezaszyfrowanych systemów będziesz musiał wybrać, który system chcesz uruchomić).\n\nNotka: Typowo, Windows jest zainstalowany na boot partycji.</string>

<string lang="pl" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Szyfrowanie Obszeru Chronionego Hosta</string>

<string lang="pl" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Na końcu wielu dysków są ukryte miejsca gdzie nie ma dostępu system operacyjny (są to zwykle Host Protected Areas). Jednakże niektóre programy potrafią czytać i pisać dane z/do tych sektorów.\n\nUWAGA: Niektórzy producenci sprzętu używają tych miejsc do przechowywania narzędzi np. do RAID, odtwarzania systemu, konfiguracji systemu, diagnostyki lub innych narzędzi. Jeżeli te narzędzia lub dane muszą być dostępne przed bootowaniem, obszar ten NIE powinien być zaszyfrowany (wybierz 'Nie' powyżej).\n\nCzy chcesz aby VeraCrypt wykrył i zaszyfrował te ukryte obszary na końcu dysku?</string>

<string lang="pl" key="SYSENC_TYPE_PAGE_TITLE">Typ Systemu Szyfrowania</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="pt-br" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ATENÇÃO: Se você já criou um Disco de Emergência VeraCrypt no passado, ele não pode ser reutilizado para esta partição/unidade de sistema, porque ele foi criado para uma chave mestra diferente! Cada vez que criptografar uma partição/unidade de sistema você deve criar um novo Disco de Emergência VeraCrypt para ela, mesmo se usar a mesma senha.</string>

<string lang="pt-br" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Erro: Não foi possível salvar as configurações de criptografia de sistema.</string>

<string lang="pt-br" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Não foi possível iniciar o pré-teste da criptografia de sistema.</string>

<string lang="pt-br" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Não é possível iniciar o processo de criação do sistema operacional oculto.</string>

<string lang="pt-br" key="WIPE_MODE_TITLE">Modo de Limpar</string>

<string lang="pt-br" key="INPLACE_ENC_WIPE_MODE_INFO">Em alguns tipos de mídias de armazenamento, quando os dados são sobrescritos com outros dados, pode ser possível recuperar os dados sobrescritos usando técnicas como microscopia de força magnética. Isto também se aplica aos dados que são sobrescritos pela sua forma criptografada (o que acontece quando VeraCrypt inicialmente criptografa uma partição ou unidade não criptografada). De acordo com alguns estudos e publicações governamentais, a recuperação de dados sobrescritos pode ser evitada (ou tornada muito difícil) sobrescrevendo os dados com outros dados pseudo-aleatórios e alguns não-aleatórios um determinado número de vezes. Portanto, se você acredita que um adversário possa ser capaz de usar tais técnicas para recuperar os dados que você pretende criptografar, você pode querer selecionar um dos modos de limpeza (dados existentes NÃO serão perdidos). Note que a limpeza NÃO será realizada depois da partição/unidade ser criptografada. Quando a partição/unidade está totalmente criptografada, nenhum dado não-criptografado é gravado nela. Quaisquer dados que estiverem sendo gravados nela são primeiro criptografados na memória e só então são gravados gravados no disco.</string>

<string lang="pt-br" key="WIPE_MODE_INFO">Em alguns tipos de mídias de armazenamento, quando os dados são sobrescritos com outros dados (por exemplo, quando eles são apagados), pode ser possível recuperar os dados sobrescritos usando técnicas como microscopia de força magnética. De acordo com alguns estudos e publicações governamentais, a recuperação de dados sobrescritos pode ser evitada (ou tornada muito difícil) sobrescrevendo os dados com outros dados pseudo-aleatórios e alguns não-aleatórios um determinado número de vezes. Portanto, se você acredita que um adversário possa ser capaz de usar tais técnicas para recuperar os dados que devem ser apagados, você pode querer selecionar um dos modos de limpeza de múltiplas passagens.\n\nNota: Quanto mais passagens de limpeza você usar, mais tempo levará para apagar os dados.</string>

<string lang="pt-br" key="DEVICE_WIPE_PAGE_TITLE">Limpando</string>

<string lang="pt-br" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNota: Você pode interromper o processo de limpeza, desligar o computador, iniciar o sistema oculto novamente e então retomar o processo (o assistente será iniciado automaticamente). No entanto, se você interrompê-lo, todo o processo de limpeza terá que começar desde o início.</string>

<string lang="pt-br" key="DEVICE_WIPE_PAGE_INFO">\n\nNota: Se você interromper o processo de limpeza e, em seguida, tentar retomá-lo, todo o processo terá que começar desde o início.</string>

<string lang="pt-br" key="CONFIRM_WIPE_ABORT">Você deseja abortar o processo de limpeza?</string>

<string lang="pt-br" key="CONFIRM_WIPE_START">Atenção: Todo o conteúdo da partição/dispositivo selecionada(o) será apagado e perdido.</string>

<string lang="pt-br" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Todo o conteúdo da partição onde o sistema original reside será apagado.\n\nNota: Todo o conteúdo da partição que está para ser apagada foi copiado para esta partição de sistema oculto.</string>

<string lang="pt-br" key="WIPE_MODE_WARN">ATENÇÃO: Note que quando você escolhe por exemplo o modo de limpeza de 3 ciclos, o tempo necessário para criptografar a partição/unidade será até 4 vezes maior. Do mesmo modo, se você escolher o modo de limpeza de 35 ciclos, vai ser até 36 vezes mais longo (o que poderia até levar várias semanas).\n\nNo entanto, observe que a limpeza NÃO será realizada após a partição/unidade ser totalmente criptografada. Quando a partição/unidade está totalmente criptografada, nenhum dado não-criptografado é gravado nela. Quaisquer dados que estão sendo gravados nela são primeiro criptografados na memória e só então são gravados no disco (por isso o desempenho NÃO será afetado).\n\nTem certeza que deseja usar o modo de limpeza?</string>

<string lang="pt-br" key="WIPE_MODE_NONE">Nenhum (mais rápido)</string>

<string lang="pt-br" key="WIPE_MODE_1_RAND">1 ciclo (dados aleatórios)</string>

<string lang="pt-br" key="WIPE_MODE_3_DOD_5220">3 ciclos (US DoD 5220.22-M)</string>

<string lang="pt-br" key="WIPE_MODE_7_DOD_5220">7 ciclos (US DoD 5220.22-M)</string>

<string lang="pt-br" key="WIPE_MODE_35_GUTMANN">35 ciclos ('Gutmann')</string>

<string lang="pt-br" key="SYS_MULTI_BOOT_MODE_TITLE">Número de Sistemas Operacionais</string>

<string lang="pt-br" key="MULTI_BOOT_FOR_ADVANCED_ONLY">AVISO: usuários inexperientes nunca devem tentar criptografar o Windows em configurações de boot múltiplo.\n\nDeseja continuar?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Disco de Inicialização</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Este sistema operacional está instalado no disco de inicialização?\n\nLembre: às vezes, o Windows não está instalado no mesmo disco que seu boot loader (partição de inicialização). Se este for o caso clique em 'Não'.</string>

<string lang="pt-br" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">O VeraCrypt não criptografa sistema operacional que não inicia do mesmo disco em que está instalado.</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Número de Discos de Sistema</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Quantos discos contêm sistema operacional?\n\nLembre: Se, por exemplo, você tem algum sistema operacional (como Windows, Mac OS X, Linux, etc.) instalado em seu disco primário e algum outro sistema operacional instalado em seu disco secundário, selecione '2 ou mais'.</string>

<string lang="pt-br" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">Esta versão do VeraCrypt não suporta criptografar um disco que contém vários sistemas operacionais.\n\nSoluções Possíveis:\n\n- Você ainda pode criptografar um dos sistemas se você voltar e escolher criptografar apenas uma partição de sistema (em vez de escolher criptografar o disco de sistema inteiro).\n\n- Você também pode criptografar o disco inteiro se, primeiro, você mover os outros sistemas operacionais para outros discos, deixando apenas um sistema no disco que você deseja criptografar.</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Vários Sistemas em Um único Disco</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Existe algum outro sistema operacional instalado no mesmo disco em que este sistema operacional?\n\nLembre: Se este sistema operacional estiver instalado, por exemplo, no disco #0, que contém várias partições, e uma delas contém o Windows e outra contém outro sistema operacional (como Windows, Mac OS X, Linux, etc.), selecione 'Sim'.</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Boot Loader Não-Windows</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">É um gerenciador de boot não-Windows instalado no Master Boot Record (MBR)?\n\nNota: Por exemplo, se a primeira faixa da unidade de boot contém o GRUB, LILO, XOSL, ou algum outro gerenciador de boot não-Windows (ou gestor de inicialização), selecione 'Sim'.</string>

<string lang="pt-br" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Boot Múltiplo</string>

<string lang="pt-br" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">Esta versão do VeraCrypt não suporta configurações de boots múltiplos com boot loader não-Windows instalado na MBR.\n\nSoluções Possíveis:\n\n- Se você usa um gerenciador de boot para iniciar o Windows e o Linux, mova o gerenciador de boot (geralmente GRUB) da MBR para uma partição. Depois, inicie este assistente novamente e criptografeo dispositivo/partição de sistema. Lembre que o VeraCrypt Boot Loader se tornará o seu gerenciador de inicialização principal e permitirá que você execute seu gerenciador original (como GRUB) como gerenciador secundário (pressionando Esc na tela do VeraCrypt Boot Loader) e, assim, você poderá iniciar o Linux.</string>

<string lang="pt-br" key="WINDOWS_BOOT_LOADER_HINTS">Se o sistema operacional atualmente em execução estiver instalado na partição de boot, então, depois que você criptografá-la, você terá que digitar a senha correta mesmo que você queira iniciar qualquer outro sistema Windows não-criptografado (uma vez que irão compartilhar um único gerenciador de boot criptografado do Windows).\n\nEm contrapartida, se o sistema operacional em execução atualmente não estiver instalado na partição de boot (ou se o gerenciador de boot do Windows não é utilizado por nenhum outro sistema), em seguida, depois de criptografar este sistema, você não precisa digitar a senha correta para iniciar o(s) outro(s) sistema(s) não-criptografado(s) – você só precisa pressionar a tecla Esc para iniciar o sistema não-criptografada (se existirem vários sistemas não criptografados, você também precisará escolher qual sistema iniciar no menu do Gerenciador de Boot do VeraCrypt).\n\nNota: Normalmente, o mais antigo sistema do Windows instalado está na partição de inicialização.</string>

<string lang="pt-br" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Criptografia da Área Protegida do Host</string>

<string lang="pt-br" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">No final de muitas unidades, existe uma área que é normalmente ocultada do sistema operacional (tais áreas são geralmente referidas como Áreas Protegidas do Host). No entanto, alguns programas podem ler e gravar dados de/para essas áreas.\n\nATENÇÃO: Alguns fabricantes de computadores podem utilizar essas áreas para armazenar dados e ferramentas para RAID, recuperação do sistema, configuração do sistema, diagnóstico, ou para outros fins. Se essas ferramentas ou dados devem estar acessíveis antes de inicializar, a área oculta NÃO deve ser criptografada (escolher 'Não' acima).\n\nVocê quer que o VeraCrypt detecte e criptografe uma área oculta assim (se houver), no final da unidade de sistema?</string>

<string lang="pt-br" key="SYSENC_TYPE_PAGE_TITLE">Tipo da Criptografia do Sistema</string>

<string lang="ru" key="LAUNCH_WIN_ISOBURN">Запустить средство записи образов дисков Windows</string>

<string lang="ru" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ВНИМАНИЕ: Если ранее вы уже создавали диск восстановления VeraCrypt, вы не сможете им воспользоваться снова для этого системного раздела/диска, так как он был создан для другого мастер-ключа! При каждом шифровании системного раздела/диска нужно создавать новый диск восстановления VeraCrypt, даже если вы используете тот же самый пароль.</string>

<string lang="ru" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Ошибка! Невозможно сохранить установки системного шифрования.</string>

<string lang="ru" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Невозможно инициировать пре-тест системного шифрования.</string>

<string lang="ru" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Невозможно начать процесс создания скрытой операционной системы.</string>

<string lang="ru" key="WIPE_MODE_TITLE">Режим очистки</string>

<string lang="ru" key="INPLACE_ENC_WIPE_MODE_INFO">На ряде перезаписываемых носителей перезаписанные данные можно восстановить с помощью спецтехник (магнитно-силовая микроскопия). Это относится и к данным, перезаписанным в зашифрованном виде (когда VeraCrypt шифрует незашифрованный системный раздел/диск). Восстановление перезаписанных данных можно предотвратить (или сильно осложнить) перезаписью псевдослучайными или определёнными неслучайными данными некоторое число раз. Если ваши неприятели могут применить подобные методы для восстановления данных, которые вы собираетесь зашифровать, выберите один из режимов очистки (имеющиеся данные НЕ будут уничтожены). После шифрования раздела/диска очистка НЕ выполняется. Когда раздел/диск полностью зашифрован, никакие незашифрованные данные на него не записываются. Любые данные сначала шифруются на лету в памяти, и лишь затем сохраняются (зашифрованными) на диске.</string>

<string lang="ru" key="WIPE_MODE_INFO">На ряде перезаписываемых носителей перезаписанные данные (например, когда данные удалены) можно восстановить с помощью спецтехник (магнитно-силовая микроскопия). Восстановление перезаписанных данных можно предотвратить (или сильно осложнить) перезаписью псевдослучайными или определёнными неслучайными данными некоторое число раз. Если ваши неприятели могут применить подобные техники для восстановления данных, которые должны быть удалены, выберите один из многопроходных режимов очистки.\n\nПримечание: чем больше проходов, тем дольше длится стирание данных.</string>

<string lang="ru" key="DEVICE_WIPE_PAGE_TITLE">Очистка</string>

<string lang="ru" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nПримечание: вы можете прервать процесс очистки, выключить компьютер, снова запустить скрытую систему и затем продолжить очистку (этот мастер запустится автоматически). Однако в случае прерывания весь процесс очистки придётся начать сначала.</string>

<string lang="ru" key="DEVICE_WIPE_PAGE_INFO">\n\nПримечание: если прервать очистку, а затем попытаться возобновить этот процесс, то его придётся выполнить с самого начала.</string>

<string lang="ru" key="CONFIRM_WIPE_ABORT">Вы хотите отменить очистку (затирание данных)?</string>

<string lang="ru" key="CONFIRM_WIPE_START">Внимание! Содержимое всего выбранного раздела/устройства будет уничтожено.</string>

<string lang="ru" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Всё содержимое раздела, где находится исходная система, будет уничтожено.\n\nПримечание: всё содержимое раздела, подлежащего стиранию, было скопировано в этот скрытый системный раздел.</string>

<string lang="ru" key="WIPE_MODE_WARN">ВНИМАНИЕ: Если выбрать, например, 3-проходный режим очистки, время шифрования диска/раздела увеличится в 4 раза. Аналогично, при выборе 35-проходного режима время увеличится в 36 раз (и может даже составить несколько недель).\n\nУчтите, однако, что очистка НЕ выполняется после того, как раздел/диск зашифрован. Когда раздел/диск полностью зашифрован, никаких незашифрованных данных на него не записывается. Любые записываемые на него данные сначала шифруются на лету в памяти, и только затем сохраняются (в зашифрованном виде) на диске (т.е. на производительности это НЕ отражается).\n\nВы действительно хотите использовать режим очистки?</string>

<string lang="ru" key="WIPE_MODE_NONE">Нет (самый быстрый)</string>

<string lang="ru" key="WIPE_MODE_1_RAND">1 проход (случайные данные)</string>

<string lang="ru" key="WIPE_MODE_3_DOD_5220">3 прохода (US DoD 5220.22-M)</string>

<string lang="ru" key="WIPE_MODE_7_DOD_5220">7 проходов (US DoD 5220.22-M)</string>

<string lang="ru" key="WIPE_MODE_35_GUTMANN">35 проходов ("Gutmann")</string>

<string lang="ru" key="SYS_MULTI_BOOT_MODE_TITLE">Число операционных систем</string>

<string lang="ru" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ВНИМАНИЕ: Неопытным пользователям не следует пытаться шифровать Windows в мультизагрузочных конфигурациях.\n\nПродолжить?</string>

<string lang="ru" key="HIDDEN_OS_MULTI_BOOT">При создании/использовании скрытой операционной системы VeraCrypt поддерживает мультизагрузочные конфигурации только при соблюдении следующих условий:\n\n- работающая сейчас операционная система должна быть установлена на загрузочном диске, на котором не может быть других операционных систем;\n\n- операционные системы, установленные на других дисках, не должны использовать загрузчик, находящийся на диске, на котором установлена текущая операционная система.\n\nЭти условия соблюдены?</string>

<string lang="ru" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt не поддерживает эту мультизагрузочную конфигурацию при создании/использовании скрытой операционной системы.</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Загрузочный диск</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Работающая в данный момент операционная система установлена на загрузочном диске?\n\nПримечание: иногда Windows бывает установлена не на том диске, с которого она грузится (где находится загрузочный раздел). Если это ваш случай, то выберите 'Нет'.</string>

<string lang="ru" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">В данный момент VeraCrypt не поддерживает шифрование операционной системы, которая загружается не с того же диска, на котором она установлена.</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Число системных дисков</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Сколько дисков содержит операционная система?\n\nПримечание: например, если одна операционная система (скажем, Windows, Mac OS X, Linux и т.д.) установлена у вас на первичном диске, а другая на вторичном, выберите '2 или более'.</string>

<string lang="ru" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">В данный момент VeraCrypt не поддерживает шифрование всего диска, который содержит несколько операционных систем.\n\nВозможные варианты:\n\n- Вы можете зашифровать одну из систем, если вернётесь назад и выберите шифрование только одного системного раздела (а не всего системного диска).\n\n- Вы сможете зашифровать весь диск, если переместите некоторые системы на другие диски, оставив только одну ОС на диске, который хотите зашифровать.</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Несколько систем на одном диске</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">На диске, где установлена текущая ОС, есть другие операционные системы?\n\nПримечание: например, если текущая ОС установлена на диске #0, содержащем несколько разделов, и если на одном из разделов находится Windows, а на другом - ещё одна ОС (скажем, Windows, Mac OS X, Linux и т.д.), то выберите 'Да'.</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Не-Windows загрузчик</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Установлен ли в главной загрузочной записи (MBR) не относящийся к Windows загрузчик (или загрузочный менеджер)?\n\nПримечание: например, если в первом цилиндре загрузочного диска содержится GRUB, LILO, XOSL или какой-то другой не относящийся к Windows загрузочный менеджер, выберите 'Да'.</string>

<string lang="ru" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Мультизагрузка</string>

<string lang="ru" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">В настоящее время VeraCrypt не поддерживает мультизагрузочные конфигурации, где в главной загрузочной записи (MBR) установлен не относящийся к Windows загрузчик.\n\nВозможные варианты:\n\n- Если вы используете загрузочный менеджер для загрузки Windows и Linux, перенесите его (обычно это GRUB) из MBR в раздел. Затем запустите снова этот мастер и зашифруйте системный раздел/диск. Обратите внимание, что загрузчик VeraCrypt станет основным загрузочным менеджером и позволит вам запускать исходный загрузочный менеджер (скажем, GRUB) как вторичный (нажатием Esc при выводе экрана загрузчика VeraCrypt) и, таким образом, запускать Linux.</string>

<string lang="ru" key="WINDOWS_BOOT_LOADER_HINTS">Если текущая ОС установлена на загрузочном разделе, то после его шифрования вам потребуется ввести правильный пароль, даже для запуска незашифрованных Windows-систем (так как они будут совместно использовать один и тот же зашифрованный загрузчик Windows).\n\nНапротив, если текущая ОС не установлена на загрузочном разделе (или загрузчик Windows не используется никакими иными системами), тогда после шифрования этой системы вам не надо вводить пароль для запуска других незашифрованных систем, достаточно будет просто нажать Esc (в случае нескольких незашифрованных систем также потребуется выбрать нужную в меню загрузчика VeraCrypt).\n\nПримечание: как правило, в загрузочном разделе бывает установлена наиболее ранняя версия Windows.</string>

<string lang="ru" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Шифрование защищённой области пользователя (HPA)</string>

<string lang="ru" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">В конце многих дисков имеется область, в обычных условиях скрытая от операционной системы (эту область обычно называют Host Protected Area - защищённая область пользователя). Однако некоторые программы способны читать и записывать данные в таких областях.\n\nВНИМАНИЕ: Производители компьютеров (в частности, ноутбуков) могут использовать области HPA для хранения в них утилит и данных для RAID, восстановления системы, её настройки, диагностики и прочих нужд. Если такие утилиты или данные должны быть доступны перед загрузкой системы, скрытую область НЕ следует шифровать (выберите 'Нет').\n\nХотите, чтобы VeraCrypt обнаружил и зашифровал скрытую область (если таковая имеется) в конце системного диска?</string>

<string lang="ru" key="SYSENC_TYPE_PAGE_TITLE">Тип шифрования системы</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="sl" key="SYS_MULTI_BOOT_MODE_TITLE">Število operacijskih sistemov</string>

<string lang="sl" key="MULTI_BOOT_FOR_ADVANCED_ONLY">OPOZORILO: Neizkušeni uporabniki naj ne bi nikoli poizkušali šifrirati Okna v nastavitvi poljubnega zagona.\n\nNadaljujem?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="sl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Zagonski pogon</string>

<string lang="sl" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Je trenutno zaganjajoči operacijski sistem naložen na zagonskem pogonu?\n\nOpomba: Včasih Okna niso naložena na istem pogonu kot zagonski program Oken (zagonski razdelek). Če so to tovrstne okoliščine (kot navedeno), potem izberite možnost 'Ne'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="sl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Število sistemskih pogonov</string>

<string lang="sl" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Koliko pogonov vsebuje operacijski sistem?\n\nOpomba: Na primer, če imate katerikoli operacijski sistem (npr., Okna Mac OS X, Linux, itn.) naložen na Vašem primarnem pogonu in če imate še kateri dodatni operacijski sistem naložen na Vašem sekundarnem pogonu, izberite možnost 'Dva ali več'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="sl" key="SYSENC_TYPE_PAGE_TITLE">Tip sistemskega šifriranja</string>

<string lang="sv" key="LAUNCH_WIN_ISOBURN">Kör programmet Bränn skivavbildning i Windows</string>

<string lang="sv" key="RESCUE_DISK_BURN_NO_CHECK_WARN">VARNING: En återställningsskiva som skapats vid ett tidigare tillfälle kan inte användas för denna systempartition eller -enhet, eftersom den skapades för en annan primär nyckel! Varje gång du krypterar en systempartition eller -enhet måste du även skapa en ny återställningsskiva för den, även om du använder samma lösenord.</string>

<string lang="sv" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Fel: Det går inte att spara systemkrypteringsinställningarna.</string>

<string lang="sv" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Det går inte att initiera det förberedande testet inför systemkrypteringen.</string>

<string lang="sv" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Det går inte att initiera processen för att skapa det dolda operativsystemet.</string>

<string lang="sv" key="WIPE_MODE_TITLE">Överskrivningsmetod</string>

<string lang="sv" key="INPLACE_ENC_WIPE_MODE_INFO">På vissa typer av lagringsmedier kan det, trots att data skrivits över av andra data, vara möjligt att återskapa överskrivna data med hjälp av tekniker som t.ex. magnetkraftsmikroskopi (MFM). Detta gäller även data som skrivits över av sina krypterade motsvarigheter (vilket sker när VeraCrypt krypterar en okrypterad partition eller enhet). Enligt vissa undersökningar kan ett återskapande av över- skrivna data hindras (eller avsevärt försvåras) genom att skriva över data med pseudoslumpmässiga och vissa icke slumpmässiga data ett visst antal gånger. Därför kan du, om du tror att någon obehörig har tillgång till sådana tekniker för att återskapa de data du tänker kryptera, välja en av överskrivningsmetoderna ovan. (Existerande data kommer INTE att gå förlorade.) Observera att någon över- skrivning INTE kommer att utföras efter det att partitionen eller enheten krypterats. När partitionen eller enheten är färdigkrypterad, kommer inga okrypterade data att skrivas till den. Data krypteras direkt i minnet innan de skrivs (krypterade) till disken.</string>

<string lang="sv" key="WIPE_MODE_INFO">På vissa typer av lagringsmedier kan det, trots att data skrivits över av andra data, vara möjligt att återskapa överskrivna data med hjälp av tekniker som t.ex. magnetkraftsmikroskopi (MFM). Enligt vissa undersökningar kan ett återskapande av överskrivna data hindras (eller avsevärt försvåras) genom att skriva över data med pseudoslumpmässiga och vissa icke slumpmässiga data ett visst antal gånger. Därför kan du, om du tror att någon obehörig har tillgång till sådana tekniker för att återskapa de data du tänker kryptera, välja en av flerstegsmetoderna för överskrivning ovan.\n\nObservera: Ju fler steg du använder, desto längre tid tar det att skriva över dina data.</string>

<string lang="sv" key="DEVICE_WIPE_PAGE_TITLE">Överskrivning</string>

<string lang="sv" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nObservera: Du kan avbryta överskrivningsprocessen, stänga av din dator, starta det dolda operativsystemet igen och sedan återuppta processen. (Denna guide kommer att startas automatiskt.) Hela överskrivningsprocessen kommer, om du avbryter den, emellertid att behöva börja om från början.</string>

<string lang="sv" key="DEVICE_WIPE_PAGE_INFO">\n\nObservera: Om du avbryter överskrivningsprocessen och sedan försöker återuppta den, kommer hela processen att behöva börja om från början.</string>

<string lang="sv" key="CONFIRM_WIPE_ABORT">Vill du avbryta överskrivningsprocessen?</string>

<string lang="sv" key="CONFIRM_WIPE_START">Varning: Hela innehållet på den valda partitionen eller enheten kommer att skrivas över och gå förlorat.</string>

<string lang="sv" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Hela innehållet på partitionen med det ursprungliga operativsystemet kommer att skrivas över.\n\nObservera: Hela innehållet på partitionen som kommer att skrivas över har kopierats till denna dolda systempartition.</string>

<string lang="sv" key="WIPE_MODE_WARN">VARNING: Observera att en överskrivningsmetod i t.ex. tre steg kan medföra att en kryptering av en enhet eller partition tar upp till fyra gånger så lång tid att genomföra. På samma sätt kan en överskrivningsmetod med 35 steg ta upp till 36 gånger så lång tid att genomföra (vilket i praktiken kan innebära flera veckor).\n\nObservera att någon överskrivning INTE kommer att utföras efter det att partitionen eller enheten krypterats. När partitionen eller enheten är färdigkrypterad, kommer inga okrypterade data att skrivas till den. Data krypteras direkt i minnet innan de skrivs (krypterade) till disken (och påverkar INTE prestandan).\n\nÄr du säker på att du vill använda överskrivning?</string>

<string lang="sv" key="WIPE_MODE_NONE">Ingen (snabbast)</string>

<string lang="sv" key="WIPE_MODE_1_RAND">Ett steg (slumpmässiga data)</string>

<string lang="sv" key="WIPE_MODE_3_DOD_5220">Tre steg (US DoD 5220.22-M)</string>

<string lang="sv" key="WIPE_MODE_7_DOD_5220">Sju steg (US DoD 5220.22-M)</string>

<string lang="sv" key="WIPE_MODE_35_GUTMANN">35 steg (”Gutmann”)</string>

<string lang="sv" key="SYS_MULTI_BOOT_MODE_TITLE">Antal operativsystem</string>

<string lang="sv" key="MULTI_BOOT_FOR_ADVANCED_ONLY">VARNING: Oerfarna användare bör aldrig försöka kryptera Windows i flervalsstartkonfigurationer.\n\nVill du fortsätta?</string>

<string lang="sv" key="HIDDEN_OS_MULTI_BOOT">Endast när följande villkor är uppfyllda stöder VeraCrypt flervalsstartkonfigurationer vid skapandet eller användandet av ett dolt operativsystem:\n\n- Det aktuella operativsystemet måste vara installerat på startenheten, som inte får innehålla några andra operativsystem.\n\n- Operativsystem installerade på övriga enheter får inte använda sig av någon startinläsare belägen på enheten där det aktuella operativsystemet är installerat.\n\nÄr ovanstående villkor uppfyllda?</string>

<string lang="sv" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt stöder inte denna flervalsstartkonfiguration vid skapandet eller användandet av ett dolt operativsystem.</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Startenhet</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Är det aktuella operativsystemet installerat på startenheten?\n\nObservera: Ibland är inte Windows installerat på samma enhet som Windows startinläsare (startpartitionen). Välj ”Nej” om så är fallet.</string>

<string lang="sv" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt stöder för närvarande inte kryptering av ett operativsystem som inte startar från den enhet det är installerat på.</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Antal systemenheter</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Hur många enheter innehåller ett operativsystem?\n\nObservera: Välj ”Två eller fler” om du exempelvis har ett operativsystem (som t.ex. Windows, Mac OS X eller Linux) installerat på din primära enhet och ytterligare ett operativsystem installerat på din sekundära enhet.</string>

<string lang="sv" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt stöder för närvarande inte kryptering av en hel enhet som innehåller flera operativsystem.\n\nMöjliga lösningar:\n\n· Du kan fortfarande kryptera ett av systemen om du går tillbaka och väljer att endast kryptera en systempartition (i motsats till att kryptera hela systemenheten).\n\n· Alternativt kan du kryptera hela enheten om du först flyttar alla system utom ett till andra enheter.</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Flera operativsystem på en enskild enhet</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Finns det några andra operativsystem installerade samma enhet som det aktuella operativsystemet?\n\nObservera: Klicka på ”Ja” om det aktuella operativsystemet t.ex. är installerat på enhet 0, som innehåller flera partitioner, och om en av partitionerna innehåller Windows och en annan partition ett ytterligare operativsystem (t.ex. Windows, Mac OS X, Linux etc.).</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Annan startinläsare än Windows</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Är en annan startinläsare (eller -hanterare) än Windows installerad i enhetens Master Boot Record (MBR)?\n\nObservera: Klicka på ”Ja” om exempelvis det första spåret på startenheten innehåller GRUB, LILO, XOSL eller någon annan starthanterare (eller -laddare) än Windows.</string>

<string lang="sv" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Flervalsstart</string>

<string lang="sv" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt stöder för närvarande inte flervalsstartkonfigurationer där en annan startinläsare än Windows är installerad i enhetens Master Boot Record.\n\nMöjliga lösningar:\n\n· Om du använder en starthanterare för att starta Windows och Linux (normalt sett GRUB), flytta den från enhetens Master Boot Record till en partition. Kör sedan denna guide igen och kryptera systempartitionen eller -enheten. Observera att VeraCrypts startinläsare kommer att bli din primära starthanterare. Din ursprungliga starthanterare (t.ex. GRUB) kommer i stället att bli din sekundära starthanterare. Den startas genom att du trycker på Esc i VeraCrypts startinläsare, varefter det blir möjligt för dig att starta Linux.</string>

<string lang="sv" key="WINDOWS_BOOT_LOADER_HINTS">Om det aktuella operativsystemet är installerat på startpartitionen måste du, efter att du krypterat det, ange rätt lösenord även om du vill starta ett annat okrypterat Windows-system (eftersom de kommer att dela en gemensam krypterad startinläsare eller -hanterare).\n\nOm det aktuella operativsystemet inte är installerat på startpartitionen – eller om Windows startinläsare eller -hanterare inte används av något annat operativsystem – behöver du inte ange rätt lösenord för att starta övriga okrypterade operativsystem; det är tillräckligt att trycka på Esc för att starta ett okrypterat operativsystem. (Om det finns flera okrypterade operativsystem installerade, kommer du även att vara tvungen att välja vilket operativsystem som ska startas i VeraCrypts starthanterares meny.)\n\nObservera: Normalt sett är den Windows-installation som gjordes först installerad på startpartitionen.</string>

<string lang="sv" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Kryptering av Host Protected Area</string>

<string lang="sv" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">I slutet av många enheter finns ett område som normalt sett är dolt för operativsystemet (ofta kallat Host Protected Area). Vissa program kan dock läsa och skriva data till och från sådana områden.\n\nVARNING: Vissa datorleverantörer kan använda sådana områden för att lagra verktyg och data för RAID, systemåterställning, systeminställningar, diagnostik eller liknande. Om sådana verktyg eller data måste vara tillgängliga före uppstart, ska det dolda området INTE krypteras (välj ”Nej” ovan).\n\nVill du att VeraCrypt ska identifiera och i så fall kryptera ett sådant område i slutet av systemenheten?</string>

<string lang="sv" key="SYSENC_TYPE_PAGE_TITLE">Typ av systemkryptering</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="uk" key="LAUNCH_WIN_ISOBURN">Запустити засіб запису образів дисків Windows</string>

<string lang="uk" key="RESCUE_DISK_BURN_NO_CHECK_WARN">УВАГА: Якщо раніше ви вже створювали диск відновлення VeraCrypt, ви не зможете ним скористатися знову для цього системного розділу/диска, так як він був створений для іншого майстер-ключа! При кожному шифруванні системного розділу/диска потрібно створювати новий диск відновлення VeraCrypt, навіть якщо ви використовуєте той самий пароль.</string>

<string lang="uk" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Помилка! Неможливо зберегти установки системного шифрування.</string>

<string lang="uk" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Неможливо ініціювати попередній тест системного шифрування.</string>

<string lang="uk" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Неможливо почати процес створення прихованої операційної системи.</string>

<string lang="uk" key="WIPE_MODE_TITLE">Режим очищення</string>

<string lang="uk" key="INPLACE_ENC_WIPE_MODE_INFO">На низці перезаписувати носіїв перезаписані дані можна відновити за допомогою спецтехніки (мікроскопія магнітної сили). Це відноситься і до даних, перезаписані в зашифрованому вигляді (коли VeraCrypt шифрує незашіфрованний системний розділ/диск). Відновлення перезаписані даних можна запобігти (або сильно ускладнити) перезаписом псевдослучайнимі або певними невипадкова даними деяке число разів. Якщо ваші супротивника можуть застосувати подібні методи для відновлення даних, які ви збираєтеся зашифрувати, виберіть один з режимів очищення (наявні дані НЕ будуть знищені). Після шифрування розділу/диска білінгові НЕ виконується. Коли розділ/диск повністю зашифровано, ніякі незашіфрованние дані на нього не записуються. Будь-які дані спочатку шифруються на льоту в пам'яті, і лише потім зберігаються (зашифрованими) на диску.</string>

<string lang="uk" key="WIPE_MODE_INFO">На низці перезаписуючих носіїв перезаписані дані (наприклад, коли дані видалені) можна відновити за допомогою спецтехніки (мікроскопія магнітної сили). Відновленню перезаписуючих даних можна запобігти (або сильно ускладнити) перезаписом псевдовипадковим або певними невипадкова даними деяку кількість разів. Якщо ваші супротивника можуть застосувати подібну техніку для відновлення даних, які повинні бути видалені, виберіть один з багатопрохідних режимів очистки.\n\nПрімечаніе: чим більше проходів, тим довше триває стирання даних.</string>

<string lang="uk" key="DEVICE_WIPE_PAGE_TITLE">Очищення</string>

<string lang="uk" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nримітка: ви можете перервати процес очищення, вимкнути комп'ютер, знову запустити приховану систему і потім продовжити очищення (цей майстер запускається автоматично). Однак у випадку переривання весь процес очищення доведеться почати спочатку.</string>

<string lang="uk" key="DEVICE_WIPE_PAGE_INFO">\n\nПримітка: якщо перервати очистку, а потім спробувати відновити цей процес, то його доведеться виконати з самого початку.</string>

<string lang="uk" key="CONFIRM_WIPE_ABORT">Ви хочете скасувати очищення (затирання даних)?</string>

<string lang="uk" key="CONFIRM_WIPE_START">Увага! Вміст всього обраного розділу/пристрою буде знищено.</string>

<string lang="uk" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Весь вміст розділу, де знаходиться вихідна система, буде знищено.\n\nПримітка: весь вміст розділу, що підлягає стиранню, було скопійовано в цей прихований системний розділ.</string>

<string lang="uk" key="WIPE_MODE_WARN">УВАГА: Якщо вибрати, наприклад, 3-прохідний режим очищення, час шифрування диска/розділу збільшиться в 4 рази. Аналогічно, при виборі 35-прохідного режиму часом збільшиться в 36 разів (і може навіть скласти кілька тижнів).\n\nМайте на увазі,що очищення НЕ виконується після того, як розділ/диск зашифровано. Коли розділ/диск повністю зашифровано, ніяких незашифрованних даних на нього не записується. Будь-які записуючі на нього дані спочатку шифруються на льоту в пам'яті, і тільки потім зберігаються (у зашифрованому вигляді) на диску (тобто на продуктивності це НЕ відображається).\n\nВи дійсно хочете використовувати режим очищення?</string>

<string lang="uk" key="WIPE_MODE_NONE">Ні (найшвидший)</string>

<string lang="uk" key="WIPE_MODE_1_RAND">1 прохід (случайные данные)</string>

<string lang="uk" key="WIPE_MODE_3_DOD_5220">3 проходи (US DoD 5220.22-M)</string>

<string lang="uk" key="WIPE_MODE_7_DOD_5220">7 проходів (US DoD 5220.22-M)</string>

<string lang="uk" key="WIPE_MODE_35_GUTMANN">35 проходів ("Gutmann")</string>

<string lang="uk" key="SYS_MULTI_BOOT_MODE_TITLE">Число операційних систем</string>

<string lang="uk" key="MULTI_BOOT_FOR_ADVANCED_ONLY">УВАГА: недосвідченим користувачам не слід намагатися шифрувати Windows в мультизагрузочних конфігураціях.\n\nПродовжити?</string>

<string lang="uk" key="HIDDEN_OS_MULTI_BOOT">При створенні/використанні прихованої операційної системи VeraCrypt підтримує Мультизавантажуючі конфігурації тільки при дотриманні наступних умов: \n\n-працююча зараз операційна система повинна бути встановлена ​​на завантажувальному диску, на якому не може бути інших операційних систем;\n\n-операційні системи, встановлені на інших дисках, не повинні використовувати завантажувач, що знаходиться на диску, на якому встановлена ​​поточна операційна система.\n\nЦі умови дотримані?</string>

<string lang="uk" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt не підтримує цю Мультизавантажуючу конфігурацію при створенні/використанні прихованої операційної системи.</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Завантажувальний диск</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Операційна система, що працює в даний момент встановлена на завантажувальному диску?\n\nПримітка: іноді буває Windows встановлений не на тому диску, з якого він грузится (де знаходиться завантажувальний розділ). Якщо це ваш випадок, то виберіть 'Ні'.</string>

<string lang="uk" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">В даний момент VeraCrypt не підтримує шифрування операційної системи, яка завантажується не з того ж диску, на якому вона встановлена.</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Число системних дисків</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Скільки дисків містить операційна система?\n\nПримітка: наприклад, якщо у вас одна операційна система (наприклад, Windows, Mac OS X, Linux і т.д.) встановлена на первинному диску, а інша - на вторинному, виберіть '2 або більше'.</string>

<string lang="uk" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">В даний момент VeraCrypt не підтримує шифрування всього диску, який містить декілька операційних систем.\n\nМожливі варіанти:\n\n-Ви можете зашифрувати одну із систем, якщо повернетеся назад і виберіть шифрування тільки одного системного розділу (а не всього системного диску).\n\n-Ви зможете зашифрувати весь диск, якщо перемістете деякі системи на інші диски, залишивши тільки одну ОС на диску який хочете зашифрувати.</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Кілька систем на одному диску</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">На диску, на якому встановлена поточна ОС, є інші операційні системи?\n\nПримітка: наприклад, якщо поточна ОС встановлена на диску #0, що містить кілька розділів, і якщо на одному з розділів знаходиться Windows, а на іншому - ще одна ОС (скажімо, Windows, Mac OS X, Linux і т.д.), то виберіть 'Так'.</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Не-Windows завантажувач</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Чи встановлений у головній завантажувального запису (MBR) не належить до Windows завантажувач (або завантажувальний менеджер)\n\nПримітка: наприклад, якщо в першому циліндрі завантажувального диска міститься GRUB, LILO, XOSL або якийсь інший не належить до Windows завантажувальний менеджер , виберіть 'Так'.</string>

<string lang="uk" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Мультизавантаження</string>

<string lang="uk" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">В даний час VeraCrypt не підтримує мультизавантажуючі конфігурації, де у головній завантажувального запису (MBR) встановлений не належить до Windows завантажувач.\n\nМожливі варіанти:\n\n-Якщо ви використовуєте завантажувальний менеджер для завантаження Windows і Linux, перенесіть його (звичайно це GRUB) з MBR у розділ. Потім запустіть знову цей майстер і зашифруйте системний розділ/диск. Зверніть увагу, що завантажувач VeraCrypt стане основним завантажувальним менеджером і дозволить вам запускати вихідний завантажувальний менеджер (скажімо, GRUB) як вторинний (натисканням Esc при виведенні екрану завантажувача VeraCrypt) і, таким чином, запускати Linux.</string>

<string lang="uk" key="WINDOWS_BOOT_LOADER_HINTS">Якщо поточна ОС встановлена на завантажувальному розділі, то після його шифрування вам буде потрібно ввести правильний пароль, навіть для запуску незашіфрованних Windows-систем (так як вони будуть спільно використовувати один і той же зашифрований завантажувач Windows).\n\nНавпаки, якщо поточна ОС не встановлена на завантажувальному розділі (або завантажувач Windows не використовується ніякими іншими системами), тоді після шифрування цієї системи вам не треба вводити пароль для запуску інших незашіфрованних систем - достатньо буде просто натиснути Esc (в разі кількох незашіфрованних систем також потрібно вибрати потрібну в меню завантажувача VeraCrypt).\n\nПримітка: як правило, в завантажувальному розділі буває встановлена найбільш рання версія Windows.</string>

<string lang="uk" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Шифрування захищеної області користувача (HPA)</string>

<string lang="uk" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">В кінці багатьох дисків є область, у звичайних умовах прихована від операційної системи (цю область зазвичай називають Host Protected Area - захищена область користувача). Однак деякі програми здатні читати і записувати дані в таких областях.\n\nУВАГА: Виробники комп'ютерів (зокрема, ноутбуків) можуть використовувати області HPA для зберігання в них утиліт і даних для RAID, відновлення системи, її налаштування, діагностики та інших потреб. Якщо такі утиліти або дані повинні бути доступні перед завантаженням системи, приховану область НЕ слід шифрувати (виберіть 'Ні').\n\nБажаєте, щоб VeraCrypt виявив і зашифрували приховану область (якщо така є) в кінці системного диска?</string>

<string lang="uk" key="SYSENC_TYPE_PAGE_TITLE">Тип шифрування системи</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="uz" key="RESCUE_DISK_BURN_NO_CHECK_WARN">ВНИМАНИЕ: Если ранее вы уже создавали диск восстановления VeraCrypt, вы не сможете им воспользоваться снова для этого системного раздела/диска, так как он был создан для другого мастер-ключа! При каждом шифровании системного раздела/диска нужно создавать новый диск восстановления VeraCrypt, даже если вы используете тот же самый пароль.</string>

<string lang="uz" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Ошибка! Невозможно сохранить установки системного шифрования.</string>

<string lang="uz" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Невозможно инициировать пре-тест системного шифрования.</string>

<string lang="uz" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Невозможно начать процесс создания скрытой операционной системы.</string>

<string lang="uz" key="WIPE_MODE_TITLE">Режим очистки</string>

<string lang="uz" key="INPLACE_ENC_WIPE_MODE_INFO">На ряде перезаписываемых носителей перезаписанные данные можно восстановить с помощью спецтехник (микроскопия магнитной силы). Это относится и к данным, перезаписанным в зашифрованном виде (когда VeraCrypt шифрует незашифрованный системный раздел/диск). Восстановление перезаписанных данных можно предотвратить (или сильно осложнить) перезаписью псевдослучайными или определёнными неслучайными данными некоторое число раз. Если ваши неприятели могут применить подобные методы для восстановления данных, которые вы собираетесь зашифровать, выберите один из режимов очистки (имеющиеся данные НЕ будут уничтожены). После шифрования раздела/диска очистка НЕ выполняется. Когда раздел/диск полностью зашифрован, никакие незашифрованные данные на него не записываются. Любые данные сначала шифруются на лету в памяти, и лишь затем сохраняются (зашифрованными) на диске.</string>

<string lang="uz" key="WIPE_MODE_INFO">На ряде перезаписываемых носителей перезаписанные данные (например, когда данные удалены) можно восстановить с помощью спецтехник (микроскопия магнитной силы). Восстановление перезаписанных данных можно предотвратить (или сильно осложнить) перезаписью псевдослучайными или определёнными неслучайными данными некоторое число раз. Если ваши неприятели могут применить подобные техники для восстановления данных, которые должны быть удалены, выберите один из многопроходных режимов очистки.\n\nПримечание: чем больше проходов, тем дольше длится стирание данных.</string>

<string lang="uz" key="DEVICE_WIPE_PAGE_TITLE">Очистка</string>

<string lang="uz" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nПримечание: вы можете прервать процесс очистки, выключить компьютер, снова запустить скрытую систему и затем продолжить очистку (этот мастер запустится автоматически). Однако в случае прерывания весь процесс очистки придётся начать сначала.</string>

<string lang="uz" key="DEVICE_WIPE_PAGE_INFO">\n\nПримечание: если прервать очистку, а затем попытаться возобновить этот процесс, то его придётся выполнить с самого начала.</string>

<string lang="uz" key="CONFIRM_WIPE_ABORT">Вы хотите отменить очистку (затирание данных)?</string>

<string lang="uz" key="CONFIRM_WIPE_START">Внимание! Содержимое всего выбранного раздела/устройства будет уничтожено.</string>

<string lang="uz" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Всё содержимое раздела, где находится исходная система, будет уничтожено.\n\nПримечание: всё содержимое раздела, подлежащего стиранию, было скопировано в этот скрытый системный раздел.</string>

<string lang="uz" key="WIPE_MODE_WARN">ВНИМАНИЕ: Если выбрать, например, 3-проходный режим очистки, время шифрования диска/раздела увеличится в 4 раза. Аналогично, при выборе 35-проходного режима время увеличится в 36 раз (и может даже составить несколько недель).\n\nУчтите, однако, что очистка НЕ выполняется после того, как раздел/диск зашифрован. Когда раздел/диск полностью зашифрован, никаких незашифрованных данных на него не записывается. Любые записываемые на него данные сначала шифруются на лету в памяти, и только затем сохраняются (в зашифрованном виде) на диске (т.е. на производительности это НЕ отражается).\n\nВы действительно хотите использовать режим очистки?</string>

<string lang="uz" key="WIPE_MODE_NONE">Нет (самый быстрый)</string>

<string lang="uz" key="WIPE_MODE_1_RAND">1 проход (случайные данные)</string>

<string lang="uz" key="WIPE_MODE_3_DOD_5220">3 прохода (US DoD 5220.22-M)</string>

<string lang="uz" key="WIPE_MODE_7_DOD_5220">7 проходов (US DoD 5220.22-M)</string>

<string lang="uz" key="WIPE_MODE_35_GUTMANN">35 проходов ("Gutmann")</string>

<string lang="uz" key="SYS_MULTI_BOOT_MODE_TITLE">Число операционных систем</string>

<string lang="uz" key="MULTI_BOOT_FOR_ADVANCED_ONLY">ВНИМАНИЕ: Неопытным пользователям не следует пытаться шифровать Windows в мультизагрузочных конфигурациях.\n\nПродолжить?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Загрузочный диск</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Работающая в данный момент операционная система установлена на загрузочном диске?\n\nПримечание: иногда Windows бывает установлена не на том диске, с которого она грузится (где находится загрузочный раздел). Если это ваш случай, то выберите 'Нет'.</string>

<string lang="uz" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">В данный момент VeraCrypt не поддерживает шифрование операционной системы, которая загружается не с того же диска, на котором она установлена.</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Число системных дисков</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Сколько дисков содержит операционная система?\n\nПримечание: например, если у вас одна операционная система (скажем, Windows, Mac OS X, Linux и т.д.) установлена на первичном диске, а другая -- на вторичном, выберите '2 или более'.</string>

<string lang="uz" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">В данный момент VeraCrypt не поддерживает шифрование всего диска, который содержит несколько операционных систем.\n\nВозможные варианты:\n\n- Вы можете зашифровать одну из систем, если вернётесь назад и выберите шифрование только одного системного раздела (а не всего системного диска).\n\n- Вы сможете зашифровать весь диск, если переместите некоторые системы на другие диски, оставив только одну ОС на диске, который хотите зашифровать.</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Несколько систем на одном диске</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">На диске, где установлена текущая ОС, есть другие операционные системы?\n\nПримечание: например, если текущая ОС установлена на диске #0, содержащем несколько разделов, и если на одном из разделов находится Windows, а на другом -- ещё одна ОС (скажем, Windows, Mac OS X, Linux и т.д.), то выберите 'Да'.</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Не-Windows загрузчик</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Установлен ли в главной загрузочной записи (MBR) не относящийся к Windows загрузчик (или загрузочный менеджер)?\n\nПримечание: например, если в первом цилиндре загрузочного диска содержится GRUB, LILO, XOSL или какой-то другой не относящийся к Windows загрузочный менеджер, выберите 'Да'.</string>

<string lang="uz" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Мультизагрузка</string>

<string lang="uz" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">В настоящее время VeraCrypt не поддерживает мультизагрузочные конфигурации, где в главной загрузочной записи (MBR) установлен не относящийся к Windows загрузчик.\n\nВозможные варианты:\n\n- Если вы используете загрузочный менеджер для загрузки Windows и Linux, перенесите его (обычно это GRUB) из MBR в раздел. Затем запустите снова этот мастер и зашифруйте системный раздел/диск. Обратите внимание, что загрузчик VeraCrypt станет основным загрузочным менеджером и позволит вам запускать исходный загрузочный менеджер (скажем, GRUB) как вторичный (нажатием Esc при выводе экрана загрузчика VeraCrypt) и, таким образом, запускать Linux.</string>

<string lang="uz" key="WINDOWS_BOOT_LOADER_HINTS">Если текущая ОС установлена на загрузочном разделе, то после его шифрования вам потребуется ввести правильный пароль, даже для запуска незашифрованных Windows-систем (так как они будут совместно использовать один и тот же зашифрованный загрузчик Windows).\n\nНапротив, если текущая ОС не установлена на загрузочном разделе (или загрузчик Windows не используется никакими иными системами), тогда после шифрования этой системы вам не надо вводить пароль для запуска других незашифрованных систем -- достаточно будет просто нажать Esc (в случае нескольких незашифрованных систем также потребуется выбрать нужную в меню загрузчика VeraCrypt).\n\nПримечание: как правило, в загрузочном разделе бывает установлена наиболее ранняя версия Windows.</string>

<string lang="uz" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Шифрование защищённой области пользователя (HPA)</string>

<string lang="uz" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">В конце многих дисков имеется область, в обычных условиях скрытая от операционной системы (эту область обычно называют Host Protected Area -- защищённая область пользователя). Однако некоторые программы способны читать и записывать данные в таких областях.\n\nВНИМАНИЕ: Производители компьютеров (в частности, ноутбуков) могут использовать области HPA для хранения в них утилит и данных для RAID, восстановления системы, её настройки, диагностики и прочих нужд. Если такие утилиты или данные должны быть доступны перед загрузкой системы, скрытую область НЕ следует шифровать (выберите 'Нет').\n\nХотите, чтобы VeraCrypt обнаружил и зашифровал скрытую область (если таковая имеется) в конце системного диска?</string>

<string lang="uz" key="SYSENC_TYPE_PAGE_TITLE">Системанинг шифрлаш тури</string>

<string lang="vi" key="LAUNCH_WIN_ISOBURN">Khởi chạy Microsoft Windows Disc Image Burner</string>

<string lang="vi" key="RESCUE_DISK_BURN_NO_CHECK_WARN">CẢNH BÁO: Nếu bạn đã cấu tạo một Đĩa Cứu hộ VeraCrypt trong quá khứ, nó không thể đuợc dùng lại cho phân vùng/ổ đĩa hệ thống này vì nó được cấu tạo cho một khóa chính khác! Mỗi khi bạn mã hóa một phân vùng/ổ đĩa hệ thống, bạn phải cấu tạo một Đĩa Cứu hộ VeraCrypt mới cho nó ngay cả nếu bạn sử dụng cùng một mật mã.</string>

<string lang="vi" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Lỗi: Không thể lưu trữ những thiết lập mã hóa hệ thống.</string>

<string lang="vi" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Không thể khởi đầu tiền thử nghiệm của mã hóa hệ thống.</string>

<string lang="vi" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Không thể khởi đầu quá trình cấu tạo hệ điều hành ẩn.</string>

<string lang="vi" key="WIPE_MODE_TITLE">Phương thức Tẩy</string>

<string lang="vi" key="INPLACE_ENC_WIPE_MODE_INFO">Trong một vài loại môi trường chứa, khi các dữ liệu bị viết chòng lên với những dữ liệu khác, các dữ liệu bị viết chòng lên có thể được khôi phục lại bằng cách dùng những kỹ thuật như microscopy lực từ trường. This also applies to data that are overwritten with their mã hóa form (which happens when VeraCrypt initially encrypts một unmã hóa phân vùng or ổ đĩa). Dựa theo một vài nghiên cứu và công bố của chính phủ, sự khôi phục của các dữ liệu bị viết chòng lên có thể được cản trở (hoặc làm cho rất khó khăn) bằng cách viết chòng các dữ liệu với dữ liệu pseudorandom và non-random một số lần nhất định. Vì vậy, nếu bạn tin là một đối phương có thể dùng những kỹ thuật như thế để khôi phục lại các dữ liệu bạn intend mã hóa, bạn có thể chọn một trong những phương thức tẩy (existing data will NOT be lost). Lưu ý là sự tẩy will NOT be performed after the phân vùng/ổ đĩa is mã hóa. When the phân vùng/ổ đĩa is fully mã hóa, no unmã hóa data is written to it. Any data being written to it is first mã hóa ngay khi cần in memory and only then is the (mã hóa) data written to the disk.</string>

<string lang="vi" key="WIPE_MODE_INFO">Trong một vài loại môi trường chứa, khi các dữ liệu bị viết chòng lên với những dữ liệu khác (ví dụ như khi dữ liệu bị xóa mất), các dữ liệu bị viết chòng lên có thể được khôi phục lại bằng cách dùng những kỹ thuật như microscopy lực từ trường. Dựa theo một vài nghiên cứu và công bố của chính phủ, sự khôi phục của các dữ liệu bị viết chòng lên có thể được cản trở (hoặc làm cho rất khó khăn) bằng cách viết chòng các dữ liệu với dữ liệu pseudorandom và non-random một số lần nhất định. Vì vậy, nếu bạn tin là một đối phương có thể dùng những kỹ thuật như thế để khôi phục lại các dữ liệu đáng được xóa mất, bạn có thể chọn một trong những phương thức tẩy nhiều-pass.\n\nLưu ý: Bạn càng sử dụng nhiều pass tẩy chừng nào thì sẽ nó sẽ mất lâu hơn để xóa mất các dữ liệu.</string>

<string lang="vi" key="DEVICE_WIPE_PAGE_TITLE">Đang tẩy</string>

<string lang="vi" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nLưu ý: Bạn có thể gián đoạn quá trình của việc tẩy, tắt máy điện toán của bạn, bắt đầu hệ ẩn lại và sau đó tiếp tục lại quá trình (trợ lý này sẽ được tự động khởi chạy). Tuy nhiên, nếu bạn gián đoạn nó, toàn bộ quá trình của việc tẩy sẽ phải bắt đầu lại từ đầu.</string>

<string lang="vi" key="DEVICE_WIPE_PAGE_INFO">\n\nLưu ý: Nếu bạn gián đoạn quá trình tẩy và thử tiếp tục lại thì cả quá trình sẽ phải bắt đầu lại từ đầu.</string>

<string lang="vi" key="CONFIRM_WIPE_ABORT">Bạn có muốn hủy bỏ quá trình tẩy không?</string>

<string lang="vi" key="CONFIRM_WIPE_START">Cảnh báo: Toàn bộ nội dung của phân vùng/thiết bị được chọn sẽ bị xóa và mất đi.</string>

<string lang="vi" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">Toàn bộ nội dung của phân vùng nơi mà hệ thống gốc nằm sẽ bị xóa đi.\n\nLưu ý: Toàn bộ nội dung của phân vùng mà bị xóa đi đã được sao chép vào phân vùng của hệ ẩn này.</string>

<string lang="vi" key="WIPE_MODE_WARN">CẢNH BÁO: Lưu ý là khi bạn chọn ví dụ như phương thức tẩy 3-bước, thời gian cần thiết để mã hóa phân vùng/ổ đĩa sẽ lâu hơn gấp 4 lần. Tương tự, nếu bạn chọn phương thức tẩy 35-bước, nó sẽ lâu hơn gấp 36 lần (nó có thể mất một vài tuần).\n\nTuy nhiên, xin lưu ý là việc tẩy sẽ KHÔNG được thực hiện sau khi phân vùng/ổ đĩa được hoàn toàn mã hóa. Khi phân vùng/ổ đĩa được hoàn toàn mã hóa, dữ liệu không được mã hóa sẽ không được viết vào nó. Bâ;t cứ dữ liệu nào được viết vào nó trước tiên được mã hóa ngay khi cần trong bộ nhớ và chỉ sau đó dữ liệu (mã hóa) mới được viết vào đĩa (vì thế hiệu suất sẽ KHÔNG bị ảnh hưởng).\n\nBạn có chắc là bạn muốn sử dụng phương thức tẩy không?</string>

<string lang="vi" key="WIPE_MODE_NONE">Không có (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="vi" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="vi" key="SYS_MULTI_BOOT_MODE_TITLE">Số Hệ Điều hành</string>

<string lang="vi" key="MULTI_BOOT_FOR_ADVANCED_ONLY">CẢNH BÁO: Người dùng không kinh nghiệm không bao giờ nên thử mã hóa Windows theo cấu hình khởi động đa hệ.\n\nTiếp tục không?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Ổ đĩa Khởi động</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Hệ điều hành đang chạy hiện thời có được cài đặt trong ổ đĩa khởi động không?\n\nLưu ý: Đôi khi Windows không được cài đặt trong cùng ổ đĩa chung với bộ nạp khởi động của Windows bộ tải khởi nạp (phân vùng khởi động). Trong trường hợp như thế, chọn 'Không'.</string>

<string lang="vi" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt hiện tại không hỗ trợ việc mã hóa một hệ điều hành mà không khởi động từ ổ đĩa nơi nó được cài đặt.</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Số Ổ đĩa Hệ thống</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">Có bao nhiêu ổ đĩa có chứa một hệ điều hành?\n\nLưu ý: Ví dụ nếu như bạn có bất cứ hệ điều hành nào(như Windows, Mac OS X, Linux, v.v.) được cài đặt trong ổ đĩa chính của bạn và một hệ điều hành khác được cài đặt trong ổ đĩa phụ của bạn thì chọn '2 hay hơn'.</string>

<string lang="vi" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt hiện tại không hỗ trợ việc mã hóa cả một ổ đĩa có chứa nhiều hệ điều hành.\n\nNhững Giải pháp Có thể:\n\n- Bạn vẫn có thể mã hóa một trong các hệ thống nếu bạn đi ngược lại và chọn chỉ mã hóa một hệ thống phân vùng đơn độc (thay vì chọn mã hóa toàn bộ ổ đĩa hệ thống).\n\n- Ngoài ra, bạn sẽ có thể mã hóa toàn bộ ổ đĩa nếu bạn dời một vài hệ thống qua những ổ đĩa khác và chỉ để một hệ thống trong ổ đĩa mà bạn muốn mã hóa.</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Đa Hệ trong Ổ đĩa Đơn</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Có hệ điều hành nào khác được cài đặt trong ổ đĩa hệ điều hành đang chạy được cài đặt không?\n\nLưu ý: Ví dụ như nếu hệ điều hành đang chạy được cài đặt trong ổ đĩa #0, nơi mà có chứa một số phân vùng, và nếu một trong các phân vùng có chứa Windows và một phân vùng khác có chứa bất cứ hệ điều hành khác (ví dụ như Windows, Mac OS X, Linux, v.v.), chọn 'Có'.</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Bộ tải Khởi nạp Không phải của Windows</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Có một bộ tải khởi nạp nào không phải của Windows (hoặc hàm quản lý khởi động) được cài đặt trong hồ sơ khởi động chính (MBR) không?\n\nLưu ý: Ví dụ như nếu phần đường đầu tiên của ổ đĩa khởi động có chứa GRUB, LILO, XOSL, hoặc vài hàm quản lý khởi động không phải của Windows (hoặc bộ tải khởi nạp), chọn 'Có'.</string>

<string lang="vi" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Khởi động Đa hệ</string>

<string lang="vi" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt hiện tại không hỗ trợ cấu hình đa-khởi động nơi một bộ tải khởi nạp không phải của Windows được cài đặt trong Hồ sơ Khởi động Chính.\n\nNhững Giải pháp Có thể:\n\n- Nếu bạn sử dụng một hàm quản lý khởi động để khởi động Windows và Linux, dời hàm quản lý khởi động (thông thường là GRUB) từ Hồ sơ Khởi động Chính đến một phân vùng. Sau đó bắt đầu trợ lý này lại và mã hóa phân vùng/ổ đĩa hệ thống. Lưu ý là Bộ tải Khởi nạp của VeraCrypt sẽ trở thành hàm quản lý khởi động chủ yếu của bạn và nó sẽ cho phép bạn khởi chạy hàm quản lý khởi động gốc (ví dụ như GRUB) như là hàm quản lý khởi động phụ của bạn (bằng cách bấm Esc trong màn ảnh Bộ tải Khởi nạp của VeraCrypt) và vì vậy bạn sẽ có thể khởi động Linux.</string>

<string lang="vi" key="WINDOWS_BOOT_LOADER_HINTS">Nếu hệ điều hành hiện đang chạy được cài đặt trong phân vùng khởi động thì sau khi bạn mã hóa nó, bạn sẽ cần phải nhập mật mã đúng vào ngay cả nếu bạn muốn bắt đầu bất cứ hệ thống Windows chưa mã hóa nào khác (vì chúng sẽ xài chung một bộ tải khởi nạp/hàm quản lý đơn độc của Windows được mã hóa).\n\nNgược lại, nếu hệ điều hành đang chạy không được cài đặt trong phân vùng khởi động (hoặc nếu bộ tải khởi nạp/hàm quản lý của Windows không được dùng bởi bất cứ hệ thống nào khác) thì sau khi bạn mã hóa hệ thống này, bạn sẽ không cần phải nhập mật mã đúng vào để khởi động (các) hệ thống chưa được mã hóa khác -- bạn sẽ chỉ cần bấm phím Esc để bắt đầu giải mã hệ thống (nếu có nhiều hệ thống chưa được mã hóa thì bạn sẽ cũng cần phải chọn hệ thống nào để bắt đầu trong trình đơn của Hàm quản lý Khởi động của VeraCrypt).\n\nLưu ý: Thông thường thì hệ thống Windows được cài đặt trước nhất thì được cài đặt trong phân vùng khởi động.</string>

<string lang="vi" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Mã hóa Vùng được Chủ Bảo vệ</string>

<string lang="vi" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">Ở phía cuối của nhiều ổ đĩa, có một vùng thường được ẩn khỏi hệ điều hành (những vùng như thế thường được nhắc đến như là những Vùng được Chủ Bảo vệ). Tuy nhiên, một vài chương trình có thể đọc và viết dữ liệu từ/vào những vùng như thế.\n\nCẢNH BÁO: Một vài nhà sản xuất máy điện toán có thể dùng những vùng như thế để lưu trữ các công cụ và dữ liệu cho RAID, hệ thống phục hồi, hệ thống thiết lập, chẩn đoán, hay những mục đích khác. Nếu such các công cụ và dữ liệu như thế phải được truy cập trước khi khởi động, vùng ẩn KHÔNG nên được mã hóa (chọn 'No' bên trên).\n\nBạn có muốn VeraCrypt truy kiếm và mã hóa một vùng ẩn như thế (nếu có) ở phía cuối của ổ đĩa hệ thống không?</string>

<string lang="vi" key="SYSENC_TYPE_PAGE_TITLE">Loại Giải Mã Hệ Thống</string>

<string lang="zh-cn" key="LAUNCH_WIN_ISOBURN">启动微软 Windows 磁盘映像刻录器</string>

<string lang="zh-cn" key="RESCUE_DISK_BURN_NO_CHECK_WARN">警告：如果您已经创建了 VeraCrypt 应急盘，它将不能再用于系统分区/驱动器，这是因为您每次加密系统分区/驱动器时都会使用不同的主密钥，尽管您使用的是同样的密码，您也必须创建一个新的 VeraCrypt 应急盘。</string>

<string lang="zh-cn" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">错误：不能保存系统加密设置。</string>

<string lang="zh-cn" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">不能初始化系统加密预测试。</string>

<string lang="zh-cn" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">不能初始化创建隐形操作系统的过程。</string>

<string lang="zh-cn" key="WIPE_MODE_TITLE">擦除模式</string>

<string lang="zh-cn" key="INPLACE_ENC_WIPE_MODE_INFO">在某些存储介质上，当数据被其他数据覆盖后，也仍有可能通过磁力显微技术恢复出来被覆盖的数据。这也包括一些被加密方式覆盖的数据（这在 VeraCrypt 加密那些原来没有加密的系统分区或系统驱动器时可能会发生）。根据一些研究机构和政府机构发布的文献，通过使用伪随机或非随机数据覆盖一定次数可以阻止数据恢复或使数据恢复变的异常困难。因此，如果您确认攻击者可能会使用类似磁力显微技术恢复您的加密数据，您可以选择下拉列表中几种擦除算法中的一种（已经存在的数据不会丢失）。需要说明的是在分区/驱动器加密后不需要再执行擦除操作。当分区/驱动器被完全加密后，不会再有非加密数据向其写入。写入加密卷中的任何数据都是在内存中实时加密，然后这些已加密数据才会被写入到磁盘。</string>

<string lang="zh-cn" key="WIPE_MODE_INFO">在某些存储介质上，当数据被其他数据覆盖后，也仍有可能通过磁力显微技术恢复出来被覆盖的数据。根据一些研究机构和政府机构发布的文献，通过使用伪随机或非随机数据覆盖一定次数可以阻止数据恢复或使数据恢复变的异常困难。因此，如果您确认攻击者可能会使用类似磁力显微技术恢复您的加密数据，您可以选择下拉列表中几种擦除算法中的一种（已经存在的数据不会丢失）。\n\n说明：擦除次数越多，花费的时间越长。</string>

<string lang="zh-cn" key="DEVICE_WIPE_PAGE_TITLE">正在擦除</string>

<string lang="zh-cn" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n说明：您可以中断擦除的过程，关闭您的计算机，重新启动隐形系统并在此后继续这个过程（该向导将会被自动运行）。然而，如果您中断此过程，整个擦除将会从头开始执行。</string>

<string lang="zh-cn" key="DEVICE_WIPE_PAGE_INFO">\n\n说明：如果您中断了擦除的过程并想在以后继续擦除，整个的过程将不得不从头开始。</string>

<string lang="zh-cn" key="CONFIRM_WIPE_ABORT">您确认要放弃擦除过程吗？</string>

<string lang="zh-cn" key="CONFIRM_WIPE_START">警告：所选 分区/设备 的全部内容将会被擦除并因此而丢失。</string>

<string lang="zh-cn" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">原始操作系统所在的分区将会被擦除。\n\n说明：该分区的全部内容已经复制到了隐形系统分区。</string>

<string lang="zh-cn" key="WIPE_MODE_WARN">警告：请注意如果使用 3-次擦除模式，加密驱动器/分区需要时间将会增加为原来的4倍。同样，如果选择35-次擦除模式，所消耗的时间会为原来的36倍（如果分区容量很大，很可能花费几周的时间）。\n\n然而，请注意在分区/驱动器完全加密后【无须】再对其执行擦除操作。在分区/驱动器被完全加密后，将不会再有非加密的数据向该分区/驱动器写入。所有写入的数据首先都会在内存中即时加密，之后才会向分区/驱动器写入加密的数据（因此并不会影响性能）。\n\n您确认要使用这种擦除模式吗？</string>

<string lang="zh-cn" key="WIPE_MODE_NONE">无（最快）</string>

<string lang="zh-cn" key="WIPE_MODE_1_RAND">1-次擦除（随机数据）</string>

<string lang="zh-cn" key="WIPE_MODE_3_DOD_5220">3-次擦除（US DoD 5220.22-M）</string>

<string lang="zh-cn" key="WIPE_MODE_7_DOD_5220">7-次擦除（US DoD 5220.22-M）</string>

<string lang="zh-cn" key="WIPE_MODE_35_GUTMANN">35-次擦除（"Gutmann"）</string>

<string lang="zh-cn" key="SYS_MULTI_BOOT_MODE_TITLE">操作系统数目</string>

<string lang="zh-cn" key="MULTI_BOOT_FOR_ADVANCED_ONLY">警告：入门用户请勿尝试加密多重启动方式的 Windows 。\n\n希望继续吗？</string>

<string lang="zh-cn" key="HIDDEN_OS_MULTI_BOOT">当创建或使用隐形操作系统时，只有满足如下条件时，VeraCrypt 才支持多重启动配置：\n\n- 当前运行操作系统必须安装在启动驱动器，并且该驱动器中不能包含其它操作系统。\n\n- 安装在其它驱动器的操作系统不能使用任何位于当前运行操作系统所在驱动器中的启动管理器。\n\n确认满足以上条件吗？</string>

<string lang="zh-cn" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">在创建或使用隐形操作系统时，VeraCrypt 不支持此多重启动配置。</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">引导驱动器</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">当前运行的操作系统安装到了引导驱动器上了吗？\n\n说明：有时 Windows 可能并未安装到 Windows 启动管理器（活动分区）分区上。如果属于这种情况，请选择〖否〗。</string>

<string lang="zh-cn" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt 当前不支持加密安装到非活动分区上的系统。</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">系统驱动器数目</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">有多少个驱动器含有操作系统？\n\n说明：例如，您在主驱动器上安装了任意系统（例如. Windows，Mac OS X，Linux，等等），在第二个驱动器上安装了其它的操作系统，这时就选择“2 个或多个”。</string>

<string lang="zh-cn" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt 目前不支持对包含多个操作系统的整个硬盘驱动器的加密。\n\n可能的解决方法：\n\n- 您可以后退并选择只加密单系统分区加密其中的一个系统（与选择加密整个系统驱动器相反）。\n\n- 或者，您也可以把要加密的驱动器中的其它系统迁移到其它的驱动器，而只在其中保留一个系统。</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">单驱动器中包含多个系统</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">在当前运行的系统所安装的驱动器中，是否包含其它任何操作系统？\n\n说明：例如当前运行的操作系统安装在驱动器 #0，该驱动器包含几个分区，其中一个分区安装了 Windows 系统，而另一个分区安装了其它任何操作系统（例如. Windows，Mac OS X，Linux，等等.），请选择〖是〗。</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">非 Windows 启动管理器</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">是否安装了一个非 Windows 启动管理器（或启动管理器）到 MBR 中了吗?\n\n说明：例如，可启动的驱动器的第一个柱面包含 GRUB、LILO、XOSL，或其它非 Windows 启动管理器（或启动管理器），则选择“是”。</string>

<string lang="zh-cn" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">多重启动</string>

<string lang="zh-cn" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt 目前不支持在 MBR 中安装的非 Windows 多重启动管理器。\n\n可能的解决办法：\n\n- 如果您使用了一个启动管理器来启动 Windows 或 Linux，把启动管理器（典型的，例如 GRUB）从 MBR 中迁移到分区上。之后再次启动向导和加密系统分区/设备。说明：VeraCrypt 启动管理器将会成为主启动管理器，并且会允许您把原来的启动管理器（例如 GRUB）作为第二启动管理器（通过在 VeraCrypt 启动管理器屏幕按下 ESC 按键），因此您仍然可以启动 Linux。</string>

<string lang="zh-cn" key="WINDOWS_BOOT_LOADER_HINTS">如果当前运行的系统安装在活动分区上，随后，在您加密了该分区后，尽管您想要启动其它未加密的系统，您仍然要输入正确的密码（因为它们都会共享同一个加密的 Windows 启动管理器）。\n\n相反的，如果当前运行的系统并没有安装到 Windows 的启动分区（或者如果其它系统并未使用 Windows 启动管理器），随后，在您加密了该分区后，您在启动其它未加密的系统时不需要输入正确的密码 -- 您只需按 ESC 按键来启动未加密的系统（如果存在多个未加密的系统，您也同样需要在 VeraCrypt 的启动管理器中选择要启动的系统）。\n\n说明：通常情况下，最早安装的那个系统一般都会安装到启动分区。</string>

<string lang="zh-cn" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">加密主机保护区域（Host Protected Area）</string>

<string lang="zh-cn" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">在很多硬盘的尾部，存在一个相对于操作系统隐藏的区域（这些区域通常被称作主机保护区域）。然而，某些程序可以从这些区域中读写数据。\n\n警告：某些计算机供应商可能使用这些区域存储用于 RAID、系统恢复、系统设置、诊断的工具和数据，或用于其它目地。如果此类工具和数据必须在启动前访问，那么这些隐藏区域不应当被加密（在上面选择〖否〗）。\n\n您希望 VeraCrypt 检测和解密系统驱动器尾部这些隐藏区域吗？</string>

<string lang="zh-cn" key="SYSENC_TYPE_PAGE_TITLE">系统加密类型</string>

<string lang="zh-hk" key="LAUNCH_WIN_ISOBURN">啟動微軟 Windows 磁片映射刻錄器</string>

<string lang="zh-hk" key="RESCUE_DISK_BURN_NO_CHECK_WARN">警告：如果您已經創建了 VeraCrypt 應急盤，它將不能再用於系統分區/驅動器，這是因為您每次加密系統分區/驅動器時都會使用不同的主密鑰，儘管您使用的是同樣的密碼，您也必須創建一個新的 VeraCrypt 應急盤。</string>

<string lang="zh-hk" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">錯誤：不能保存系統加密設置。</string>

<string lang="zh-hk" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">不能初始化系統加密預測試。</string>

<string lang="zh-hk" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">不能初始化創建隱形作業系統的過程。</string>

<string lang="zh-hk" key="WIPE_MODE_TITLE">擦除模式</string>

<string lang="zh-hk" key="INPLACE_ENC_WIPE_MODE_INFO">在某些存儲介質上，當資料被其他資料覆蓋後，也仍有可能通過磁力顯微技術恢復出來被覆蓋的資料。這也包括一些被加密方式覆蓋的資料（這在 VeraCrypt 加密那些原來沒有加密的系統分區或系統驅動器時可能會發生）。根據一些研究機構和政府機構發佈的文獻，通過使用偽隨機或非亂數據覆蓋一定次數可以阻止資料恢復或使資料恢復變的異常困難。因此，如果您確認攻擊者可能會使用類似磁力顯微技術恢復您的加密資料，您可以選擇下拉清單中幾種擦除演算法中的一種（已經存在的資料不會丟失）。需要說明的是在分區/驅動器加密後不需要再執行擦除操作。當分區/驅動器被完全加密後，不會再有非加密資料向其寫入。寫入加密卷中的任何資料都是在記憶體中即時加密，然後這些已加密資料才會被寫入到磁片。</string>

<string lang="zh-hk" key="WIPE_MODE_INFO">在某些存儲介質上，當資料被其他資料覆蓋後，也仍有可能通過磁力顯微技術恢復出來被覆蓋的資料。根據一些研究機構和政府機構發佈的文獻，通過使用偽隨機或非亂數據覆蓋一定次數可以阻止資料恢復或使資料恢復變的異常困難。因此，如果您確認攻擊者可能會使用類似磁力顯微技術恢復您的加密資料，您可以選擇下拉清單中幾種擦除演算法中的一種（已經存在的資料不會丟失）。\n\n說明：擦除次數越多，花費的時間越長。</string>

<string lang="zh-hk" key="DEVICE_WIPE_PAGE_TITLE">正在擦除</string>

<string lang="zh-hk" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\n說明：您可以中斷擦除的過程，關閉您的電腦，重新啟動隱形系統並在此後繼續這個過程（該嚮導將會被自動運行）。然而，如果您中斷此過程，整個擦除將會從頭開始執行。</string>

<string lang="zh-hk" key="DEVICE_WIPE_PAGE_INFO">\n\n說明：如果您中斷了擦除的過程並想在以後繼續擦除，整個的過程將不得不從頭開始。</string>

<string lang="zh-hk" key="CONFIRM_WIPE_ABORT">您確認要放棄擦除過程嗎？</string>

<string lang="zh-hk" key="CONFIRM_WIPE_START">警告：選定 分區/設備 的全部內容將會被擦除並因此而丟失。</string>

<string lang="zh-hk" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">原始作業系統所在的分區將會被擦除。\n\n說明：該分區的全部內容已經複製到了隱形系統分區。</string>

<string lang="zh-hk" key="WIPE_MODE_WARN">警告：請注意如果使用 3-次擦除模式，加密驅動器/分區需要時間將會增加為原來的4倍。同樣，如果你選擇了35-次擦除模式，所消耗的時間會為原來的36倍（如果分區容量很大，很可能花費幾周的時間）。\n\n然而，請注意在分區/驅動器完全加密後〖無須〗再對其執行擦除操作。在分區/驅動器被完全加密後，將不會再有非加密的資料向該分區/驅動器寫入。所有寫入的資料首先都會在記憶體中即時加密，之後才會向分區/驅動器寫入加密的資料（因此並不會影響性能）。\n\n您確認要使用這種擦除模式嗎？</string>

<string lang="zh-hk" key="WIPE_MODE_NONE">無（最快）</string>

<string lang="zh-hk" key="WIPE_MODE_1_RAND">1-次擦除（亂數據）</string>

<string lang="zh-hk" key="WIPE_MODE_3_DOD_5220">3-次擦除（US DoD 5220.22-M）</string>

<string lang="zh-hk" key="WIPE_MODE_7_DOD_5220">7-次擦除（US DoD 5220.22-M）</string>

<string lang="zh-hk" key="WIPE_MODE_35_GUTMANN">35-次擦除（"Gutmann"）</string>

<string lang="zh-hk" key="SYS_MULTI_BOOT_MODE_TITLE">作業系統數目</string>

<string lang="zh-hk" key="MULTI_BOOT_FOR_ADVANCED_ONLY">警告：入門用戶應當從來不嘗試加密多重啟動方式的 Windows 。\n\n希望繼續嗎？</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">引導驅動器</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">當前運行的作業系統安裝到了引導驅動器上了嗎？\n\n說明：有時 Windows 可能並未安裝到 Windows 啟動管理器（活動分區）分區上。如果屬於這種情況，請選擇 '否'。</string>

<string lang="zh-hk" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt 當前不支持加密安裝到非活動分區上的系統。</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">系統驅動器數目</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">有多少個驅動器含有作業系統？\n\n說明：例如，您在主驅動器上安裝了任意系統（例如. Windows，Mac OS X，Linux，等等），在第二個驅動器上安裝了其他的作業系統，這時就選擇 '2 個或多個'。</string>

<string lang="zh-hk" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt 目前不支援對包含多個作業系統的整個硬碟驅動器的加密。\n\n可能的解決方法：\n\n- 您可以後退並選擇只加密單系統分區加密其中的一個系統（與選擇加密整個系統驅動器相反）。\n\n- 或者，你也可以把要加密的驅動器中的其他系統遷移到其他的驅動器，而只在其中保留一個系統。</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">單驅動器中包含多個系統</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">在當前運行的系統所安裝的驅動器中，是否包含其他任何作業系統？\n\n說明：例如當前運行的作業系統安裝在驅動器 #0，該驅動器包含幾個分區，其中一個分區安裝了 Windows 系統，而另一個分區安裝了其他任何作業系統（例如. Windows，Mac OS X，Linux，等等.），請選擇 '是'。</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">非 Windows 啟動管理器</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">是否安裝了一個非 Windows 啟動管理器（或啟動管理器）到 MBR 中了嗎?\n\n說明：例如，可啟動的驅動器的第一個柱面包含 GRUB、LILO、XOSL，或其他非 Windows 啟動管理器（或啟動管理器），則選擇 '是'。</string>

<string lang="zh-hk" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">多重啟動</string>

<string lang="zh-hk" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt 目前不支持在 MBR 中安裝的非 Windows 多重啟動管理器。\n\n可能的解決辦法：\n\n- 如果您使用了一個啟動管理器來啟動 Windows 或 Linux，把啟動管理器（典型的，例如 GRUB）從 MBR 中遷移到分區上。之後再次啟動嚮導和加密系統分區/設備。說明：VeraCrypt 啟動管理器將會成為主啟動管理器，並且會允許您把原來的啟動管理器（例如 GRUB）作為第二啟動管理器（通過在 VeraCrypt 啟動管理器螢幕按下 ESC 按鍵），因此你仍然可以啟動 Linux。</string>

<string lang="zh-hk" key="WINDOWS_BOOT_LOADER_HINTS">如果當前運行的系統安裝在活動分區上，隨後，在您加密了該分區後，儘管您想要啟動其他未加密的系統，您仍然要輸入正確的密碼（因為它們都會共用同一個加密的 Windows 啟動管理器）。\n\n相反的，如果當前運行的系統並沒有安裝到 Windows 的啟動分區（或者如果其他系統並未使用 Windows 啟動管理器），隨後，在您加密了該分區後，您在啟動其他未加密的系統時不需要輸入正確的密碼 -- 您只需按 ESC 按鍵來啟動未加密的系統（如果存在多個未加密的系統，您也同樣需要在 VeraCrypt 的啟動管理器中選擇要啟動的系統）。\n\n說明：通常情況下，最早安裝的那個系統一般都會安裝到啟動分區。</string>

<string lang="zh-hk" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">加密主機保護區域（Host Protected Area）</string>

<string lang="zh-hk" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">在很多硬碟的尾部，存在一個相對於作業系統隱藏的區域（這些區域通常被稱作主機保護區域）。然而，某些程式可以從這些區域中讀寫資料。\n\n警告：某些電腦供應商可能使用這些區域存儲用於 RAID、系統恢復、系統設置、診斷的工具和資料，或用於其他目地。如果此類工具和資料必須在啟動前訪問，那麼這些隱藏區域不應當被加密（在上面選擇 '否'）。\n\n您希望 VeraCrypt 檢測和解密系統驅動器尾部這些隱藏區域嗎？</string>

<string lang="zh-hk" key="SYSENC_TYPE_PAGE_TITLE">系統加密類型</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="zh-tw" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">錯誤：不能儲存系統加密設定。</string>

<string lang="zh-tw" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">不能初始化系統加密預先測試。</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="zh-tw" key="WIPE_MODE_TITLE">清除模式</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="zh-tw" key="WIPE_MODE_NONE">無(最快)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="zh-tw" key="WIPE_MODE_3_DOD_5220">3 次複寫(美國國防部 5220.22-M 演算法)</string>

<string lang="zh-tw" key="WIPE_MODE_7_DOD_5220">7 次複寫(美國國防部 5220.22-M 演算法)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="zh-tw" key="SYS_MULTI_BOOT_MODE_TITLE">作業系統數目</string>

<string lang="zh-tw" key="MULTI_BOOT_FOR_ADVANCED_ONLY">警告：經驗不足的使用者從不應該試圖在多重開機的組態設定下加密 Windows。\n\n要繼續嗎？</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">啟動磁碟機</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">目前執行的作業系統安裝到了啟動磁碟機上了嗎？\n\n注意：有時，Windows 可能沒有跟 Windows 開機管理程式(啟動分割區)安裝在同一個磁碟機上。如果是這種情況，選擇 "否"。</string>

<string lang="zh-tw" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt 目前不支援加密不是從安裝作業系統磁碟機開機的作業系統。</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">系統磁碟機數目</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">有多少個磁碟機含有作業系統？\n\n注意：舉例來說，您在主要的磁碟機上安裝了作業系統(例如 Windows，Mac OS X，Linux，等等)又在第二個磁碟機上安裝了額外的作業系統，就選擇 "2 或更多"。</string>

<string lang="zh-tw" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt 目前不支援對整個包含多個作業系統磁碟機的加密。\n\n可能的解決方法：\n\n- 您可以回上一步並選只加密單一系統分割區(相對於去選加密整個系統磁碟機)。\n\n- 另外，如果把磁碟機中的其他系統移到其他的磁碟機只保留一個系統的話您將可以加密整個磁碟機。</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">多個系統在單一磁碟機中</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">在目前執行的作業系統所安裝的磁碟機中，是否包含其他任何的作業系統？\n\n注意：例如目前執行的作業系統安裝在磁碟機 #0，該磁碟機包含了幾個分割區，其中一個分割區安裝 Windows 系統，而另一個分割區安裝了額外任何的作業系統(例如 Windows，Mac OS X，Linux，等等)，選擇 "是"。</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">非 Windows 的開機管理程式</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="zh-tw" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">多重開機</string>

<string lang="zh-tw" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt 目前不支援是在主要啟動磁區中安裝非 Windows 的開機管理程式的多重開機組態設定。\n\n可能的解決辦法：\n\n- 如果您使用了一個啟動管理程式來開啟 Windows 和 Linux，把啟動管理程式(一般來說，GRUB)從主要啟動磁區移到一個分割區上。然後再啟動精靈來加密系統分割區/磁碟機。注意：VeraCrypt 開機管理程式將會成為主要的啟動管理程式，而且會允許您把原來的啟動管理程式(例如 GRUB)作為第二啟動管理程式來執行(經由在 VeraCrypt 開機管理程式畫面按下 'ESC' 鍵)，因此您仍然可以開啟 Linux。</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>

<string lang="en" key="LAUNCH_WIN_ISOBURN">Launch Microsoft Windows Disc Image Burner</string>

<string lang="en" key="RESCUE_DISK_BURN_NO_CHECK_WARN">WARNING: If you already created a VeraCrypt Rescue Disk in the past, it cannot be reused for this system partition/drive because it was created for a different master key! Every time you encrypt a system partition/drive, you must create a new VeraCrypt Rescue Disk for it even if you use the same password.</string>

<string lang="en" key="CANNOT_SAVE_SYS_ENCRYPTION_SETTINGS">Error: Cannot save system encryption settings.</string>

<string lang="en" key="CANNOT_INITIATE_SYS_ENCRYPTION_PRETEST">Cannot initiate the system encryption pretest.</string>

<string lang="en" key="CANNOT_INITIATE_HIDDEN_OS_CREATION">Cannot initiate the process of creation of the hidden operating system.</string>

<string lang="en" key="WIPE_MODE_TITLE">Wipe Mode</string>

<string lang="en" key="INPLACE_ENC_WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data, it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. This also applies to data that are overwritten with their encrypted form (which happens when VeraCrypt initially encrypts an unencrypted partition or drive). According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data you intend encrypt, you may want to select one of the wipe modes (existing data will NOT be lost). Note that wiping will NOT be performed after the partition/drive is encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk.</string>

<string lang="en" key="WIPE_MODE_INFO">On some types of storage media, when data is overwritten with other data (e.g. when the data is erased), it may be possible to recover the overwritten data using techniques such as magnetic force microscopy. According to some studies and governmental publications, recovery of overwritten data can be prevented (or made very difficult) by overwritting the data with pseudorandom and certain non-random data a certain number of times. Therefore, if you believe that an adversary might be able to use such techniques to recover the data that is to be erased, you may want to select one of the multi-pass wipe modes.\n\nNote: The more wipe passes you use, the longer it takes to erase the data.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_TITLE">Wiping</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO_HIDDEN_OS">\nNote: You can interrupt the process of wiping, shut down your computer, start the hidden system again and then resume the process (this wizard will be launched automatically). However, if you interrupt it, the entire process of wiping will have to start from the beginning.</string>

<string lang="en" key="DEVICE_WIPE_PAGE_INFO">\n\nNote: If you interrupt the process of wiping and then attempt to resume it, the entire process will have to start from the beginning.</string>

<string lang="en" key="CONFIRM_WIPE_ABORT">Do you want to abort the process of wiping?</string>

<string lang="en" key="CONFIRM_WIPE_START">Warning: The entire content of the selected partition/device will be erased and lost.</string>

<string lang="en" key="CONFIRM_WIPE_START_DECOY_SYS_PARTITION">The entire content of the partition where the original system resides will be erased.\n\nNote: The entire content of the partition that is to be erased has been copied to this hidden system partition.</string>

<string lang="en" key="WIPE_MODE_WARN">WARNING: Note that when you choose e.g. the 3-pass wipe mode, the time necessary to encrypt the partition/drive will be up to 4 times longer. Likewise, if you choose the 35-pass wipe mode, it will be up to 36 times longer (it might even take several weeks).\n\nHowever, please note that wiping will NOT be performed after the partition/drive is fully encrypted. When the partition/drive is fully encrypted, no unencrypted data is written to it. Any data being written to it is first encrypted on the fly in memory and only then is the (encrypted) data written to the disk (so the performance will NOT be affected).\n\nAre you sure you want to use the wipe mode?</string>

<string lang="en" key="WIPE_MODE_NONE">None (fastest)</string>

<string lang="en" key="WIPE_MODE_1_RAND">1-pass (random data)</string>

<string lang="en" key="WIPE_MODE_3_DOD_5220">3-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_7_DOD_5220">7-pass (US DoD 5220.22-M)</string>

<string lang="en" key="WIPE_MODE_35_GUTMANN">35-pass ("Gutmann")</string>

<string lang="en" key="SYS_MULTI_BOOT_MODE_TITLE">Number of Operating Systems</string>

<string lang="en" key="MULTI_BOOT_FOR_ADVANCED_ONLY">WARNING: Inexperienced users should never attempt to encrypt Windows in multi-boot configurations.\n\nContinue?</string>

<string lang="en" key="HIDDEN_OS_MULTI_BOOT">When creating/using a hidden operating system, VeraCrypt supports multi-boot configurations only when the following conditions are met:\n\n- The currently running operating system must be installed on the boot drive, which must not contain any other operating systems.\n\n- Operating systems installed on other drives must not use any boot loader residing on the drive on which the currently running operating system is installed.\n\nAre the above conditions met?</string>

<string lang="en" key="UNSUPPORTED_HIDDEN_OS_MULTI_BOOT_CFG">VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_TITLE">Boot Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_SYS_EQ_BOOT_HELP">Is the currently running operating system installed on the boot drive?\n\nNote: Sometimes, Windows is not installed on the same drive as the Windows boot loader (boot partition). If that is the case, select 'No'.</string>

<string lang="en" key="SYS_PARTITION_MUST_BE_ON_BOOT_DRIVE">VeraCrypt currently does not support encrypting an operating system that does not boot from the drive on which it is installed.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_TITLE">Number of System Drives</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NBR_SYS_DRIVES_HELP">How many drives contain an operating system?\n\nNote: For example, if you have any operating system (e.g. Windows, Mac OS X, Linux, etc.) installed on your primary drive and any additional operating system installed on your secondary drive, select '2 or more'.</string>

<string lang="en" key="WDE_UNSUPPORTED_FOR_MULTIPLE_SYSTEMS_ON_ONE_DRIVE">VeraCrypt currently does not support encrypting a whole drive that contains multiple operating systems.\n\nPossible Solutions:\n\n- You can still encrypt one of the systems if you go back and choose to encrypt only a single system partition (as opposed to choosing to encrypt the entire system drive).\n\n- Alternatively, you will be able to encrypt the entire drive if you move some of the systems to other drives leaving only one system on the drive you want to encrypt.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_TITLE">Multiple Systems on Single Drive</string>

<string lang="en" key="SYSENC_MULTI_BOOT_ADJACENT_SYS_HELP">Are there any other operating systems installed on the drive on which the currently running operating system is installed?\n\nNote: For example, if the currently running operating system is installed on the drive #0, which contains several partitions, and if one of the partitions contains Windows and another partition contains any additional operating system (e.g. Windows, Mac OS X, Linux, etc.), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_TITLE">Non-Windows Boot Loader</string>

<string lang="en" key="SYSENC_MULTI_BOOT_NONWIN_BOOT_LOADER_HELP">Is a non-Windows boot loader (or boot manager) installed in the master boot record (MBR)?\n\nNote: For example, if the first track of the boot drive contains GRUB, LILO, XOSL, or some other non-Windows boot manager (or boot loader), select 'Yes'.</string>

<string lang="en" key="SYSENC_MULTI_BOOT_OUTCOME_TITLE">Multi-Boot</string>

<string lang="en" key="CUSTOM_BOOT_MANAGERS_IN_MBR_UNSUPPORTED">VeraCrypt currently does not support multi-boot configurations where a non-Windows boot loader is installed in the Master Boot Record.\n\nPossible Solutions:\n\n- If you use a boot manager to boot Windows and Linux, move the boot manager (typically, GRUB) from the Master Boot Record to a partition. Then start this wizard again and encrypt the system partition/drive. Note that the VeraCrypt Boot Loader will become your primary boot manager and it will allow you to launch the original boot manager (e.g. GRUB) as your secondary boot manager (by pressing Esc in the VeraCrypt Boot Loader screen) and thus you will be able boot Linux.</string>

<string lang="en" key="WINDOWS_BOOT_LOADER_HINTS">If the currently running operating system is installed on the boot partition, then, after you encrypt it, you will need to enter the correct password even if you want to start any other unencrypted Windows system(s) (as they will share a single encrypted Windows boot loader/manager).\n\nIn contrast, if the currently running operating system is not installed on the boot partition (or if the Windows boot loader/manager is not used by any other system), then, after you encrypt this system, you will not need to enter the correct password to boot the other unencrypted system(s) -- you will only need to press the Esc key to start the unencrypted system (if there are multiple unencrypted systems, you will also need to choose which system to start in the VeraCrypt Boot Manager menu).\n\nNote: Typically, the earliest installed Windows system is installed on the boot partition.</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_TITLE">Encryption of Host Protected Area</string>

<string lang="en" key="SYSENC_PRE_DRIVE_ANALYSIS_HELP">At the end of many drives, there is an area that is normally hidden from the operating system (such areas are usually referred to as Host Protected Areas). However, some programs can read and write data from/to such areas.\n\nWARNING: Some computer manufacturers may use such areas to store tools and data for RAID, system recovery, system setup, diagnostic, or other purposes. If such tools or data must be accessible before booting, the hidden area should NOT be encrypted (choose 'No' above).\n\nDo you want VeraCrypt to detect and encrypt such a hidden area (if any) at the end of the system drive?</string>

<string lang="en" key="SYSENC_TYPE_PAGE_TITLE">Type of System Encryption</string>