Annuller Installer &til alle brugere Gen&nemse... Tilføj VeraCrypt ikon til &skrivebord Donate now... Registrer .hc fil &endelser som VeraCrypt &Åben destinationsmappen efter afslutning Tilføj VeraCrypt til &Start menu Opret system &gendannelsespunkt &Afinstaller &Udpak &Installer VeraCrypt Oprettelsesguide Afinstaller VeraCrypt &Hjælp Vælg eller indtast venligst placeringen hvor du ønsker at gemme de udpakkede filer: Vælg eller indtast venligst placeringen hvor du ønsker at installere VeraCrypt program filerne. Hvis den angivne mappe ikke eksisterer, vil den automatisk blive oprettet. Klik på Afinstaller for at fjerne VeraCrypt fra systemet. Afbryd &Benchmark &Test Create encrypted volume and format it Encrypt partition in place Vis de generede nøgler (deres mængde) Vis pool indhold Download CD/DVD brænde software Create an encrypted file container &GB &TB Mere information Sk&jult VeraCrypt bind Mere information om skjulte bind Direkte tilstand Normal tilstand &KB Brug nøglef&iler Try first to mount with an empty password Random size ( 64 <-> 1048576 ) Nøglefiler.. Information om hakke algoritmer Mere information Information on PIM &MB Mere information Mere information om system kryptering Mere information Multi-boot Encrypt a non-system partition/drive Gem aldrig hi&storik Åben Ydre Bind &Pause Use P&IM Use PIM Ekspres Formatering &Vis kodeord &Vis kodeord &Display PIM Single-boot Standard VeraCrypt bind Skj&ult Normalt Krypter system partitionen eller hele system drevet Krypter Windows system partitionen Krypter hele drevet VeraCrypt Bind Oprettelsesguide Klynge VIGTIGT: Bevæg musen så tilfældigt som muligt indenfor dette vindue. Jo længere tid du bevæger den, jo bedre. Dette forhøjer den kryptografiske styrke af krypteringsnøglerne betydeligt. Klik på Næste for at fortsætte. Godkend: Fuldført Drive letter: Krypterings Algoritme Filsystem Opretter en virtuel krypteret disk inden i en fil. Anbefales til uerfarne brugere. Valg Hakke Algoritme Etiketnøgle: Venstre Hovednøgle: Vælg dette hvis der er to eller flere operativsystemer installeret på denne computer.\n\nFor eksempel:\n- Windows XP og Windows XP\n- Windows XP og Windows Vista\n- Windows og Mac OS X\n- Windows og Linux\n- Windows, Linux og Mac OS X Encrypts a non-system partition on any internal or external drive (e.g. a flash drive). Optionally, creates a hidden volume. Nuværende pool indhold (partiel) Pass Kodeord: Volume PIM: Volume PIM: Udførsel: Tilfældig Pool: Vælg dette hvis der kun er et operativsystem installeret på denne computer (også selv om der er flere brugere). Hastighed Status Nøgler, salt, og anden data er blevet oprettet med succes. Hvis du ønsker at oprette nye nøgler, klik på Tilbage og så Næste. Ellers klik på Næste for at fortsætte. Krypterer partitionen/drevet hvor Windows er installeret. Enhver der ønsker at få adgang og bruge systemet, læse og skrive filer, osv., er nødt til at indtaste det korrekte kodeord hver gang inden Windows booter op. Valgfrit, oprettes et skjult system. Select this option to encrypt the partition where the currently running Windows operating system is installed. Volume Label in Windows: Udviske tilstand: Luk Allow pre-boot &authentication to be bypassed by pressing the Esc key (enables boot manager) Gør Ingenting Tilslut &Automatisk til VeraCrypt Bind (angiv neden for) &Start VeraCrypt Auto-&Detect Library &Cache pre-boot authentication password in driver memory (for mounting of non-system volumes) Gennemse... Gennemse... Gem kodeord og nøgl&efiler i hukommelsen Afslut når alle tilsluttede bind afbrydes &Close token session (log out) after a volume is successfully mounted Include VeraCrypt Volume Expander Anvend VeraCrypt Bind Oprettelsesguide Opret &Opret Bind Do not &show any texts in the pre-boot authentication screen (except the below custom message) Disable "Evil Maid" attack detection Accelerate AES encryption/decryption by using the AES instructions of the processor (if available) Brug nøglef&iler Brug nøglef&iler Afslut Help on favorite volumes Do not mount selected volume when 'Mount Favorite Volumes' &hot key is pressed Mount selected volume when its host device gets &connected Mount selected volume upon log&on Mount selected volume as read-o&nly Mount selected volume as remo&vable medium Move &Down Move &Up Open &Explorer window for selected volume when successfully mounted &Fjern Use favorite label as Explorer drive label Global Settings Display balloon tooltip after successful hot-key dismount Play system notification sound after successful hot-key dismount Alt Ctrl Shift Win Tildel Fjern Nøglefiler... Do not use the following number of logical processors for encryption/decryption: More information More information More Settings... A&uto-Tilslut Enheder Tilslutnings Va&lg... Tilslut bind som læs-&kun Nøglefiler... (Empty or 0 for default iterations) (Empty or 0 for default iterations) Tilsluttet Gem kodeord i driverhukommelse Auto-afbryd bind efter der ikke har været læst/skrevet til det i Brugeren logger af User session locked Går i strømbesparende funktion Pauseskærm aktiveres Udfør auto-afbryd selvom bindet indeholder åbne filer eller mapper Tilslut alle enheds-baserede VeraCrypt bind Start VeraCrypt Background Task Tilslut bind som læs-kun Tilslut bind som flytbart medie Åben Explorer vindue til succesfuldt tilsluttet bind Temporarily cache password during "Mount Favorite Volumes" operations Use a different taskbar icon when there are mounted volumes Slet kodeord i hukommelsen ved auto-afbryd Slet kodeord i hukommelsen ved afslut Preserve modification timestamp of file containers Nulstil Vælg &Enhed... Vælg &Fil... Select &Library... Vis kodeord Vis kodeord Åben &Explorer vindue for tilsluttet bind &Gem kodeord i driver-hukommelsen &TrueCrypt Mode Afb&ryd Alle Bin&d Egenskaber... Bind V&ærktøjer... &Slet hukommelsen VeraCrypt - Mount Parameters VeraCrypt - Favorite Volumes VeraCrypt - System genvejstaster VeraCrypt Ændre Kodeord eller Nøglefiler Indtast VeraCrypt Bind kodeord VeraCrypt - Performance and Driver Options VeraCrypt - Præferencer VeraCrypt - System Encryption Settings VeraCrypt - Security Token Preferences VeraCrypt Rejse Disk Setup VeraCrypt Bind Egenskaber Om... Tilføj/Fjern nøglefiler til/fra Bind... Add Mounted Volume to Favorites... Add Mounted Volume to System Favorites... Analyze a System Crash... Backup Af Bind Etiket... Benchmark... Ændre etiketnøgle oprindelses algoritme... Ændre Bind kodeord... Indstil Etiketnøgle Oprindelses Algoritme... Ændre Kodeord... Slet Bind Historie Close All Security Token Sessions Kontakt... Opret Skjult Operativsystem... Opret Nødhjælps Disk... Opret nyt Bind... Permanently Decrypt... Standard nøglefiler... Default Mount Parameters... Donate now... Krypter System Partition/Drev... FAQ - Ofte stillede spørgsmål Brugervejledning &Hjemmeside Genvejstaster... Nøglefil Generator Sprog... Juridiske Bemærkninger Manage Security Token Keyfiles... Auto-Tilslut alle Enheds-placerede Bind Tilslut Favorit Bind Tilslut uden før-boot &godkendelse... Tilslut Bind Tilslut Bind med funktioner Nyheder Online Hjælp Begyndervejledning Organize Favorite Volumes... Organize System Favorite Volumes... Performance/Driver Configuration Dekrypter System Partition/Drev Permanent Præferencer... Opdater drev bogstaver Fjern alle nøglefiler fra Bind... Gendan Bind Etiket... Genoptag afbrudt proces Vælg Enhed... Vælg Fil... Genoptag afbrudt proces System Encryption... Properties... Settings... System Favorite Volumes... Downloads Test Vektorer... Security Tokens... Rejse Disk Setup... Afbryd alle tilsluttede Bind Afbryd Bind Kontroller Nødhjælps Disk Verify Rescue Disk Image Versions Historik Volume Expander Bind Egenskaber Bind Oprettelsesguide VeraCrypt Hjemmeside Slet kodeord i hukommelsen OK Hardware Acceleration Genvej AutoRun Konfiguration (autorun.inf) Auto-Afbryd Afbryd alle når: Boot Loader Screen Options Bekræft kodeord: Nuværende Display this custom message in the pre-boot authentication screen (24 characters maximum): Standard Tilslutning Funktioner Genvejstast Funktioner Driver Configuration Enable extended disk control codes support Label of selected favorite volume: Fil Indstillinger Tildel tast: Processor (CPU) in this computer supports hardware acceleration for AES: Opgaver der skal udføres ved login til Windows minutter Tilslut bind som drev bogstav: Tilslutnings Indstillinger Ny Kodeord: Thread-Based Parallelization PKCS #11 Library Path PKCS-5 PRF: PKCS-5 PRF: Kodeords hukommelse Security Options VeraCrypt Baggrundsopgaver VeraCrypt bind for tilslutning (relaterer til rejse disk rod): Ved isættelse af rejse disk: Opret rejse disk filer i (rejse disk rod mappe): Bind Windows Tilføj &sti... &Auto-Test alle &Fortsæt &Dekrypter &Delete &Krypter &Export... Generer og gem nøglefil... &Generer tilfældig nøglefil... Download sprogpakker Hardware-accelerated AES: &Import Keyfile to Token... Add &Files... Brug nøglef&iler &Nøglefiler... &Fjern Fjern &Alle Hvad er skjult bind beskyttelse? More information on keyfiles Tilslut bind som flytbart &medie Tilslut partition &ved brug af system kryptering uden før-boot godkendelse Parallelization: Benchmark &Udskriv &Beskyt skjult bind imod skade forårsaget af skrivning til ydre bind &Nulstil &Vis kodeord Add &Token Files... Brug backup header implementeret i &Bind hvis tilgængeligt XTS tilstand Om VeraCrypt VeraCrypt - Krypterings algoritme benchmark VeraCrypt - Test vektorer Kommandolinie Hjælp VeraCrypt - Nøglefiler VeraCrypt - Nøglefil Generator VeraCrypt - Sprog VeraCrypt - Tilslutningsvalg New Security Token Keyfile Properties VeraCrypt - Random Pool Enrichment Vælg en Partition eller Enhed VeraCrypt Security Token Keyfiles Security token password/PIN required Aktive sprogpakker Hastigheden afhænger af CPU belastning og hukommelseenhed karakteristik.\n\nDisse tests foregår i RAM. Buffer Størrelse: Ciffer: K&odeord til skjult bind:\n(tomt=hukommelse) Skjult bind beskyttelse Nøgle størrelse: VIGTIGT: Bevæg musen så tilfældigt som muligt i dette vindue. Jo længere tid du bevæger den, jo bedre. Dette forbedrer signifikant den kryptografiske styrke på nøglefilen. ADVARSEL: Hvis du mister en nøglefil eller dele af dens første 1024 kilobytes ændres, vil det være umuligt at tilslutte bindet som bruger denne nøglefil! bits Number of keyfiles: Keyfiles size: Keyfiles base name: Oversat af: Ren tekst størrelse: bits Nuværende Pool Indhold Blandet PRF: IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases security. When done, click 'Continue'. Sekundær nøgle (hexadecimal) Security token: Sorterings Metode: Please wait. This process may take a long time... Please wait...\nThis process may take a long time and VeraCrypt may seem unresponsive. Blok nummer: Ciffer tekst (hexadecimal) Data enheds nummer (64-bit hexadecimal, data enheds størrelsen er 512 bytes) Nøgle (hexadecimal) Ren tekst (hexadecimal) Keyfile name: XTS tilstand S&ystem &Bind Favor&ites &Værktøjer In&dstillinger &Hjælp Hjemme&side &Om... Læs-kun egenskaben på dit gamle bind kan ikke ændres. Kontroller venligst filadgangs tilladelser. Fejl: Adgang nægtet.\n\nPartitionen du prøver at få adgang til er enten 0 sektorer lang, eller det er boot enheden. Administrator For at kunne loade VeraCrypt driveren, er du nødt til at være logget ind med en brugerkonto med administrator rettigheder. Bemærk venligst for at kunne kryptere/formatere en partition/enhed er du nødt til at være logget ind med en brugerkonto med administrator rettigheder.\n\nDette gælder ikke for fil-værtede bind. Unable to activate fast file creation: Administrator privileges required.\nPlease relaunch the program as an Administrator to enable this feature.\n\nWould you like to proceed without fast file creation? For at oprette et skjult bind er du nødt til at være logget ind med en brugerkonto med administrator rettigheder.\n\nContinue? Bemærk venligst for at kunne formatere bindet som NTFS er du nødt til at være logget ind med en brugerkonto med administrator rettigheder.\n\nUden administrator rettigheder, kan du formatere bindet som FAT. FIPS-godkendt ciffer (Rijndael, udgivet i 1998) som kan benyttes af U.S. regerings afdelinger og bureauer for at beskytte klassificeret information op til Top Secret niveau. 256-bit nøgle, 128-bit blok, 14 runder (AES-256). Drift tilstand er XTS. Bindet er allerede tilsluttet. ADVARSEL: Mindst en kryptering eller hakke algoritme fejlede ved de automatiske selv-tests!\n\nVeraCrypt installationen kan være ødelagt. ADVARSEL: Der er ikke nok data i tilfældigheds nummer generator pool til at forsyne det nødvendige antal data.\n\nDu bør ikke fortsætte yderligere. Vælg venligst 'Rapporter en fejl...' fra Hjælp menuen, og rapporter denne fejl. Drevet er beskadiget (der er en fysisk skade på det) eller et kabel er beskadiget, eller hukommelsen har en fejlfunktion.\n\nBemærk venligst at dette er et problem med din hardware, ikke med VeraCrypt. Rapporter derfor venligst IKKE dette som en fejl/problem i VeraCrypt og spørg venligst IKKE om hjælp med dette i VeraCrypt Forums. Kontakt venligst din computer forhandlers tekniske support team for assistance. Tak.\n\nBemærk: Hvis fejlen opstår gentagne gange samme sted, er det højst sandsynligt forårsaget af en dårlig disk blok, som burde være mulig at reparere ved brug af tredieparts software (bemærk at, i mange tilfælde, kan 'chkdsk /r' kommandoen ikke rette den fordi den arbejder på filsystem niveau; i nogle tilfælde, kan 'chkdsk' værktøjet ikke engang opdage den). If you are accessing a drive for removable media, please make sure that a medium is inserted in the drive. The drive/medium may also be damaged (there may be a physical defect on it) or a cable may be damaged/disconnected. Your system appears to be using custom chipset drivers containing a bug that prevents encryption of the whole system drive.\n\nPlease try updating or uninstalling any custom (non-Microsoft) chipset drivers before proceeding. If it does not help, try encrypting the system partition only. Ugyldigt drev bogstav. Ugyldig sti. Annuller Enheden ikke tilgængelig. Sørg for at enheden eksisterer og ikke er i brug af systemet. Advarsel: Caps Lock er slået til. Dette kan medføre at kodeordet indtastes forkert. Bind Type Det kan ske at du bliver tvunget til at afsløre kodeordet til et krypteret bind. Der er mange situationer hvor du ikke kan afvise at afsløre kodeordet (for eksempel, pga. afpresning). Ved brug af et såkaldt skjult bind tillader det dig at klare sådanne situationer uden at afsløre kodeordet til dit bind. Vælg dette hvis du ønsker at oprette et normalt VeraCrypt bind. Bemærk venligst at hvis du ønsker at installere et operativsystem i et skjult partitions bind, så kan hele system drevet ikke blive kryptereret ved hjælp af en enkelt nøgle. Ydre Bind Krypterings Funktioner Skjult Bind Krypterings Funktioner Krypterings Funktioner ADVARSEL: Kunne ikke slette stien til det senest valgte bind/nøglefil (historik af filgennemsyn)! Fejl: Beholderen er blevet komprimeret ved filsystem niveau. VeraCrypt understøtter ikke komprimerede beholdere (Bemærk: Komprimering at krypterede data er ueffektivt og overflødig).\n\nSlå venligst komprimering af denne beholder fra ved at følge disse trin: 1) Højreklik på denne beholder i Windows Stifinder (ikke i VeraCrypt). 2) Vælg 'Egenskaber'. 3) I 'Egenskaber' dialog boks, klik 'Avanceret'. 4) I 'Advancede Attributter' dialog boks, slå funktionen 'Komprimer indhold for at spare diskplads' fra og klik 'OK'. 5) I 'Egenskaber' dialog boks, Klik 'OK'. Fejl i oprettelsen af bind %s Størrelsen af %s er %.2f bytes Størrelsen af %s er %.2f KB Størrelsen af %s er %.2f MB Size of %s is %.2f GB Size of %s is %.2f TB Size of %s is %.2f PB ADVARSEL: Enhed/partition er i brug af operativsystem eller andre applikationer. Formatering af enhed/partition kan medføre data korruption og system ustabilitet.\n\nFortsæt? Warning: The partition is in use by the operating system or applications. You should close any applications that might be using the partition (including antivirus software).\n\nContinue? Fejl: Enhed/partition indeholder et filsystem som ikke kunne afbrydes. Filsystemet kan være i brug af operativsystem. Formatering af enhed/partition vil sandsynligvis medføre data korruption og system ustabilitet.\n\nFor at løse dette problem, anbefaler vi at du først sletter paritionen og så genopretter den uden formatering. For at gøre dette, følg disse trin: 1) Højreklik på 'Computer' (eller 'Denne computer') ikonet i 'Start Menuen' og vælg and select 'Administrer'. Vinduet 'Computeradministration' bør da komme frem. 2) I vinduet 'Computeradministration', vælg 'Lager' > 'Diskhåndtering'. 3) Højreklik på den partition du vil kryptere og vælg enten 'slet partition', eller 'slet bind', eller 'slet logisk drev'. 4) Klik 'Ja'. Hvis Windows beder dig om at genstarte computeren, gør dette. Gentag da trin 1 og 2 og fortsæt fra trin 5. 5) Højreklik på området for tildelt/ledig disk plads og vælg enten 'Ny Partition', eller 'Nyt Simpelt Bind', eller 'Nyt logisk drev'. 6) 'Ny Partition hjælp' eller 'Nyt Simpelt Bind hjælp' vinduet burde komme frem nu; følg instruktionerne. På hjælpesiden benævnt 'Formater Partition', vælg enten 'formater ikke denne partition' eller 'formater ikke dette bind'. I samme hjælp, klik 'Næste' og så 'Afslut'. 7) Bemærk at enhedsstien du har valgt i VeraCrypt måske er forkert nu. Derfor, gå ud af VeraCrypt Bind Oprettelseshjælp (hvis den stadig er åben) og så start den igen. 8) Prøv at kryptere enhed/partition igen.\n\nHvis VeraCrypt gentagne gange giver fejl ved kryptering af enhed/partition, måtte du måske overveje at oprette en fil-beholder istedet. Error: The filesystem could not be locked and/or dismounted. It may be in use by the operating system or applications (for example, antivirus software). Encrypting the partition might cause data corruption and system instability.\n\nPlease close any applications that might be using the filesystem (including antivirus software) and try again. If it does not help, please follow the below steps. ADVARSEL: Nogle af de tilsluttede enheder/partitioner er var allerede i brug!\n\nIgnoreres dette kan det medføre uønskede resultater inklusiv system ustabilitet.\n\nVi anbefaler kraftigt at du lukker enhver applikation der måtte bruge enheden/partitionen. Den valgte enhed indeholder partitioner.\n\nFormatering af enheden kan forårsage system ustabilitet og/eller data korruption. Vælg venligst enten en partition på enheden, eller fjern alle partitioner på enheden for at VeraCrypt kan formatere den sikkert. The selected non-system device contains partitions.\n\nEncrypted device-hosted VeraCrypt volumes can be created within devices that do not contain any partitions (including hard disks and solid-state drives). A device that contains partitions can be entirely encrypted in place (using a single master key) only if it is the drive where Windows is installed and from which it boots.\n\nIf you want to encrypt the selected non-system device using a single master key, you will need to remove all partitions on the device first to enable VeraCrypt to format it safely (formatting a device that contains partitions might cause system instability and/or data corruption). Alternatively, you can encrypt each partition on the drive individually (each partition will be encrypted using a different master key).\n\nNote: If you want to remove all partitions from a GPT disk, you may need to convert it to a MBR disk (using e.g. the Computer Management tool) in order to remove hidden partitions. Warning: If you encrypt the entire device (as opposed to encrypting only a partition on it), operating systems will consider the device as new, empty, and unformatted (as it will contain no partition table) and may spontaneously initialize the device (or ask you if you want to do so), which may damage the volume. Furthermore, it will not be possible to consistently mount the volume as favorite (e.g. when the drive number changes) or to assign a favorite-volume label to it.\n\nTo avoid that you may want to consider creating a partition on the device and encrypting the partition instead.\n\nAre you sure want to encrypt the entire device? IMPORTANT: Please keep in mind that this volume can NOT be mounted/accessed using the drive letter %c:, which is currently assigned to it!\n\nTo mount this volume, click 'Auto-Mount Devices' in the main VeraCrypt window (alternatively, in the main VeraCrypt window, click 'Select Device', then select this partition/device, and click 'Mount'). The volume will be mounted to a different drive letter, which you select from the list in the main VeraCrypt window.\n\nThe original drive letter %c: should be used only in case you need to remove encryption from the partition/device (e.g., if you no longer need encryption). In such a case, right-click the drive letter %c: in the 'Computer' (or 'My Computer') list and select 'Format'. Otherwise, the drive letter %c: should never be used (unless you remove it, as described e.g. in the VeraCrypt FAQ, and assign it to another partition/device). In-place encryption of non-system volumes is not supported on the version of the operating system you are currently using (it is supported only on Windows Vista and later versions of Windows).\n\nThe reason is that this version of Windows does not support shrinking of a filesystem (the filesystem needs to be shrunk to make space for the volume header and backup header). The selected partition does not appear to contain an NTFS filesystem. Only partitions that contain an NTFS filesystem can be encrypted in place.\n\nNote: The reason is that Windows does not support shrinking of other types of filesystems (the filesystem needs to be shrunk to make space for the volume header and backup header). The selected partition does not appear to contain an NTFS filesystem. Only partitions that contain an NTFS filesystem can be encrypted in place.\n\nIf you want to create an encrypted VeraCrypt volume within this partition, choose the option "Create encrypted volume and format it" (instead of the option "Encrypt partition in place"). Error: The partition is too small. VeraCrypt cannot encrypt it in place. To encrypt the data on this partition, please follow these steps:\n\n1) Create a VeraCrypt volume on an empty partition/device and then mount it.\n\n2) Copy all files from the partition that you originally wanted to encrypt to the mounted VeraCrypt volume (that has been created and mounted in step 1). That way, you will create a VeraCrypt-encrypted backup of the data.\n\n3) Create a VeraCrypt volume on the partition that you originally wanted to encrypt and make sure that (in the VeraCrypt wizard) you choose the option "Create encrypted volume and format it" (instead of the option "Encrypt partition in place"). Note that all data stored on the partition will be erased. After the volume is created, mount it.\n\n4) Copy all files from the mounted backup VeraCrypt volume (created and mounted in step 1) to the mounted VeraCrypt volume that has been created (and mounted) in step 3.\n\nAfter you complete these steps, the data will be encrypted and, in addition, there will be an encrypted backup of the data. VeraCrypt can in-place encrypt only a partition, a dynamic volume, or an entire system drive.\n\nIf you want to create an encrypted VeraCrypt volume within the selected non-system device, choose the option "Create encrypted volume and format it" (instead of the option "Encrypt partition in place"). Error: VeraCrypt can in-place encrypt only a partition, a dynamic volume, or an entire system drive. Please make sure the specified path is valid. Error: Cannot shrink the filesystem (the filesystem needs to be shrunk to make space for the volume header and backup header).\n\nPossible causes and solutions:\n\n- Not enough free space on the volume. Please make sure no other application is writing to the filesystem.\n\n- Corrupted file system. Try to check it and fix any errors (right-click the corresponding drive letter in the 'Computer' list, then select Properties > Tools > 'Check Now', make sure the option 'Automatically fix file system errors' is enabled and click Start).\n\nIf the above steps do not help, please follow the below steps. Error: There is not enough free space on the volume and so the filesystem cannot be shrunk (the filesystem needs to be shrunk to make space for the volume header and backup header).\n\nPlease delete any redundant files and empty the Recycle Bin so as to free at least 256 KB of space and then try again. Note that due to a Windows issue, the amount of free space reported by the Windows Explorer may be incorrect until the operating system is restarted. If restarting the system does not help, the file system may be corrupted. Try to check it and fix any errors (right-click the corresponding drive letter in the 'Computer' list, then select Properties > Tools > 'Check Now', make sure the option 'Automatically fix file system errors' is enabled and click Start).\n\nIf the above steps do not help, please follow the below steps. Den ledige plads på drevet %s er %.2f bytes. Free space on drive %s is %.2f KB Free space on drive %s is %.2f MB Free space on drive %s is %.2f GB Free space on drive %s is %.2f TB Free space on drive %s is %.2f PB Kunne ikke finde ledige drev bogstaver. Fejl: VeraCrypt driver er ikke fundet.\n\nKopier venligst filerne 'veracrypt.sys' og 'veracrypt-x64.sys' til biblioteket hvor VeraCrypt hovedprogrammet (VeraCrypt.exe) er placeret. Error: An incompatible version of the VeraCrypt driver is currently running.\n\nIf you are trying to run VeraCrypt in portable mode (i.e. without installing it) and a different version of VeraCrypt is already installed, you must uninstall it first (or upgrade it using the VeraCrypt installer). To uninstall it, follow these steps: On Windows Vista or later, select 'Start Menu' > Computer > 'Uninstall or change a program' > VeraCrypt > Uninstall; on Windows XP, select 'Start Menu' > Settings > 'Control Panel' > 'Add Or Remove Programs' > VeraCrypt > Remove.\n\nSimilarly, if you are trying to run VeraCrypt in portable mode (i.e. without installing it) and a different version of VeraCrypt is already running in portable mode, you must restart the system first and then run only this new version. Fejl: Ciffer initialiseringsfejl. Fejl: En svag eller potientiel svag nøgle er detekteret. Nøglen vil blive afvist. Prøv venligst igen. A critical error has occurred and VeraCrypt must be terminated. If this is caused by a bug in VeraCrypt, we would like to fix it. To help us, you can send us an automatically generated error report containing the following items:\n\n- Program version\n- Operating system version\n- Type of CPU\n- VeraCrypt component name\n- Checksum of VeraCrypt executable\n- Symbolic name of dialog window\n- Error category\n- Error address\n- VeraCrypt call stack\n\nIf you select 'Yes', the following URL (which contains the entire error report) will be opened in your default Internet browser.\n\n%hs\n\nDo you want to send us the above error report? A critical error has occurred in your system, which requires VeraCrypt to be terminated.\n\nNote that this error has not been caused by VeraCrypt (so the VeraCrypt developers cannot fix it). Please, check your system for possible problems (e.g., system configuration, network connection, failing hardware components). A critical error has occurred in your system, which requires VeraCrypt to be terminated.\n\nIf this problem persists, you may want to try disabling or uninstalling applications that could potentially be causing this issue, such as antivirus or Internet security software, system "enhancers", "optimizers" or "tweakers", etc. If it does not help, you may want to try reinstalling your operating system (this problem may also be caused by malware). VeraCrypt Kritisk Fejl VeraCrypt detected that the operating system recently crashed. There are many potential reasons why the system could have crashed (for example, a failing hardware component, a bug in a device driver, etc.)\n\nDo you want VeraCrypt to check whether a bug in VeraCrypt could have caused the system crash? Do you want VeraCrypt to continue detecting system crashes? VeraCrypt found no system crash minidump file. Do you want to delete the Windows crash dump file to free up disk space? In order to analyze the system crash, VeraCrypt needs to install Microsoft Debugging Tools for Windows first.\n\nAfter you click OK, the Windows installer will download the Microsoft Debugging Tools installation package (16 MB) from a Microsoft server and install it (the Windows installer will be forwarded to the Microsoft server URL from the veracrypt.org server, which ensures that this feature works even if Microsoft changes the location of the installation package). After you click OK, VeraCrypt will analyze the system crash. This may take up to several minutes. Please make sure the environment variable 'PATH' includes the path to 'kd.exe' (Kernel Debugger). It appears that VeraCrypt most likely did not cause the system crash. There are many potential reasons why the system could have crashed (for example, a failing hardware component, a bug in a device driver, etc.) Results of the analysis indicate that updating the following driver might solve this issue: To help us determine whether there is a bug in VeraCrypt, you can send us an automatically generated error report containing the following items:\n- Program version\n- Operating system version\n- Type of CPU\n- Error category\n- Driver name and version\n- System call stack\n\nIf you select 'Yes', the following URL (which contains the entire error report) will be opened in your default Internet browser. Do you want to send us the above error report? &Krypter &Dekrypter &Dekrypter permanent Afslut Opret venligst et logisk drev til denne udvidede partition, og prøv igen. A VeraCrypt volume can reside in a file (called VeraCrypt container), which can reside on a hard disk, on a USB flash drive, etc. A VeraCrypt container is just like any normal file (it can be, for example, moved or deleted as any normal file). Click 'Select File' to choose a filename for the container and to select the location where you wish the container to be created.\n\nWARNING: If you select an existing file, VeraCrypt will NOT encrypt it; the file will be deleted and replaced with the newly created VeraCrypt container. You will be able to encrypt existing files (later on) by moving them to the VeraCrypt container that you are about to create now. Select the location of the outer volume to be created (within this volume the hidden volume will be created later on).\n\nA VeraCrypt volume can reside in a file (called VeraCrypt container), which can reside on a hard disk, on a USB flash drive, etc. A VeraCrypt container can be moved or deleted as any normal file. Click 'Select File' to choose a filename for the container and to select the location where you wish the container to be created. If you select an existing file, VeraCrypt will NOT encrypt it; it will be deleted and replaced with the newly created container. You will be able to encrypt existing files (later on) by moving them to the VeraCrypt container you are about to create now. Encrypted device-hosted VeraCrypt volumes can be created within partitions on hard disks, solid-state drives, USB memory sticks, and on any other supported storage devices. Partitions can also be encrypted in place.\n\nIn addition, encrypted device-hosted VeraCrypt volumes can be created within devices that do not contain any partitions (including hard disks and solid-state drives).\n\nNote: A device that contains partitions can be entirely encrypted in place (using a single key) only if it is the drive where Windows is installed and from which it boots. A device-hosted VeraCrypt volume can be created within a hard disk partition, solid-state drive, USB memory stick, and other storage devices.\n\nWARNING: Note that the partition/device will be formatted and all data currently stored on it will be lost. \nSelect the location of the outer volume to be created (within this volume the hidden volume will be created later on).\n\nOuter volumes can be created within partitions on hard disks, solid-state drives, USB memory sticks, and on any other supported storage devices. Outer volumes can also be created within devices that do not contain any partitions (including hard disks and solid-state drives).\n\nWARNING: Note that the partition/device will be formatted and all data currently stored on it will be lost. Vælg lokationen på det VeraCrypt bind hvori du ønsker at oprette et skjult bind. WARNING: The host file/device is already in use!\n\nIgnoring this can cause undesired results including system instability. All applications that might be using the host file/device (for example, antivirus or backup applications) should be closed before mounting the volume.\n\nContinue mounting? Fejl: Kan ikke tilslutte bind. Værts filen/enheden er allerede i brug. Forsøg på at tilslutte uden eksklusiv adgang fejlede også. Filen kunne ikke åbnes. Bind placering Store Filer Ønsker du at gemme filer større end 4 GB i dette VeraCrypt bind? Afhængigt af dit valg ovenfor, vil VeraCrypt vælge et passende standard filsystem til dit VeraCrypt bind (du vil være i stand til at vælge et filsystem i det næste trin). Da du opretter et ydre bind, bør du overveje at vælge 'Nej'. Hvis du vælger 'Ja', vil standard filsystemet blive NTFS, hvilket ikke er så passende til ydre bind som FAT (for eksempel, den maksimalt mulige størrelse på det skjulte bind vil blive væsentligt større hvis det ydre bind er formatteret som FAT). Normalt er FAT standard for både skjulte og normale bind (så FAT bind er ikke så mistænkelige). Dog, hvis brugeren indikerer ønske om at gemme filer større end 4 GB (hvilket FAT filsystemet ikke tillader), så er FAT ikke standard. Er du sikker på du ønsker at vælge 'Ja'? Bind oprettelses tilstand This is the fastest way to create a partition-hosted or device-hosted VeraCrypt volume (in-place encryption, which is the other option, is slower because content of each sector has to be first read, encrypted, and then written). Any data currently stored on the selected partition/device will be lost (the data will NOT be encrypted; it will be overwritten with random data). If you want to encrypt existing data on a partition, choose the other option. The entire selected partition and all data stored on it will be encrypted in place. If the partition is empty, you should choose the other option (the volume will be created much faster). Bemærk: &Genoptag &Udsæt &Start &Fortsæt &Formater &Wipe Afbryd formatering? Vis mere information Vis ikke dette igen The content of the partition/device has been successfully erased. The content of the partition where the original system (of which the hidden system is a clone) resided has been successfully erased. Please make sure the version of Windows you are going to install (on the wiped partition) is the same as the version of Windows you are currently running. This is required due to the fact that both systems will share a common boot partition. The system partition/drive has been successfully encrypted.\n\nNote: If there are non-system VeraCrypt volumes that you need to have mounted automatically every time Windows starts, you can set it up by mounting each of them and selecting 'Favorites' > 'Add Mounted Volume to System Favorites'). System partitionen/drevet er dekrypteret med succes. \n\nVeraCrypt bindet er oprettet og klar til brug. Hvis du ønsker at oprette et andet VeraCrypt bind, klik Næste. Ellers, klik Afslut. \n\nThe hidden VeraCrypt volume has been successfully created (the hidden operating system will reside within this hidden volume).\n\nClick Next to continue. Volume Fully Encrypted Volume Fully Decrypted IMPORTANT: TO MOUNT THIS NEWLY CREATED VERACRYPT VOLUME AND TO ACCESS DATA STORED IN IT, CLICK 'Auto-Mount Devices' IN THE MAIN VERACRYPT WINDOW. After you enter the correct password (and/or supply correct keyfiles), the volume will be mounted to the drive letter you select from the list in the main VeraCrypt window (and you will be able to access the encrypted data via the selected drive letter).\n\nPLEASE REMEMBER OR WRITE DOWN THE ABOVE STEPS. YOU MUST FOLLOW THEM WHENEVER YOU WANT TO MOUNT THE VOLUME AND ACCESS DATA STORED IN IT. Alternatively, in the main VeraCrypt window, click 'Select Device', then select this partition/volume, and click 'Mount'.\n\nThe partition/volume has been successfully encrypted (it contains a fully encrypted VeraCrypt volume now) and is ready for use. The VeraCrypt volume has been successfully decrypted. The VeraCrypt volume has been successfully decrypted.\n\nPlease select a drive letter that you wish to assign to the decrypted volume and then click Finish.\n\nIMPORTANT: Until a drive letter is assigned to the decrypted volume, you will not be able to access data stored on the volume. Warning: To be able to access the decrypted data, a drive letter needs to be assigned to the decrypted volume. However, no drive letter is currently available.\n\nPlease vacate a drive letter (for example, by disconnecting a USB flash drive or external hard drive, etc.) and then click OK. VeraCrypt bindet er oprettet med succes. Bind Oprettet VIGTIGT: Bevæg musen så tilfældigt som muligt i dette vindue. Jo længere tid du bevæger den, jo bedre. Dette forbedrer signifikant den kryptografiske styrke på nøglefilen. Klik på Formater for at oprette bindet. Klik på Formater for at oprette det ydre bind. For mere information, læs venligst dokumentationen. Ydre Bind Formatering Skjult Bind Formatering Bind Formatering Adobe Reader (eller et kompatibelt værktøj) er nødvendigt for at se eller udskrive VeraCrypt Brugervejledning. Adobe Reader (freeware) kan downloades på: www.adobe.com/dk/\n\nØnsker du at se den online dokumentation istedet? Hvis du vælger denne mulighed, vil oprettelsesguiden først hjælpe dig med at oprette et normalt VeraCrypt bind og så et skjult VeraCrypt bind deri. Uerfarne brugere bør altid vælge denne mulighed. Hvis du vælger denne mulighed, vil du oprette et skjult bind i et eksisterende VeraCrypt bind. Det vil formodes at du allerede har oprettet et VeraCrypt bind der er passende som vært til det skjulte bind. Bind oprettelses tilstand Skjult Bind oprettet The hidden VeraCrypt volume has been successfully created and is ready for use. If all the instructions have been followed and if the precautions and requirements listed in the section "Security Requirements and Precautions Pertaining to Hidden Volumes" in the VeraCrypt User's Guide are followed, it should be impossible to prove that the hidden volume exists, even when the outer volume is mounted.\n\nWARNING: IF YOU DO NOT PROTECT THE HIDDEN VOLUME (FOR INFORMATION ON HOW TO DO SO, REFER TO THE SECTION "PROTECTION OF HIDDEN VOLUMES AGAINST DAMAGE" IN THE VERACRYPT USER'S GUIDE), DO NOT WRITE TO THE OUTER VOLUME. OTHERWISE, YOU MAY OVERWRITE AND DAMAGE THE HIDDEN VOLUME! You have started the hidden operating system. As you may have noticed, the hidden operating system appears to be installed on the same partition as the original operating system. However, in reality, it is installed within the partition behind it (in the hidden volume). All read and write operations are being transparently redirected from the original system partition to the hidden volume.\n\nNeither the operating system nor applications will know that data written to and read from the system partition are actually written to and read from the partition behind it (from/to a hidden volume). Any such data is encrypted and decrypted on the fly as usual (with an encryption key different from the one that will be used for the decoy operating system).\n\n\nPlease click Next to continue. Det ydre bind er blevet oprettet og tilsluttet som drev %hc:. Til dette ydre bind bør du nu kopiere nogle følsomt udseende filer som du egentlig IKKE ønsker at skjule. De vil være der for dem der eventuelt afpresser dig til at afsløre kodeordet for den første partition bag system partitionen, hvor både det ydre og skjulte bind (indeholdende det skjulte operativsystem) vil være placeret. Du vil kunne afsløre kodeordet for dette ydre bind, og eksistensen af det skjulte bind (og det skjulte operativsystem) vil fortsat være hemmeligt.\n\nVIGTIGT: Filerne du kopierer til det ydre bind bør ikke optage mere plads end %s. Ellers er der muligvis ikke nok ledig plads i det ydre bind for det skjulte bind (og du vil ikke være i stand til at fortsætte). Efter du har afsluttet din kopiering, klik Næste (afbryd ikke bindet). Ydre Bind er oprettet med succes og tilsluttet som drev %hc:. Til dette bind bør du nu kopiere nogle filer over der ser følsomme ud, men som du egentlig ikke ønsker at skjule. Filerne vil så være der hvis nogen aftvinger dig dit kodeord. Du afslører da kun kodeordet for det ydre bind, ikke for det skjulte. De filer du virkelig bekymrer dig om vil være i det skjulte bind, som bliver oprettet senere. Når du er færdig med at kopiere, klik Næste. Afslut ikke bindet.\n\nBemærk: Når du har klikket på Næste, vil klynge bitmap til det ydre bind blive skannet for at afgøre størrelsen af uafbrudt fri plads hvis slutning ligger udenfor slutningen af bindet. Dette område vil indeholde det skjulte bind, så det vil begrænse den maksimale størrelse. Klynge bitmap skanning sikrer at ingen data på det ydre bind overskrives af det skjulte bind. Ydre bind indeholder \n\nI de næste trin indstiller du valgmuligheder for det ydre bind (hvori det skjulte bind vil blive oprettet senere). \n\nI de næste trin, vil du oprette et såkaldt ydre VeraCrypt bind indeni den første partition bag system partition (som blev forklaret i en af de tidligere trin). Ydre bind In the following steps, you will set the options and password for the hidden volume, which will contain the hidden operating system.\n\nRemark: The cluster bitmap of the outer volume has been scanned in order to determine the size of uninterrupted area of free space whose end is aligned with the end of the outer volume. This area will accommodate the hidden volume, so it limits its maximum possible size. The maximum possible size of the hidden volume has been determined and confirmed to be greater than the size of the system partition (which is required, because the entire content of the system partition will need to be copied to the hidden volume). This ensures that no data currently stored on the outer volume will be overwritten by data written to the area of the hidden volume. IMPORTANT: Please remember the algorithms that you select in this step. You will have to select the same algorithms for the decoy system. Otherwise, the hidden system will be inaccessible! (The decoy system must be encrypted with the same encryption algorithm as the hidden system.)\n\nNote: The reason is that the decoy system and the hidden system will share a single boot loader, which supports only a single algorithm, selected by the user (for each algorithm, there is a special version of the VeraCrypt Boot Loader). \n\nBindets cluster bitmap er blevet skannet og den maksimalt mulige størrelse på det skjulte bind er blevet afgjort. I de næste trin vil du vælge indstilling, størrelse, og kodeord for det skjulte bind. Skjult bind Det skjulte bind er nu beskyttet mod beskadigelse indtil det ydre bind bliver afbrudt.\n\nADVARSEL: Hvis nogen data forsøges gemt i området for det skjulte bind, vil VeraCrypt igangsætte skrive-beskyttelse af hele bindet (både det ydre og den skjulte del) indtil det bliver afbrudt. Dette kan medføre filsystem korruption på det ydre bind, hvilket (hvis gentaget) uforsætligt kan have indflydelse på den plausible benægtelse af det skjulte bind. Derfor bør du gøre en effektiv indsats for at undgå at gemme i området for det skjulte bind. Alle data gemt i området for det skjulte bind vil ikke blive gemt og vil være mistet. Windows kan rapportere dette som en skrivefejl ("Fejl forsinket skrivning" eller "Parameteren er ukorrekt"). Ethvert skjult bind indeni det nu tilsluttede bind er nu beskyttet imod beskadigelse indtil det bliver afbrudt.\n\nADVARSEL: Hvis der forsøges at gemme nogen data i området for beskyttede skjulte bind, vil VeraCrypt igangsætte skrive-beskyttelse af hele bindet (både det ydre og den skjulte del) indtil det bliver afbrudt. Dette kan medføre filsystem korruption på det ydre bind, hvilket (hvis gentaget) uforsætligt kan have indflydelse på den plausible benægtelse af det skjulte bind. Derfor bør du gøre en effektiv indsats for at undgå at gemme i området for det skjulte bind. Alle data gemt i området for det skjulte bind vil ikke blive gemt og vil være mistet. Windows kan rapportere dette som en skrivefejl ("Fejl forsinket skrivning" eller "Parameteren er ukorrekt"). ADVARSEL: Der blev forsøgt at gemme data i området for det skjulte bind tilsluttet som %c:! VeraCrypt forhindrede disse data i at blive gemt for at beskytte det skjulte bind. Dette kan have medført filsystem korruption i det ydre bind og Windows kan have rapporteret en skrivefejl ("Fejl forsinket skrivning" eller "Parameteren er ukorrekt"). Hele bindet (både den ydre og skjulte del) vil blive skrive-beskyttet indtil det bliver afbrudt. Hvis dette ikke er første gang VeraCrypt har beskyttet data i at blive gemt i området for det skjulte bind, kan det uforsætligt have indflydelse på den plausible benægtelse af det skjulte bind (pga. mulig usædvanligt modsigende uoverenstemmelse i det ydre filsystem). Derfor bør du overveje at oprette et nyt VeraCrypt bind (med ekspresformatering slået fra) og flytte filerne fra dette bind til det nye bind; dette bind bør slettes sikkert (både det ydre og den skjulte del). Vi anbefaler kraftigt at du genstarter operativsystemet nu. You have indicated intent to store files larger than 4 GB on the volume. This requires the volume to be formatted as NTFS, which, however, will not be possible. Please note that when a hidden operating system is running, non-hidden VeraCrypt volumes cannot be formatted as NTFS. The reason is that the volume would need to be temporarily mounted without write protection in order to allow the operating system to format it as NTFS (whereas formatting as FAT is performed by VeraCrypt, not by the operating system, and without mounting the volume). For further technical details, see below. You can create a non-hidden NTFS volume from within the decoy operating system. For security reasons, when a hidden operating system is running, hidden volumes can be created only in the 'direct' mode (because outer volumes must always be mounted as read-only). To create a hidden volume securely, follow these steps:\n\n1) Boot the decoy system.\n\n2) Create a normal VeraCrypt volume and, to this volume, copy some sensitive-looking files that you actually do NOT want to hide (the volume will become the outer volume).\n\n3) Boot the hidden system and start the VeraCrypt Volume Creation Wizard. If the volume is file-hosted, move it to the system partition or to another hidden volume (otherwise, the newly created hidden volume would be mounted as read-only and could not be formatted). Follow the instructions in the wizard so as to select the 'direct' hidden volume creation mode.\n\n4) In the wizard, select the volume you created in step 2 and then follow the instructions to create a hidden volume within it. For security reasons, when a hidden operating system is running, local unencrypted filesystems and non-hidden VeraCrypt volumes are mounted as read-only (no data can be written to such filesystems or VeraCrypt volumes).\n\nData is allowed to be written to any filesystem that resides within a hidden VeraCrypt volume (provided that the hidden volume is not located in a container stored on an unencrypted filesystem or on any other read-only filesystem). There are three main reasons why such countermeasures have been implemented:\n\n- It enables the creation of a secure platform for mounting of hidden VeraCrypt volumes. Note that we officially recommend that hidden volumes are mounted only when a hidden operating system is running. (For more information, see the subsection 'Security Requirements and Precautions Pertaining to Hidden Volumes' in the documentation.)\n\n- In some cases, it is possible to determine that, at a certain time, a particular filesystem was not mounted under (or that a particular file on the filesystem was not saved or accessed from within) a particular instance of an operating system (e.g. by analyzing and comparing filesystem journals, file timestamps, application logs, error logs, etc). This might indicate that a hidden operating system is installed on the computer. The countermeasures prevent these issues.\n\n- It prevents data corruption and allows safe hibernation. When Windows resumes from hibernation, it assumes that all mounted filesystems are in the same state as when the system entered hibernation. VeraCrypt ensures this by write-protecting any filesystem accessible both from within the decoy and hidden systems. Without such protection, the filesystem could become corrupted when mounted by one system while the other system is hibernated. Bemærk: Hvis du har behov for at overføre filer sikkert fra aflednings systemet til det skjulte system, følg disse trin: 1) Start aflednings systemet. 2) Gem filerne til et ukrypteret bind eller til et normalt/ydre VeraCrypt bind. 3) Start det skjulte system. 4) Hvis du har gemt filerne til et VeraCrypt bind, tilslut det (det vil automatisk blive tilsluttet som læs-kun). 5) Kopier filerne til den skjulte system partition eller til et andet skjult bind. Din computer skal genstartes.\n\nØnsker du at genstarte den nu? En fejl opstod under læsning af system krypterings status. No password specified in the command line. The volume can't be created. No volume size specified in the command line. The volume can't be created. The volume file size specified in the command line is incompatible with selected NTFS filesystem. The volume file size specified in the command line is incompatible with selected FAT32 filesystem. The filesystem on the target drive doesn't support creating sparse files which is required for dynamic volumes. Only container files can be created through the command line. The container file size specified in the command line is greater than the available disk free space. Volume can't be created. The volume size specified in the command line is too small. The volume can't be created. The volume size specified in the command line is too big. The volume can't be created. Kan ikke initialisere applikations komponenter for system kryptering. Kunne ikke initialisere tilfældigheds nummergenerator! Windows Crypto API failed!\n\n\n(If you report a bug in connection with this, please include the following technical information in the bug report:\n%hs, Last Error = 0x%.8X) Kunne ikke initialisere applikationen. Fejl i registrering af Dialog class. Error: Failed to load the Rich Edit system library. VeraCrypt Bind Oprettelsesguide Den maksimale skjulte bind størrelse for dette bind er %.2f bytes. Den maksimale skjulte bind størrelse for dette bind er %.2f KB. Den maksimale skjulte bind størrelse for dette bind er %.2f MB. Maximum possible hidden volume size for this volume is %.2f GB. Maximum possible hidden volume size for this volume is %.2f TB. Bind kodeord/nøglefiler kan ikke ændres mens bindet er tilsluttet. Afbryd venligst bindet først. Etiketnøgle oprindelses algoritmen kan ikke ændres mens bindet er tilsluttet. Afbryd venligst bindet først. &Tilslut En nyere version af VeraCrypt kræves for at tilslutte dette bind. Fejl: Bind Oprettelsesguiden er ikke fundet.\n\nKontroller venligst at 'VeraCrypt Format.exe' er i mappen hvorfra 'VeraCrypt.exe' blev startet. Hvis den ikke er, geninstaller VeraCrypt, eller find 'VeraCrypt Format.exe' på din harddisk og start den. Error: Volume Expander not found.\n\nPlease make sure that the file 'VeraCryptExpander.exe' is in the folder from which 'VeraCrypt.exe' was launched. If it is not, please reinstall VeraCrypt, or locate 'VeraCryptExpander.exe' on your disk and run it. &Næste > &Afslut &Installer U&dpak Ude i stand til at tilslutte VeraCrypt enhedsdriver. VeraCrypt vil ikke virke hvis enhedsdriveren ikke kører.\n\nBemærk venligst at, pga. et Windows problem, kan det være nødvendigt at logge af eller genstarte systemet førend enhedsdriveren kan lokalisere. Fejl opstået under indlæsning/forberedelse af skrifttyper. Drev bogstavet blev ikke fundet eller der blev ikke angivet noget drev bogstav. Error: Cannot assign drive letter.\n\nUntil a drive letter is assigned to the decrypted volume, you will not be able to access data stored on the volume.\n\nRetry? Drev bogstav er ikke tilgængeligt. Ingen fil valgt! Ingen drev bogstaver tilgængelige. Ingen ledige drev bogstaver til det ydre bind! Oprettelse af bind kan ikke fortsætte. Kunne ikke fastsætte din version af operativsystem eller du anvender et usupporteret operativsystem. Ingen sti valgt! Ikke nok ledig plads til det skjulte bind! Oprettelse af bind kan ikke fortsætte. Fejl: Filerne du har kopieret til det ydre bind optager for meget plads. Derfor er der ikke nok plads på det ydre bind til det skjulte bind.\n\nBemærk at det skjulte bind skal være ligeså stort som system partitionen (den partition hvor det nuværende aktive operativsystem er installeret). Grunden er at det skjulte operativsystem er nødt til at blive oprettet ved at kopiere indholdet af system partitionen til det skjulte bind.\n\n\nProcessen ved oprettelse af det skjulte operativsystem kan ikke fortsætte. Driveren kan ikke afbryde bindet. Enkelte filer i bindet er muligvis stadig åbne. Bindet kan ikke låses. Der er stadig åbne filer i bindet. Derfor kan det ikke afbrydes. VeraCrypt cannot lock the volume because it is in use by the system or applications (there may be open files on the volume).\n\nDo you want to force dismount on the volume? Vælg et VeraCrypt Bind Vælg sti og filnavn Select PKCS #11 Library Ikke mere hukommelse IMPORTANT: We strongly recommend that inexperienced users create a VeraCrypt file container on the selected device/partition, instead of attempting to encrypt the entire device/partition.\n\nWhen you create a VeraCrypt file container (as opposed to encrypting a device or partition) there is, for example, no risk of destroying a large number of files. Note that a VeraCrypt file container (even though it contains a virtual encrypted disk) is actually just like any normal file. For more information, see the chapter Beginner's Tutorial in the VeraCrypt User Guide.\n\nAre you sure you want to encrypt the entire device/partition? ADVARSEL: Filen '%s' eksisterer allerede!\n\nVIGTIGT: VERACRYPT KRYPTERER IKKE FILEN, MEN VIL SLETTE DEN. Er du sikker på du vil slette filen og erstatte den med en ny VeraCrypt beholder? ADVARSEL: ALLE NUVÆRENDE FILER GEMT PÅ DET VALGTE %s '%s'%s VIL BLIVE SLETTET OG TABT (DE BLIVER IKKE KRYPTERET)!\n\nEr du sikker på du ønsker at fortsætte med formatering? WARNING: You will not be able to mount the volume or access any files stored on it until it has been fully encrypted.\n\nAre you sure you want to start encrypting the selected %s '%s'%s? WARNING: You will not be able to mount the volume or access any files stored on it until it has been fully decrypted.\n\nAre you sure you want to start decrypting the selected %s '%s'%s? WARNING: Please note that if power supply is suddenly interrupted while encrypting/decrypting existing data in place, or when the operating system crashes due to a software error or hardware malfunction while VeraCrypt is encrypting/decrypting existing data in place, portions of the data will be corrupted or lost. Therefore, before you start encrypting/decrypting, please make sure that you have backup copies of the files you want to encrypt/decrypt.\n\nDo you have such a backup? FORSIGTIG: ALLE NUVÆRENDE GEMTE FILER PÅ PARTITIONEN '%s'%s (F.EKS. PÅ DEN FØRSTE PARTITION BAG SYSTEM PARTITIONEN) VIL BLIVE SLETTET OG TABT (DE VIL IKKE BLIVE KRYPTERET)!\n\nEr du sikker på du ønsker at fortsætte med formattering? WARNING: THE SELECTED PARTITION CONTAINS A LARGE AMOUNT OF DATA! Any files stored on the partition will be erased and lost (they will NOT be encrypted)! Erase any files stored on the partition by creating a VeraCrypt volume within it Kodeord PIM Ændre etiketnøgle oprindelses algoritme Tilføj/Fjern nøglefiler til/fra Bind Fjern alle nøglefiler fra Bind Password, PIM and/or keyfile(s) successfully changed.\n\nIMPORTANT: Please make sure you have read the section 'Changing Passwords and Keyfiles' in the chapter 'Security Requirements and Precautions' in the VeraCrypt User Guide. This volume is registered as a System Favorite and its PIM was changed.\nDo you want VeraCrypt to automatically update the System Favorite configuration (administrator privileges required)?\n\nPlease note that if you answer no, you'll have to update the System Favorite manually. VIGTIGT: Hvis du ikke har destrueret din VeraCrypt Nødhjælps Disk, vil dit system partition/drev stadig kunne dekrypteres ved brug af det gamle kodeord (ved at boote på VeraCrypt Nødhjælps Disk og indtaste det gamle kodeord). Du bør oprette en ny VeraCrypt Nødhjælps Disk og så destruere den gamle.\n\nØnsker du at oprette en ny VeraCrypt Nødhjælps Disk? Bemærk at din VeraCrypt Nødhjælps Disk stadig bruger den tidligere algoritme. Hvis du fornemmer den tidligere algoritme er usikker, bør du oprette en ny VeraCrypt Nødhjælps Disk og så destruere den gamle.\n\nØnsker du at oprette en ny VeraCrypt Nødhjælps Disk? Any kind of file (for example, .mp3, .jpg, .zip, .avi) may be used as a VeraCrypt keyfile. Note that VeraCrypt never modifies the keyfile contents. You can select more than one keyfile (the order does not matter). If you add a folder, all non-hidden files found in it will be used as keyfiles. Click 'Add Token Files' to select keyfiles stored on security tokens or smart cards (or to import keyfiles to security tokens or smart cards). Nøglefil(er) tilføjet/fjernet med succes. Keyfile exported. Etiketnøgle oprindelses algoritme ændret med success. Please enter the password and/or keyfile(s) for the non-system volume where you want to resume the process of in-place encryption.\n\n\nRemark: After you click Next, VeraCrypt will attempt to find all non-system volumes where the process of encryption has been interrupted and where the VeraCrypt volume header can be decrypted using the supplied password and/or keyfile(s). If more than one such volume is found, you will need to select one of them in the next step. Please select one of the listed volumes. The list contains every accessible non-system volume where the process of encryption has been interrupted and whose header could be decrypted using the supplied password and/or keyfile(s). Please enter the password and/or keyfile(s) for the non-system VeraCrypt volume that you want to decrypt. Det er meget vigtigt at du vælger et godt kodeord. Du bør undgå at vælge et der kun indeholder et enkelt ord der kan findes i en ordbog (eller en kombination af 2, 3 eller 4 af sådanne ord). Det bør ikke indeholde nogle navne eller fødselsdatoer. Det skal ikke være nemt at gætte. Et godt kodeord er en tilfældig kombination af store og små bogstaver, tal, og specielle karakterer, så som @ ^ = $ * + osv. Vi anbefaler at du vælger et kodeord der består af mere end 20 karakterer (jo længere, jo bedre). Det maksimalt mulige længde er 128 karakterer. Vælg venligst et kodeord til det skjulte bind. Vælg venligst et kodeord til det skjulte operativsystem (f.eks. til det skjulte bind). IMPORTANT: The password that you choose for the hidden operating system in this step must be substantially different from the other two passwords (i.e. from the password for the outer volume and from the password for the decoy operating system). Indtast venligst kodeordet til det bind hvori du ønsker at oprette et skjult bind.\n\nEfter du har klikket Næste, vil VeraCrypt forsøge at tilslutte bindet. Så snart at bindet er tilsluttet, vil dets cluster bitmap bliver skannet for at afgøre størrelsen af det ubrudte område af ledig plads (hvis der er noget) hvis slutning ligger lige med slutningen af bindet. Dette område vil indeholde det skjulte bind og vil derfor begrænse dets maksimale mulige størrelse. Cluster map skanning er nødvendigt for at sikre at ingen data i det ydre bind, vil blive overskrevet af det skjulte bind. \nVælg venligst et kodeord til det ydre bind. Dette vil være det kodeord som du vil kunne afsløre i det tilfælde du bliver spurgt eller tvunget til at afsløre det.\n\nVIGTIGT: Kodeordet du vælger skal være mærkbart forskelligt fra det du vælger til det skjulte bind.\n\nBemærk: Den maksimalt mulige kodeords længde er på 128 karakterer. Vælg venligst et kodeord til det ydre bind. Dette vil være det kodeord som du vil kunne afsløre i det tilfælde du bliver spurgt eller tvunget til at afsløre det for den første partition bag system partitionen, hvor både det ydre bind og det skjulte bind (indeholdende det skjulte operativsystem) vil være placeret. Eksistensen af det skjulte bind (og det skjulte operativsystem) vil forblive hemmeligt. Bemærk at kodeordet ikke er til aflednings systemet.\n\nVIGTIGT: Kodeordet du vælger skal være mærkbart forskelligt fra det du vælger til det skjulte bind (dvs. til det skjulte operativsystem). Ydre Bind kodeord Skjult Bind kodeord Kodeord til skjult operativsystem ADVARSEL: Korte kodeord er lette at bryde ved brug af magtfulde teknikker!\n\nVi anbefaler et kodeord over 20 karakterer. Er du sikker på du vil bruge et kort kodeord? Bind kodeord Ukorrekt kodeord eller ikke et VeraCrypt bind. Ukorrekt nøglefil(er) og/eller kodeord eller ikke et VeraCrypt bind. Forkert tilslutningstilstand, ukorrekt kodeord, eller ikke et VeraCrypt bind. Forkert tilslutningstilstand, ukorrekt nøglefil(er) og/eller kodeord, eller ikke et VeraCrypt bind. Ukorrekt kodeord eller intet VeraCrypt bind fundet. Ukorrekt nøglefil(er)/kodeord eller intet VeraCrypt bind fundet. \n\nAdvarsel: Caps Lock er slået til. Dette kan medføre at kodeordet indtastes ukorrekt. Remember Number to Mount Volume Outer Volume PIM Hidden Volume PIM PIM for Hidden Operating System PIM (Personal Iterations Multiplier) is a value that controls the number of iterations used by the header key derivation as follows:\n Iterations = 15000 + (PIM x 1000).\n\nWhen left empty or set to 0, VeraCrypt will use a default value (485) that ensures a high security.\n\nWhen the password is less than 20 characters, PIM can't be smaller than 485 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, PIM can be set to any value.\n\nA PIM value larger than 485 will lead to slower mount. A small PIM value (less than 485) will lead to a quicker mount but it can reduce security if the password is not strong enough. PIM (Personal Iterations Multiplier) is a value that controls the number of iterations used by the header key derivation as follows:\n Iterations = PIM x 2048.\n\nWhen left empty or set to 0, VeraCrypt will use a default value that ensures a high security.\n\nWhen the password is less than 20 characters, PIM can't be smaller than 98 in order to maintain a minimal security level.\nWhen the password is 20 characters or more, PIM can be set to any value.\n\nA PIM value larger than 98 will lead to slower boot. A small PIM value (less than 98) will lead to a quicker boot but it can reduce security if the password is not strong enough. Remember Number to Boot System You have chosen a PIM value that is larger than VeraCrypt default value.\nPlease note that this will lead to much slower mount/boot. You have chosen a Personal Iterations Multiplier (PIM) that is smaller than the default VeraCrypt value. Please note that if your password is not strong enough, this could lead to a weaker security.\n\nDo you confirm that you are using a strong password? Personal Iterations Multiplier (PIM) maximum value for system encryption is 65535. Volume PIM \n\nWARNING: Hidden file(s) have been found in a keyfile search path. Such hidden files cannot be used as keyfiles. If you need to use them as keyfiles, remove their 'Hidden' attribute (right-click each of them, select 'Properties', uncheck 'Hidden' and click OK). Note: Hidden files are visible only if the corresponding option is enabled (Computer > Organize > 'Folder and search options' > View). If you are attempting to protect a hidden volume containing a hidden system, please make sure you are using the standard US keyboard layout when typing the password for the hidden volume. This is required due to the fact that the password needs to be typed in the pre-boot environment (before Windows starts) where non-US Windows keyboard layouts are not available. VeraCrypt has not found any volume where non-system encryption has been interrupted and where the volume header can be decrypted using the supplied password and/or keyfile(s).\n\nPlease make sure the password and/or keyfile(s) are correct and that the partition/volume is not being used by the system or applications (including antivirus software). The selected partition/device is already fully encrypted.\nHeader Flags = 0x%.8X The selected partition/device is not using in-place encryption.\nHeader Flags = 0x%.8X \n\nBemærk: Hvis du forsøger at tilslutte en partition placeret på et krypteret system drev uden før-boot godkendelse eller tilslutte en krypteret system partition fra et operativsystem der ikke kører, kan du gøre dette ved at vælge 'System' > 'Tilslut uden før-Boot Godkendelse'. I denne tilstand kan du ikke tilslutte en partition placeret på et drev hvis portion er indenfor nøglens rækkevidde af aktiv system kryptering.\n\nFør du kan tilslutte denne partition i denne tilstand, er du nødt til enten at boote et operativsystem installeret på et andet drev (krypteret eller ukrypteret) eller boote på et ukrypteret operativsystem. VeraCrypt cannot decrypt an individual partition on an entirely encrypted system drive (you can decrypt only the entire system drive). Warning: As the drive contains the VeraCrypt Boot Loader, it may be an entirely encrypted system drive. If it is, please note that VeraCrypt cannot decrypt an individual partition on an entirely encrypted system drive (you can decrypt only the entire system drive). If that is the case, you will be able to continue now but you will receive the 'Incorrect password' error message later. < &Tilbage Ude af stand til at vise de rå enheder der er installeret på dit system! Bindet '%s' eksisterer, og er læs-kun. Er du sikker på du vil erstatte det? Vælg destinationsmappe Vælg nøglefil Vælg en nøglefil søgesti. ADVARSEL: Bemærk at kun stien vil blive husket, ikke filnavne! Select a directory where to store the keyfiles. The current container file was selected as a keyfile. It will be skipped. Designet af Ross Anderson, Eli Biham, og Lars Knudsen. Udgivet i 1998. 256-bit nøgle, 128-bit blok. Driftstilstand er XTS. Serpent var en af AES finalisterne. Please specify the size of the container you want to create.\n\nIf you create a dynamic (sparse-file) container, this parameter will specify its maximum possible size.\n\nNote that the minimum possible size of a FAT volume is 292 KB. The minimum possible size of an NTFS volume is 3792 KB. Please specify the size of the outer volume to be created (you will first create the outer volume and then a hidden volume within it). The minimum possible size of a volume within which a hidden volume is intended to be created is 340 KB. Please specify the size of the hidden volume to create. The minimum possible size of a hidden volume is 40 KB (or 3664 KB if it is formatted as NTFS). The maximum possible size you can specify for the hidden volume is displayed above. Ydre bind størrelse Skjult bind størrelse Please verify that the size of the selected device/partition shown above is correct and click Next. Det ydre bind og det skjulte bind (indeholdende det skjulte operativsystem) vil placeres indeni partition ovenfor. Det bør være den første partition bag system partitionen.\n\nKontroller venligst at størrelsen på partitionen og dets nummer vist ovenfor er korrekte, og hvis de er, klik på Næste. \n\nNote that the minimum possible size of a volume within which a hidden volume is intended to be created is 340 KB. Bind Størrelse Dynamisk ADVARSEL: SELV-TEST FEJLET! Selv-test af alle algoritmer gennemført Data enheds nummeret som du har angivet er for langt eller kort. Den sekundære nøgle som du har angivet er for lang eller kort. Testen ciffertekst du har angivet er for lang eller kort. Testen nøgle du har angivet er for lang eller kort. Testen ren tekst du har angivet er for lang eller kort. To cifre i kaskade funktion i XTS tilstand. Hver blok bliver først krypteret med %s (%d-bit nøgle) og så med %s (%d-bit nøgle). Hvert ciffer bruger dets egen nøgle. Alle nøgler er indbyrdes uafhængige. Tre cifre i kaskade funktion i XTS tilstand. Hver blok bliver først krypteret med %s (%d-bit nøgle), og så med %s (%d-bit nøgle), og tilsidst med %s (%d-bit nøgle). Hvert ciffer bruger dets egen nøgle. Alle nøgler er indbyrdes uafhængige. Note that, depending on the operating system configuration, these auto-run and auto-mount features may work only when the traveler disk files are created on a non-writable CD/DVD-like medium. Also note that this is not a bug in VeraCrypt (it is a limitation of Windows). VeraCrypt traveler disk has been successfully created.\n\nNote that you need administrator privileges to run VeraCrypt in portable mode. Also note that, after examining the registry file, it may be possible to tell that VeraCrypt was run on a Windows system even if it is run in portable mode. VeraCrypt Rejse Disk Designet af Bruce Schneier, John Kelsey, Doug Whiting, David Wagner, Chris Hall, og Niels Ferguson. Udgivet i 1998. 256-bit nøgle, 128-bit blok. Drift tilstand er XTS. Twofish var en af AES finalisterne. Mere information på %s Ukendt An unspecified or unknown error occurred (%d). Nogle bind indeholder filer eller mapper som bliver brugt af andre programmer eller systemet.\n\nGennemtving afbrydelse? &Afbryd Afbrydelse er fejlet! Bindet indeholder filer eller mapper som bliver brugt af andre programmer eller systemet.\n\nGennemtving afbrydelse? No volume is mounted to the specified drive letter. Bindet du prøver at tilslutte er allerede tilsluttet. En fejl opstod under forsøget på at tilslutte bindet. Fejl i søgning af placering indenfor bind. Fejl: Ukorrekt bind størrelse. WARNING: You should use Quick Format only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Format? Dynamic container is a pre-allocated NTFS sparse file whose physical size (actual disk space used) grows as new data is added to it.\n\nWARNING: Performance of sparse-file-hosted volumes is significantly worse than performance of regular volumes. Sparse-file-hosted volumes are also less secure, because it is possible to tell which volume sectors are unused. Furthermore, sparse-file-hosted volumes cannot provide plausible deniability (host a hidden volume). Also note that if data is written to a sparse file container when there is not enough free space in the host file system, the encrypted file system may get corrupted.\n\nAre you sure you want to create a sparse-file-hosted volume? Note that the size of the dynamic container reported by Windows and by VeraCrypt will always be equal to its maximum size. To find out current physical size of the container (actual disk space it uses), right-click the container file (in a Windows Explorer window, not in VeraCrypt), then select 'Properties' and see the 'Size on disk' value.\n\nAlso note that if you move a dynamic container to another volume or drive, the physical size of the container will be extended to the maximum. (You can prevent that by creating a new dynamic container in the destination location, mounting it and then moving the files from the old container to the new one.) Password cache wiped Passwords (and/or processed keyfile contents) stored in the VeraCrypt driver cache have been wiped. VeraCrypt kan ikke ændre kodeord for et fremmed bind. Vælg venligst et ledigt drev bogstav fra listen. Vælg venligst et tilsluttet bind i drev bogstav listen. Warning: Two different volumes/devices are currently selected (the first is selected in the drive letter list and the second is selected in the input field below the drive letter list).\n\nPlease confirm your choice: Fejl: Kan ikke oprette autorun.inf Fejl under bearbejdning af nøglefil! Fejl under bearbejdning af nøglefil sti! The keyfile path contains no files.\n\nPlease note that folders (and files they contain) found in keyfile search paths are ignored. VeraCrypt supporterer ikke dette operativsystem. Error: VeraCrypt supports only stable versions of this operating system (beta/RC versions are not supported). Fejl: Kan ikke tildele hukommelse. Fejl: Kunne modtage værdien af ydelsestæller. Fejl: Forkert bind format. Fejl: Du angav et kodeord til et skjult bind (ikke til et normalt bind). For security reasons, a hidden volume cannot be created within a VeraCrypt volume containing a filesystem that has been encrypted in place (because the free space on the volume has not been filled with random data). VeraCrypt - Juridiske Bemærkninger Alle Filer VeraCrypt Bind Library Modules NTFS formatering kan ikke fortsætte. Kan ikke tilslutte bind. Kan ikke afbryde bind. Windows fejlede under formatering af bindet som NTFS.\n\nVælg venligst en anden type filsystem (hvis muligt) og prøv igen. Alternativt kan du lade bindet være uformateret (Vælg 'Ingen' som filsystem), afbryd denne hjælp, tilslut bindet, og brug da enten et system eller 3-parts værktøj til at formatere bindet (bindet vil forblive krypteret). Windows fejlede under formatering af bindet som NTFS.\n\nØnsker du at formatere bindet som FAT istedet? Standard partition PARTITION Enhed device ENHED Bind volume VOLUME Etiket Den valgte klynge størrelse er for lille til denne størrelse bind. En større klynge størrelse vil blive brugt istedet. Fejl: Kan ikke hente bind størrelsen!\n\nSørg for at det valgte bind ikke anvendes af systemet eller et andet program. Hidden volumes must not be created within dynamic (sparse file) containers. To achieve plausible deniability, the hidden volume needs to be created within a non-dynamic container. VeraCrypt Bind Oprettelsesguide kan kun oprette et skjult bind i FAT eller NTFS bind. I Windows 2000, kan VeraCrypt Bind Oprettelsesguide kun oprette et skjult bind i FAT bind. Bemærk: FAT fil systemet er mere passende for ydre bind end NTFS fil systemet (for eksempel, den maksimalt mulige størrelse på et skjult bind ville meget muligt have været betydeligt større hvis det ydre bind havde været formatteret som FAT). Bemærk at FAT fil systemet er mere passende for ydre bind end NTFS fil systemet. For eksempel, den maksimalt mulige størrelse på det skjulte bind vil meget muligt være betydeligt større hvis det ydre bind bliver formatteret som FAT (grunden er at NTFS fil systemet altid gemmer interne data nøjagtigt i midten af bindet og, derfor kan det skjulte bind kun være i den anden halvdel af det ydre bind).\n\nEr du sikker på du ønsker at formattere det ydre bind som NTFS? Ønsker du at formattere bindet som FAT istedet? Note: This volume cannot be formatted as FAT, because it exceeds the maximum volume size supported by the FAT32 filesystem for the applicable sector size (2 TB for 512-byte sectors and 16 TB for 4096-byte sectors). Fejl: Partitionen for det skjulte operativsystem (dvs. den første partition bag system partitionen) skal være mindst 5% større end system partitionen (system partitionen er den hvor det nuværende kørende operativsystem er installeret). Fejl: Partitionen for det skjulte operativsystem (dvs. den første partition bag system partitionen) skal være mindst 110% (2.1 gange) større end system partitionen (system partitionen er den hvor det nuværende kørende operativsystem er installeret). Årsagen er den at et NTFS fil system altid gemmer interne data nøjagtigt i midten af bindet og, derfor kan det skjulte bind (som skal indeholde en klon af system partitionen) kun placeres i den anden halvdel af bindet. Fejl: Hvis det ydre bind er formatteret som NTFS, skal det mindst være 110% (2.1 gange) større end system partitionen. Årsagen er den at et NTFS fil system altid gemmer interne data nøjagtigt i midten af bindet og, derfor kan det skjulte bind (som skal indeholde en klon af system partitionen) kun placeres i den anden halvdel af bindet.\n\nBemærk: Det ydre bind skal være placeret indeni samme partition som det skjulte operativsystem (dvs. indeni den første partition bag system partitionen). Fejl: Der er ingen partition bag system partitionen.\n\nBemærk at før du kan oprette et skjult operativsystem, skal du oprette en partition til det på system drevet. Det skal være den første partition bag system partitionen og den skal være mindst 5% større end system partitionen (system partitionen er den hvor det nuværende kørende operativsystem er installeret). Derimod, hvis det ydre bind (ikke at forveksle med system partitionen) er formatteret som NTFS, skal partitionen for det skjulte operativsystem være mindst 110% (2.1 gange) større end system partitionen (Årsagen er den at et NTFS fil system altid gemmer interne data nøjagtigt i midten af bindet og, derfor kan det skjulte bind (som skal indeholde en klon af system partitionen) kun placeres i den anden halvdel af partitionen. Bemærk: Det er ikke praktisk (og derfor heller ikke supporteret) at installere operativsystemer i to VeraCrypt bind der er integreret indeni en enkelt partition, fordi brug af det ydre operativsystem ville ofte kræve at data skulle skrives til området med det skjulte operativsystem (og hvis sådanne skrive opgaver blev forhindret ved brug af skjult bind beskyttelses funktionen, ville det uundgåeligt medføre system nedbrud, dvs. 'Blå Skærm' fejl). For information om hvordan man opretter og administrerer partitioner, læs venligst dokumentationen som fulgte med dit operativsystem eller kontakt din computer forhandlers tekniske support for yderligere hjælp. Fejl: Det nuværende kørende operativsystem er ikke installeret på boot partitionen (første Aktive partition). Dette er ikke supporteret. You indicated that you intend to store files larger than 4 GB in this VeraCrypt volume. However, you chose the FAT file system, on which files larger than 4 GB cannot be stored.\n\nAre you sure you want to format the volume as FAT? Error: VeraCrypt does not support in-place decryption of legacy non-system volumes created by VeraCrypt 1.0b or earlier.\n\nNote: You can still decrypt files stored on the volume by copying/moving them to any unencrypted volume. Error: VeraCrypt cannot in-place decrypt a hidden VeraCrypt volume.\n\nNote: You can still decrypt files stored on the volume by copying/moving them to any unencrypted volume. Warning: Note that VeraCrypt cannot in-place decrypt a volume that contains a hidden VeraCrypt volume (the hidden volume would be overwritten with pseudorandom data).\n\nPlease confirm that the volume you are about to decrypt contains no hidden volume.\n\nNote: If the volume contains a hidden volume but you do not mind losing the hidden volume, you can select Proceed (the outer volume will be safely decrypted). The volume does not contain any hidden volume. Proceed. The volume contains a hidden volume. Cancel. Fejl: Har ikke adgang til bindet!\n\nSørg for at det valgte bind eksisterer, at det ikke er tilsluttet eller bliver brugt af systemet eller andre programmer, at du har læse/skrive rettighed til bindet, og at det ikke er skrivebeskyttet. Error: Cannot obtain volume properties. Error: Cannot access the volume and/or obtain information about the volume.\n\nMake sure that the selected volume exists, that it is not being used by the system or applications, that you have read/write permission for the volume, and that it is not write-protected. Error: Cannot access the volume and/or obtain information about the volume. Make sure that the selected volume exists, that it is not being used by the system or applications, that you have read/write permission for the volume, and that it is not write-protected.\n\nIf the problem persists, it might help to follow the below steps. An error prevented VeraCrypt from encrypting the partition. Please try fixing any previously reported problems and then try again. If the problems persist, it might help to follow the below steps. An error prevented VeraCrypt from resuming the process of encryption of the partition.\n\nPlease try fixing any previously reported problems and then try resuming the process again. Note that the volume cannot be mounted until it has been fully encrypted. An error prevented VeraCrypt from decrypting the volume. Please try fixing any previously reported problems and then try again if possible. Fejl: Kan ikke afbryde det ydre bind!\n\nBindet kan ikke afbrydes hvis det indeholder filer eller mapper der bliver brugt af et program eller systemet.\n\nLuk venligst alle programmer der måtte bruge filer eller mapper på bindet og klik på Prøv igen. Fejl: Kan ikke finde information om det ydre bind! Oprettelse af bind kan ikke fortsætte. Fejl: Har ikke adgang til det ydre bind! Oprettelse af bind kan ikke fortsætte. Fejl: Kan ikke tilslutte det ydre bind! Oprettelse af bind kan ikke fortsætte. Fejl: Kan ikke hente bitmap! Oprettelse af bind kan ikke fortsætte. Alfabetisk/Kategoriseret Gennemsnits hastighed (Aftagende) Algoritme Kryptering Dekryptering Gennemsnit Drev Størrelse Krypterings Algoritme Krypterings Algoritme Type Værdi Egenskaber Placering bytes Skjult Ydre Normal System Skjult (system) Læs-kun System drev System drev (krypterer - %.2f%% færdiggjort) System drev (dekrypterer - %.2f%% færdiggjort) System drev (%.2f%% krypteret) System partition Skjult system partition System partition (krypterer - %.2f%% færdiggjort) System partition (dekrypterer - %.2f%% færdiggjort) System partition (%.2f%% krypteret) Ja (Skade undgået!) Ingen Primær Nøgle Størrelse Sekundær Nøgle Størrelse (XTS Tilstand) Klemt Nøgle Størrelse (LRW Tilstand) bits Blok størrelse PKCS-5 PRF PKCS-5 gentagelse talt Bind oprettet Etiket sidst ændret (%I64d dage siden) Bind Formatterings Version Implementeret Backup Header VeraCrypt Boot Loader Version Først tilgængelige Removable Disk Harddisk Uændret Autodetection Oprettelsesguide Tilstand Vælg en af tilstandende. Hvis du ikke er sikker på hvilken du skal vælge, brug da standard tilstand. Select this option if you want to install VeraCrypt on this system. Note: You can upgrade without decrypting even if the system partition/drive is encrypted or you use a hidden operating system. If you select this option, all files will be extracted from this package but nothing will be installed on the system. Do not select it if you intend to encrypt the system partition or system drive. Selecting this option can be useful, for example, if you want to run VeraCrypt in so-called portable mode. VeraCrypt does not have to be installed on the operating system under which it is run. After all files are extracted, you can directly run the extracted file 'VeraCrypt.exe' (then VeraCrypt will run in portable mode). Indstillings Muligheder Her kan du indstille forskellige muligheder for at kontrollere installations processen. Installerer Vent venligst mens VeraCrypt bliver installeret. VeraCrypt has been successfully installed VeraCrypt has been successfully upgraded Please consider making a donation. You can click Finish anytime to close the installer. Udpaknings Muligheder Her kan du indstille forskellige muligheder for at kontrollere udpaknings processen. Vent venligst mens filerne bliver udpakket. Files successfully extracted Alle filer er blevet udpakket med succes på destinations placeringen. Hvis den ønskede mappe ikke findes, vil den blive oprettet automatisk. The VeraCrypt program files will be upgraded in the location where VeraCrypt is installed. If you need to select a different location, please uninstall VeraCrypt first. Ønsker du at se udgivelsesnoter for den nuværende (seneste stabile) version af VeraCrypt? Hvis du aldrig før har brugt VeraCrypt, anbefaler vi at du læser kapitlet Begyndervejledning i VeraCrypt Brugervejledningen. Ønsker du at se vejledningen? Vælg venligst en handling der skal udføres udfra følgende: Reparer/geninstaller Upgrade Afinstaller To successfully install/uninstall VeraCrypt, you must have administrator privileges. Do you want to continue? VeraCrypt Installation kører nu på dette system og udfører eller forbereder installation eller opdatering af VeraCrypt. Før du fortsætter, vent venligst til det afsluttes eller luk det. Hvis du ikke kan lukke det, genstart venligst din computer før du fortsætter. Fejl under installation. Fejl under afinstallation. Denne distributions pakke er beskadiget. Prøv venligst at downloade den igen (helst fra det officielle VeraCrypt websted på https://www.veracrypt.fr). Kan ikke skrive fil %s Udpakker Kan ikke læse data fra pakken. Kan ikke kontrollere integriteten på denne distributions pakke. Fejl i udpakning. Installationen er trukket tilbage. VeraCrypt er installeret med succes. VeraCrypt has been successfully updated. VeraCrypt has been successfully upgraded. However, before you can start using it, the computer must be restarted.\n\nDo you want to restart it now? Failed to upgrade VeraCrypt!\n\nIMPORTANT: Before you shut down or restart the system, we strongly recommend that you use System Restore (Windows Start menu > All programs > Accessories > System Tools > System Restore) to restore your system to the restore point named 'VeraCrypt installation'. If System Restore is not available, you should try installing the original or the new version of VeraCrypt again before you shut down or restart the system. VeraCrypt er afinstalleret med succes.\n\nKlik 'Afslut' for at fjerne VeraCrypt installer og mappen %s. Bemærk at mappen ikke vil blive fjernet hvis den indeholder filer der blev installeret af VeraCrypt installer eller blev oprettet af VeraCrypt. Fjerner VeraCrypt i registreringsdatabasen Tilføjer i registreringsdatabasen Fjerner applikations-specifikke data Installerer Stopper Fjerner Tilføjer ikon Opretter system gendannelsespunkt Oprettelse af system gendannelsespunkt mislykket! Opdaterer boot loader Kunne ikke installere '%s'. %s Ønsker du at fortsætte installationen? Kunne ikke afinstallere '%s'. %s Ønsker du at fortsætte afinstallationen? Installationen fuldført. Mappen '%s' kunne ikke oprettes VeraCrypt enhedsdriveren kan ikke frakobles.\n\nLuk venligst alle åbne VeraCrypt vinduer først. Hvis dette ikke hjælper, genstart venligst Windows og prøv igen. Alle VeraCrypt bind skal afbrydes inden installation eller afinstallation af VeraCrypt. An obsolete version of VeraCrypt is currently installed on this system. It needs to be uninstalled before you can install this new version of VeraCrypt.\n\nAs soon as you close this message box, the uninstaller of the old version will be launched. Note that no volume will be decrypted when you uninstall VeraCrypt. After you uninstall the old version of VeraCrypt, run the installer of the new version of VeraCrypt again. Installation i registringsdatabasen er mislykket Installation af enhedsdriver er mislykket. Genstart venligst Windows og prøv at installere VeraCrypt igen. Starter VeraCrypt enhedsdriver Fejl i afinstallation af enhedsdriver. Bemærk venligst at, på grund af et Windows problem, kan det være nødvendigt at logge af eller genstarte systemet førend at enhedsdriveren kan afinstalleres (eller geninstalleres). Installerer VeraCrypt enhedsdriver Stopper VeraCrypt enhedsdriver Afinstallerer VeraCrypt enhedsdriver Registrering af Brugerkonto kontrolsupport bibliotek er mislykket. Afregistrering af Brugerkonto kontrolsupport bibliotek er mislykket. Note about portable mode:\n\nPlease note that the operating system requires drivers to be registered with it before they can be started. Hence, the VeraCrypt driver is not (and cannot be) fully portable (whereas the VeraCrypt applications are fully portable, i.e. they do not have to be installed or registered with the operating system). Also note that VeraCrypt needs a driver to provide transparent on-the-fly encryption/decryption. Note that if you decide to run VeraCrypt in portable mode (as opposed to running an installed copy of VeraCrypt), the system will ask you for permission to run VeraCrypt (UAC prompt) every time you attempt to run it.\n\nThe reason is that when you run VeraCrypt in portable mode, VeraCrypt needs to load and start the VeraCrypt device driver. VeraCrypt needs a device driver to provide transparent on-the-fly encryption/decryption, and users without administrator privileges cannot start device drivers in Windows. Therefore, the system will ask you for permission to run VeraCrypt with administrator privileges (UAC prompt).\n\nNote that if you install VeraCrypt on the system (as opposed to running VeraCrypt in portable mode), the system will NOT ask you for permission to run VeraCrypt (UAC prompt) every time you attempt to run it.\n\nAre you sure you want to extract the files? Warning: This instance of the Volume Creation Wizard has administrator privileges.\n\nYour new volume may be created with permissions that will not allow you to write to the volume when it is mounted. If you want to avoid that, close this instance of the Volume Creation Wizard and launch a new one without administrator privileges.\n\nDo you want to close this instance of the Volume Creation Wizard? Fejl: Kan ikke vise licensen. Ydre(!) dage timer minutter sekunder Åben Afbryd Vis VeraCrypt Skjul VeraCrypt Data læst siden tilslutning Data skrevet siden tilslutning Krypteret Mængde 100% (fuldt krypteret) 0% (ikke krypteret) %.3f%% 100% Afventer Preparing Resizing Krypterer Dekrypterer Finalizing Pause Afsluttet Error Device disconnected System favorite volumes saved.\n\nTo enable mounting of system favorite volumes when the system starts, please select 'Settings' > 'System Favorite Volumes' > 'Mount system favorite volumes when Windows starts'. The volume you are adding to favorites is neither a partition nor a dynamic volume. Therefore, VeraCrypt will be unable to mount this favorite volume if the device number changes. The volume you are adding to favorites is a partition not recognized by Windows.\n\nVeraCrypt will be unable to mount this favorite volume if the device number changes. Please set the type of the partition to a type recognized by Windows (use the SETID command of the Windows 'diskpart' tool). Then add the partition to favorites again. VeraCrypt Background Task is disabled or it is configured to exit when there are no mounted volumes (or VeraCrypt is running in portable mode). This may prevent your favorite volumes from being automatically mounted when devices hosting them get connected.\n\nNote: To enable the VeraCrypt Background Task, select Settings > Preferences and check the 'Enabled' checkbox in the section 'VeraCrypt Background Task'. A container stored in a remote filesystem shared over a network cannot be automatically mounted when its host device gets connected. The device displayed below is neither a partition nor a dynamic volume. Therefore, the volume hosted on the device cannot be automatically mounted when the device gets connected. Please set the type of the partition displayed below to a type recognized by Windows (use the SETID command of the Windows 'diskpart' tool). Then remove the partition from favorites and add it again. This will enable the volume hosted on the device to be automatically mounted when the device gets connected. The device displayed below is neither a partition nor a dynamic volume. Therefore, no label can be assigned to it. Please set the type of the partition displayed below to a type recognized by Windows (use the SETID command of the Windows 'diskpart' tool). Then remove the partition from favorites and add it again. This will enable VeraCrypt to assign a label to the partition. Due to a Windows limitation, a container stored in a remote filesystem shared over a network cannot be mounted as a system favorite volume (however, it can be mounted as a non-system favorite volume when a user logs on). Skriv kodeord til %s Enter password for '%s' Indtast kodeord for det normale/ydre bind Indtast kodeord for det skjulte bind Indtast kodeord for header gemt i backup filen Nøglefil er oprettet med succes. The number of keyfiles you supplied is invalid. The keyfile size must be at least 64 bytes. Please enter a name for the keyfile(s) to be generated The base name of the keyfile(s) is invalid The keyfile '%s' already exists.\nDo you want to overwrite it? The generation process will be stopped if you answer No. ADVARSEL: Etikettet på dette bind er beskadiget! VeraCrypt brugte automatisk det backup af bind etiketten der er implementeret i bindet.\n\nDu bør reparere bind etiketten ved at vælge 'Værktøjer' > 'Gendan Bind Etiket'. Backup af bind etiket er udført med succes.\n\nVIGTIGT: Gendannelse af bind etiket med dette backup vil også gendanne det nuværende binds kodeord. Derudover, hvis nøglefil(er) er nødvendige for at tilslutte bindet, vil de samme nøglefil(er) være nødvendige for at tilslutte bindet igen når bind etiketten gendannes.\n\nADVARSEL: Denne backup af bind etiket kan KUN bruges til at gendanne etiket for dette bestemte bind. Hvis du bruger denne etiket backup til at gendanne en etiket for et andet bind, vil du kunne tilslutte bindet, men du vil ikke være i stand til at dekryptere nogen data på bindet (fordi du vil ændre dets hovednøgle). Bindets etiket er blevet gendannet med succes.\n\nVIGTIGT: Bemærk venligst at et gammelt kodeord også kan være gendannet. Derudover, hvis nøglefil(er) var nødvendig til at tilslutte bindet da backup var lavet, vil de samme nøglefil(er) nu være nødvendige for at tilslutte bindet igen. Af sikkerheds årsager, vil du være nødt til at indtaste det korrekte kodeord (og/eller tilføje de korrekte nøglefiler) til bindet.\n\nBemærk: Hvis bindet indeholder et skjult bind, vil du være nødt til at indtaste det korrekte kodeord (og/eller tilføje de korrekte nøglefiler) for det ydre bind først. Bagefter, hvis du ønsker at lave back up af etiketten på det skjulte bind, vil du være nødt til at indtaste det korrekte kodeord (og/eller tilføje de korrekte nøglefiler) for det skjulte bind. Er du sikker på du ønsker at oprette bind etiket backup for %s?\n\nEfter du har klikket Ja, vil du blive spurgt om et filnavn for etiket backup.\n\nBemærk: Både standard og det skjulte binds etiketter vil blive gen-krypteret ved brug af en ny pulje og gemt i backup filen. Hvis der ikke er noget skjult bind i dette bind, bliver området reserveret for det skjulte binds etiket i backup filen udfyldt med tilfældig data (for at bevare den troværdige benægtelse). Ved gendannelse af en bind etiket fra backup filen, vil du være nødt til at indtaste det korrekte kodeord (og/eller tilføje de korrekte nøglefiler) som var gældende da bind etiket backuppen blev oprettet. Kodeordet (og/eller nøglefiler) vil også automatisk bestemme typen af bind etiketten der skal gendannes, dvs. standard eller skjult (bemærk at VeraCrypt bestemmer typen gennem en proces med prøver og fejl). Er du sikker på du ønsker at gendanne bind etiketten for %s?\n\nADVARSEL: Gendannelse af bind etiketter gendanner også det bind kodeord der var gældende da backup blev foretaget. Ydermere, hvis nøglefil(er) var påkrævet for at tilslutte bindet da backup blev foretaget, vil de samme nøglefiler være nødvendige for at tilslutte bindet igen efter bind etiketten er gendannet.\n\nEfter du har klikket Ja, kan du vælge backup etiket filen. Indeholder bindet et skjult bind? Bindet indeholder et skjult bind Bindet indeholder ikke et skjult bind Vælg venligst typen af bind etiket backup du ønsker at bruge: Gendan bind etiket fra den indbyggede backup i bindet Gendan bind etiket fra en ekstern backup fil Størrelsen af bind etiket backup filen er ukorrekt. Der er ingen backup etiket indbygget i dette bind (bemærk at kun bind oprettet med TrueCrypt 6.0 eller senere indeholder indbyggede backup etiketter). Du forsøger at lave backup af etiket for system partition/drevet. Dette er ikke tilladt. Backup/gendan funktioner angående system partition/drev kan kun udføres ved hjælp af VeraCrypt Nødhjælps Disk.\n\nØnsker du at oprette en VeraCrypt Nødhjælps Disk? Du forsøger at gendanne en etiket for et virtuelt VeraCrypt bind men du valgte system partition/drev. Dette er ikke tilladt. Backup/gendan funktioner angående system partition/drev kan kun udføres ved hjælp af VeraCrypt Nødhjælps Disk.\n\nØnsker du at oprette en VeraCrypt Nødhjælps Disk? Efter du har klikket OK, skal du vælge et filnavn til det nye VeraCrypt Nødhjælps Disk billede og placeringen hvor du ønsker at placere det. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to burn the Rescue Disk image to a CD or DVD.\n\nIMPORTANT: 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.\n\nAfter you burn the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly burned. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to burn the Rescue Disk image to a CD or DVD.\n\nDo you want to launch the Microsoft Windows Disc Image Burner now?\n\nNote: After you burn the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly burned. Indsæt venligst din VeraCrypt Nødhjælps Disk og klik på OK for at kontrollere den. VeraCrypt Nødhjælps Disk er blevet kontrolleret med succes. Kan ikke kontrollere at Nødhjælps Disk er blevet korrekt brændt.\n\nHvis du har brændt Nødhjælps Disk, vær venlig at tage CD/DVD ud og sætte den i igen; prøv så igen. Hvis dette ikke hjælper, prøv venligst en anden CD/DVD optager software og/eller medie.\n\nHvis du forsøgte at kontrollere en VeraCrypt Nødhjælps Disk oprettet med en anden hovednøgle, kodeord, salt, osv., bemærk venligst at en sådan Nødhjælps Disk altid vil fejle denne kontrol. For at oprette en ny Nødhjælps Disk der er fuld ud kompatibel med din nuværende konfiguration, vælg 'System' > 'Opret Nødhjælps Disk'. The VeraCrypt Rescue Disk image has been successfully verified. The Rescue Disk image verification failed.\n\nIf you attempted to verify a VeraCrypt Rescue Disk image created for a different master key, password, salt, etc., please note that such Rescue Disk image will always fail this verification. To create a new Rescue Disk image fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. Fejl i oprettelsen af VeraCrypt Nødhjælps Disk. VeraCrypt Nødhjælps Disk kan ikke oprettes når et skjult operativsystem kører.\n\nFor at oprette en VeraCrypt Nødhjælps Disk, boot op på aflednings operativsystemet og vælg så 'System' > 'Opret Nødhjælps Disk'. Cannot verify that the Rescue Disk has been correctly burned.\n\nIf you have burned the Rescue Disk, please eject and reinsert the CD/DVD; then click Next to try again. If this does not help, please try another medium%s.\n\nIf you have not burned the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to burn the newly generated Rescue Disk. and/or other CD/DVD recording software VeraCrypt - System Favorite Volumes What are system favorite volumes? The system partition/drive does not appear to be encrypted.\n\nSystem favorite volumes can be mounted using only a pre-boot authentication password. Therefore, to enable use of system favorite volumes, you need to encrypt the system partition/drive first. Afbryd venligst bindet før der fortsættes. Fejl: Kan ikke indstille timer. Kontroller Filsystem Reparer Filsystem Add to Favorites... Add to System Favorites... P&roperties... Skjult Bind beskyttet N/A Ja Nej Deaktiveret 1 2 eller flere Driftstilstand Label: Size: Path: Drive Letter: Fejl: Kodeord må kun indeholde ASCII karakterer.\n\nIkke-ASCII karakterer i kodeord kan forårsage at bindet vil være umuligt at tilslutte når dine system indstillinger ændres.\n\nFølgende karakterer kan anvendes:\n\n ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ Advarsel: Kodeord indeholder ikke-ASCII karakterer. Dettekan forårsage at bindet vil være umuligt at tilslutte når dine system indstillinger ændres.\n\nDu bør udskifte alle ikke-ASCII karakterer i kodeordet med ASCII. For at gøre dette klik 'Bind' -> 'Ændre Bind Kodeord'.\n\nFølgende er ASCII karakterer:\n\n ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \\ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ WARNING: We strongly recommend that you avoid file extensions that are used for executable files (such as .exe, .sys, or .dll) and other similarly problematic file extensions. Using such file extensions causes Windows and antivirus software to interfere with the container, which adversely affects the performance of the volume and may also cause other serious problems.\n\nWe strongly recommend that you remove the file extension or change it (e.g., to '.hc').\n\nAre you sure you want to use the problematic file extension? WARNING: This container has a file extension that is used for executable files (such as .exe, .sys, or .dll) or some other file extension that is similarly problematic. It will very likely cause Windows and antivirus software to interfere with the container, which will adversely affect the performance of the volume and may also cause other serious problems.\n\nWe strongly recommend that you remove the file extension of the container or change it (e.g., to '.hc') after you dismount the volume. Hjemmeside ADVARSEL: Tilsyneladende har du ikke Service Packs i din Windows XP installation. Du bør ikke gemme på IDE diske større end 128 GB under Windows XP hvor du ikke har tilføjet Service Pack 1 eller nyere! Hvis du gør, vil data på disken (uanset om det er et VeraCrypt bind eller ej) blive ødelagt. Bemærk at dette er en begrænsning i Windows, ikke en fejl i VeraCrypt. ADVARSEL: Tilsyneladende har du ikke Service Pack 3 eller nyere i din Windows installation. Du bør ikke gemme på IDE diske større end 128 GB under Windows 2000 hvor du ikke har tilføjet Service Pack 3 eller nyere! Hvis du gør, vil data på disken (uanset om det er et VeraCrypt bind eller ej) blive ødelagt. Bemærk at dette er en begrænsning i Windows, ikke en begræsning i VeraCrypt.\n\nBemærk: Måske er det også nødvendigt at aktivere 48-bit LBA support i registreringsdatabasen; for mere information, se http://support.microsoft.com/kb/305098/EN-US ADVARSEL: 48-bit LBA ATAPI support er slået fra i dit system. Derfor bør du ikke skrive til IDE diske større end 128 GB! Hvis du gør, vil data på disken (uanset om det er et VeraCrypt bind eller ej) blive ødelagt. Bemærk at dette er en begrænsning i Windows, ikke en begræsning i VeraCrypt.\n\nFor at aktivere 48-bit LBA support, tilføj 'EnableBigLba' registreringsværdien i registreringsnøglen HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\atapi\\Parameters og sæt den til 1.\n\nFor yderligere information, se http://support.microsoft.com/kb/305098 Fejl: Filer større end 4 GB kan ikke gemmes på et FAT32 fil system. Derfor kan fil-baserede VeraCrypt bind (beholdere) gemt på et FAT32 fil ikke være større end 4 GB.\n\nHvis du har behov for et større bind, opret det da som et NTFS fil system (eller, hvis du bruger Windows Vista SP1 eller nyere, på et exFAT fil system) eller, istedet for at oprette et fil-baseret bind, krypter en hel partition eller enhed. Warning: Windows XP does not support files larger than 2048 GB (it will report that "Not enough storage is available"). Therefore, you cannot create a file-hosted VeraCrypt volume (container) larger than 2048 GB under Windows XP.\n\nNote that it is still possible to encrypt the entire drive or create a partition-hosted VeraCrypt volume larger than 2048 GB under Windows XP. ADVARSEL: Hvis du ønsker at kunne tilføje data/filer til det ydre bind i fremtiden, bør du overveje at vælge en mindre størrelse for det skjulte bind.\n\nEr du sikker på du ønsker at fortsætte med den valgte størrelse? Ingen bind valgt.\n\nKlik 'Vælg Enhed' eller 'Vælg Fil' for at vælge et VeraCrypt bind. Ingen partition valgt.\n\nKlik 'Vælg Enhed' for at vælge en afbrudt partition der normalt kræver før-boot godkendelse (for eksempel, en partition placeret på et krypteret system drev af et andet operativsystem, som ikke kører, eller en krypteret system partition af et andet operativsystem).\n\nBemærk: Den valgte partition vil blive tilsluttet som et almindeligt VeraCrypt bind uden før-boot godkendelse. Dette er brugbart f.eks. ved backup eller reparationsarbejde. ADVARSEL: Hvis standard nøglefiler er valgt og aktiveret, vil bind der ikke bruger disse nøglefiler være umulige at tilslutte. Derfor, efter du har aktiveret standard nøglefiler, husk at fjerne markeringen udfor 'Brug nøglefiler' afmærkningsboksen (under et kodeords indtastningsfelt) når du tilslutter sådanne bind.\n\nEr du sikker på du ønsker at gemme de valgte nøglefiler/stier som standard? Auto-Tilslut Enheder Afbryd alle Ryd hukommelse Dismount All & Wipe Cache Gennemtving afbrydelse af alle & Ryd hukommelse Gennemtving afbrydelse af alle, Ryd hukommelse & Afslut Tilslut Favorit Bind Vis/Skjul Hoved VeraCrypt Vindue (Klik her og tryk på en tast) Handling Genvej Fejl: Denne genvej er reserveret. Vælg venligst en anden. Fejl: Genvejen er allerede i brug. ADVARSEL: En eller flere VeraCrypt system-tilgængelige genvejstaster vil ikke virke!\n\nKontroller venligst at andre applikationer og operativsystem ikke benytter samme genvej(e) som VeraCrypt. Paging file creation has been prevented.\n\nPlease note that, due to Windows issues, paging files cannot be located on non-system VeraCrypt volumes (including system favorite volumes). VeraCrypt supports creation of paging files only on an encrypted system partition/drive. En fejl eller ukompatibilitet forhindrer VeraCrypt fra at kryptere dvale filen. Derfor er dvale forhindret.\n\nBemærk: Når en computer går i dvale (eller går i strømbesparende tilstand), bliver indholdet i system hukommelsen skrevet til en dvale opbevarings fil der gemmes på system drevet. VeraCrypt ville ikke være i stand til at forhindre krypterings nøgler og indhold i følsomme filer der er åbne i RAM fra at blive gemt ukrypteret til dvale opbevarings filen. Hibernation has been prevented.\n\nVeraCrypt does not support hibernation on hidden operating systems that use an extra boot partition. Please note that the boot partition is shared by both the decoy and the hidden system. Therefore, in order to prevent data leaks and problems while resuming from hibernation, VeraCrypt has to prevent the hidden system from writing to the shared boot partition and from hibernating. VeraCrypt volume mounted as %c: has been dismounted. VeraCrypt volumes have been dismounted. VeraCrypt volumes have been dismounted and password cache has been wiped. Successfully dismounted WARNING: If the VeraCrypt Background Task is disabled, the following functions will be disabled:\n\n1) Hot keys\n2) Auto-dismount (e.g., upon logoff, inadvertent host device removal, time-out, etc.)\n3) Auto-mount of favorite volumes\n4) Notifications (e.g., when damage to hidden volume is prevented)\n5) Tray icon\n\nNote: You can shut down the Background Task anytime by right-clicking the VeraCrypt tray icon and selecting 'Exit'.\n\nAre you sure you want to permanently disable the VeraCrypt Background Task? ADVARSEL: Hvis denne funktion deaktiveres, vil bind der indeholder åbne filer/mapper ikke være mulige at auto-tilslutte.\n\nEr du sikker på du vil deaktivere denne funktion? ADVARSEL: Bind der indeholder åbne filer/mapper vil IKKE blive auto-afbrudt.\n\nFor at undgå dette, aktiver den følgende funktion i dette dialog vindue: 'Udfør auto-afbryd selv om bindet indeholder åbne filer eller mapper' WARNING: When the notebook battery power is low, Windows may omit sending the appropriate messages to running applications when the computer is entering power saving mode. Therefore, VeraCrypt may fail to auto-dismount volumes in such cases. You have scheduled the process of encryption of a partition/volume. The process has not been completed yet.\n\nDo you want to resume the process now? Du har planlagt en krypterings eller dekrypterings proces af system partition/drev. Processen er endnu ikke blevet fuldført.\n\nØnsker du at starte (genoptage) processen nu? Do you want to be prompted about whether you want to resume the currently scheduled processes of encryption of non-system partitions/volumes? Yes, keep prompting me No, do not prompt me IMPORTANT: Keep in mind that you can resume the process of encryption of any non-system partition/volume by selecting 'Volumes' > 'Resume Interrupted Process' from the menu bar of the main VeraCrypt window. Du har skemalagt processen for kryptering eller dekryptering af system partition/drev. Imidlertid opstod der fejl på før-boot godkendelsen (eller den blev sprunget over).\n\nBemærk: Hvis du dekrypterede system partition/drev i før-boot miljøet, kan det være nødvendigt du afslutter processen ved at vælge 'System' > 'Dekrypter System Partition/Drev Permanent' fra menulinien i hovedvinduet af VeraCrypt. WARNING: If VeraCrypt exits now, the following functions will be disabled:\n\n1) Hot keys\n2) Auto-dismount (e.g., upon logoff, inadvertent host device removal, time-out, etc.)\n3) Auto-mount of favorite volumes\n4) Notifications (e.g., when damage to hidden volume is prevented)\n\nNote: If you do not wish VeraCrypt to run in the background, disable the VeraCrypt Background Task in the Preferences (and, if necessary, disable the automatic start of VeraCrypt in the Preferences).\n\nAre you sure you want VeraCrypt to exit? Afslut? VeraCrypt har ikke nok information til at afgøre om der skal krypteres eller dekrypteres. VeraCrypt har ikke nok information til at afgøre om der skal krypteres eller dekrypteres.\n\nBemærk: Hvis du har dekrypteret system partition/drev i før-boot miljøet, kan det være nødvendigt at du afslutter processen ved at klikke på Dekrypter. Note: When you are encrypting a non-system partition/volume in place and an error persistently prevents you from finishing the process, you will not be able to mount the volume (and access data stored on it) until you entirely DECRYPT the volume (i.e. reverse the process).\n\nIf you need to do so, follow these steps:\n1) Exit this wizard.\n2) In the main VeraCrypt window, select 'Volumes' > 'Resume Interrupted Process'.\n3) Select 'Decrypt'. Do you want to interrupt and postpone the process of encryption of the partition/volume?\n\nNote: Keep in mind that the volume cannot be mounted until it has been fully encrypted. You will be able to resume the process of encryption and it will continue from the point it was stopped. You can do so, for example, by selecting 'Volumes' > 'Resume Interrupted Process' from the menu bar of the main VeraCrypt window. Ønsker du at afbryde og udskyde processen med kryptering af system partition/drev?\n\nBemærk: Du vil være i stand til at genoptage processen og den vil fortsætte fra det sted den blev stoppet. Du kan gøre dette ved f.eks. ved at vælge 'System' > 'Genoptag Afbrudt Proces' fra menulinien i hovedvinduet i VeraCrypt. Hvis du ønsker permanent at afbryde eller tilbageføre krypterings processen, vælg 'System' > 'Dekrypter System Partition/Drev Permanent'. Ønsker du at afbryde og udskyde processen med dekryptering af system partition/drev?\n\nBemærk: Du vil være i stand til at genoptage processen og den vil fortsætte fra det sted den blev stoppet. Du kan gøre dette ved f.eks. ved at vælge 'System' > 'Genoptag Afbrudt Proces' fra menulinien i hovedvinduet i VeraCrypt. Hvis du ønsker at tilbageføre dekrypterings processen (og påbegynde kryptering), vælg 'System' > 'Krypter System Partition/Drev'. Fejl: Kunne ikke afbryde processen med kryptering/dekryptering af system partition/drev. Error: Failed to interrupt the process of wiping. Fejl: Kunne ikke genoptage processen med kryptering/dekryptering af system partition/drev. Error: Failed to start the process of wiping. Uoverensstemmelse løst.\n\n\n(Hvis du ønsker at rapportere en fejl i denne forbindelse, inkluder venligst følgende tekniske information i fejlrapporten: %hs) Error: Unexpected state.\n\n\n(If you report a bug in connection with this, please include the following technical information in the bug report:\n%hs) There is no interrupted process of encryption/decryption of the system partition/drive to resume.\n\nNote: If you want to resume an interrupted process of encryption/decryption of a non-system partition/volume, select 'Volumes' > 'Resume Interrupted Process'. ADVARSEL: VeraCrypt baggrundsopgaver er slået fra. Efter du afslutter VeraCrypt, vil du ikke blive gjort opmærksom på om skade på det skjulte bind er undgået.\n\nBemærk: Du kan nårsomhelst lukke baggrundsopgaver ned ved at højreklikke på VeraCrypt ikonet i systembakken, og klikke på 'Afslut'.\n\nAktiver VeraCrypt Baggrundsopgaver? Sprogpakke version: %s Kontrollerer fil systemet på VeraCrypt bindet tilsluttet som %s... Prøver at reparere filsystemet på det VeraCrypt bind der er tilsluttet som %s. Advarsel: Dette bind er krypteret med en ældre algoritme.\n\nAlle 64-bit-blok krypterings algoritmer (f.eks., Blowfish, CAST-128, eller Triple DES) foretrækkes ikke. Det vil være muligt at tilslutte disse bind med fremtidige versioner af VeraCrypt. Dog vil der fremover ikke komme flere forbedringer til udførelsen af disse ældre krypterings algoritmer. Vi anbefaler at du opretter et nyt VeraCrypt bind krypteret med 128-bit-blok krypterings algorithmer (f.eks., AES, Serpent, Twofish, osv.) og at du flytter alle filer til dette nye bind. Dit system er ikke konfigureret til automatisk at tilslutte nye bind. Det kan være umuligt at tilslutte enhedsbaserede VeraCrypt bind. Automatisk tilslutning kan konfigureres ved at køre denne kommando og genstarte systemet.\n\nmountvol.exe /E Tildel venligst et drev bogstav til partitionen/enheden før du fortsætter ('Kontrolpanel' > 'Ydelse og Vedligeholdelse' > 'Administration' - 'Computeradministration / Diskhåndtering').\n\nBemærk at dette er afhængig af det anvendte operativsystem. Tilslut VeraCrypt Bind Afbryd alle VeraCrypt Bind VeraCrypt fejl i at opnå administrator rettighed. Adgang nægtet af operativsystem.\n\nMulig årsag: Operativsystemet kræver at du har læse/skrive tilladelse (eller administrations rettigheder) for bestemte mapper, filer, og enheder, for at du kan få tilladelse til at læse og skrive data til/fra dem. Normalt kan en bruger uden administrator rettigheder godt oprette, læse og redigere filer i brugerens dokumentmappe. Error: The drive uses an unsupported sector size.\n\nIt is currently not possible to create partition/device-hosted volumes on drives that use sectors larger than 4096 bytes. However, note that you can create file-hosted volumes (containers) on such drives. It is currently not possible to encrypt a system installed on a disk that uses a sector size other than 512 bytes. VeraCrypt Boot Loader kræver mindst 32 KBytes ledig disk plads i begyndelsen af system drevet (VeraCrypt Boot Loader kræver at det skal gemmes i det område). Desværre imødekommer dit drev ikke denne tilstand.\n\nVær venlig IKKE at rapportere dette som en fejl/problem i VeraCrypt. For at løse dette problem, vil du skulle partitionere din disk igen og lade de første 32 KBytes af din disk være fri (i de fleste tilfælde, vil du være nødt til at slette og genoprette den første partition). Vi anbefaler at du bruger Microsoft partition manager som er tilgængelig f.eks. når du installerer Windows. Funktionen er ikke supporteret i denne version af det operativsystem du nu benytter. VeraCrypt supporterer ikke kryptering af en system partition/drev i denne version af operativsystem du nu benytter. Before you can encrypt the system partition/drive on Windows Vista, you need to install Service Pack 1 or higher for Windows Vista (no such Service Pack has been installed on this system yet).\n\nNote: Service Pack 1 for Windows Vista resolved an issue causing a shortage of free base memory during system boot. VeraCrypt no longer supports encryption of the system partition/drive on Windows Vista with no Service Pack installed. Before upgrading VeraCrypt, please install Service Pack 1 or higher for Windows Vista. Error: This feature requires VeraCrypt to be installed on the system (you are running VeraCrypt in portable mode).\n\nPlease install VeraCrypt and then try again. WARNING: Windows does not appear to be installed on the drive from which it boots. This is not supported.\n\nYou should continue only if you are sure that Windows is installed on the drive from which it boots.\n\nDo you want to continue? FORSIGTIG: VeraCrypt Boot Loader er allerede installeret på dit system drev!\n\nDet er muligt at et andet system på din computer allerede er krypteret.\n\nADVARSEL: FORTSÆTTELSE MED KRYPTERING AF DET NUVÆRENDE KØRENDE SYSTEM VIL KUNNE GØRE ANDRE SYSTEMER UMULIGE AT STARTE OG RELATERET DATA UTILGÆNGELIGT.\n\nEr du sikker på du ønsker at fortsætte? Failed to restore the original system loader.\n\nPlease use your VeraCrypt Rescue Disk ('Repair Options' > 'Restore original system loader') or Windows installation medium to replace the VeraCrypt Boot Loader with the Windows system loader. Den originale system loader kan ikke gemmes på Nødhjælps Disk (mulig årsag: manglende backup fil). Kunne ikke skrive MBR sektor.\n\nDin BIOS er muligvis konfigureret til at beskytte MBR sektoren. Tjek din BIOS indstilling (tryk F2, Delete, eller Esc, efter du har tændt din computer) for MBR/antivirus beskyttelse. WARNING: The verification of VeraCrypt bootloader fingerprint failed!\nYour disk may have been tampered with by an attacker ("Evil Maid" attack).\n\nThis warning can also be triggered if you restored VeraCrypt boot loader using an Rescue Disk generated using a different VeraCrypt version.\n\nYou are advised to change your password immediately which will also restore the correct VeraCrypt bootloader. It is recommended to reinstall VeraCrypt and to take measures to avoid access to this machine by untrusted entities. The required version of the VeraCrypt Boot Loader is currently not installed. This may prevent some of the settings from being saved. Note: In some situations, you may wish to prevent a person (adversary) that is watching you start the computer from knowing that you use VeraCrypt. The above options allow you to do that by customizing the VeraCrypt boot loader screen. If you enable the first option, no texts will be displayed by the boot loader (not even when you enter the wrong password). The computer will appear to be "frozen" while you can type your password. In addition, a custom message can be displayed to mislead the adversary. For example, fake error messages such as "Missing operating system" (which is normally displayed by the Windows boot loader if it finds no Windows boot partition). It is, however, important to note that if the adversary can analyze the content of the hard drive, he can still find out that it contains the VeraCrypt boot loader. WARNING: Please keep in mind that if you enable this option, the VeraCrypt boot loader will not display any texts (not even when you enter the wrong password). The computer will appear to be "frozen" (unresponsive) while you can type your password (the cursor will NOT move and no asterisk will be displayed when you press a key).\n\nAre you sure you want to enable this option? Dit system partition/drev ser ud til at være helt krypteret. VeraCrypt supporterer ikke kryptering af system drev der er blevet konverteret til en dynamisk disk. The system drive contains extended (logical) partitions.\n\nYou can encrypt an entire system drive containing extended (logical) partitions only on Windows Vista and later versions of Windows. On Windows XP, you can encrypt an entire system drive provided that it contains only primary partitions.\n\nNote: You can still encrypt the system partition instead of the entire system drive (and, in addition to that, you can create partition-hosted VeraCrypt volumes within any non-system partitions on the drive). WARNING: As you are running Windows XP/2003, after you start encrypting the drive, you must NOT create any extended (logical) partitions on it (you may create only primary partitions). Any extended (logical) partition on the drive would be inaccessible after you start encrypting (the drive currently does not contain any such partition).\n\nNote: If this limitation is not acceptable, you can go back and choose to encrypt only the system partition instead of the entire drive (and, in addition to that, you can create partition-hosted VeraCrypt volumes within any non-system partitions on the drive).\n\nAlternatively, if this limitation is not acceptable, you may want to consider upgrading to Windows Vista or a later version of Windows (you can encrypt an entire system drive containing extended/logical partitions only on Windows Vista or later). Your system drive contains a non-standard partition.\n\nIf you are using a notebook, your system drive probably contains a special recovery partition. After the whole system drive is encrypted (including any recovery partition), your system might become unbootable if your computer is using an inappropriately designed BIOS. It would also be impossible to use any recovery partition until the system drive is decrypted. Therefore, we recommend that you encrypt only the system partition. Ønsker du at kryptere system partitionen istedet for hele drevet?\n\nBemærk at du kan oprette partition-værts baserede VeraCrypt bind inden i enhver ikke-system partition på drevet (foruden at kryptere system partitionen). Da dit system drev kun indeholder en enkelt partition som optager hele drevet, vil det være at foretrække (mere sikkert) at kryptere hele drevet inklusiv den ledige "rest" plads der typisk omgiver sådan en partition.\n\nØnsker du at kryptere hele system drevet? Your system is configured to store temporary files on a non-system partition.\n\nTemporary files may be stored only on the system partition. Your user profile files are not stored on the system partition.\n\nUser profile files may be stored only on the system partition. There is/are paging file(s) on non-system partitions.\n\nPaging files may be located only on the system partition. Do you want to configure Windows to create paging files only on the Windows partition now?\n\nNote that if you click 'Yes', the computer will be restarted. Then start VeraCrypt and try creating the hidden OS again. Otherwise, plausible deniability of the hidden operating system might be adversely affected.\n\nNote: If an adversary analyzed the content of such files (residing on a non-system partition), he might find out that you used this wizard in the hidden-system-creation mode (which might indicate the existence of a hidden operating system on your computer). Also note that any such files stored on the system partition will be securely erased by VeraCrypt during the process of creation of the hidden operating system. WARNING: During the process of creation of the hidden operating system, you will be required to fully reinstall the currently running system (in order to create a decoy system securely).\n\nNote: The currently running operating system and the entire content of the system partition will be copied to the hidden volume (in order to create the hidden system).\n\n\nAre you sure you will be able to install Windows using a Windows Setup medium (or using a service partition)? For security reasons, if the currently running operating system requires activation, it must be activated before proceeding. Note that the hidden operating system will be created by copying the content of the system partition to a hidden volume (so if this operating system is not activated, the hidden operating system will not be activated either). For more information, see the section "Security Requirements and Precautions Pertaining to Hidden Volumes" in the VeraCrypt User's Guide.\n\nImportant: Before proceeding, please make sure you have read the section "Security Requirements and Precautions Pertaining to Hidden Volumes" in the VeraCrypt User's Guide.\n\n\nDoes the currently running operating system meet the above condition? Your system uses an extra boot partition. VeraCrypt does not support hibernation on hidden operating systems that use an extra boot partition (decoy systems can be hibernated without any problems).\n\nPlease note that the boot partition would be shared by both the decoy and the hidden system. Therefore, in order to prevent data leaks and problems while resuming from hibernation, VeraCrypt has to prevent the hidden system from writing to the shared boot partition and from hibernating.\n\n\nDo you want to continue? If you select 'No', instructions for removing the extra boot partition will be displayed. \nThe extra boot partition can be removed before installing Windows. To do so, follow these steps:\n\n1) Boot your Windows installation disc.\n\n2) In the Windows installer screen, click 'Install now' > 'Custom (advanced)'.\n\n3) Click 'Drive Options'.\n\n4) Select the main system partition and delete it by clicking 'Delete' and 'OK'.\n\n5) Select the 'System Reserved' partition, click 'Extend', and increase its size so that the operating system can be installed to it.\n\n6) Click 'Apply' and 'OK'.\n\n7) Install Windows on the 'System Reserved' partition.\n\n\nShould an attacker ask why you removed the extra boot partition, you can answer that you wanted to prevent any possible data leaks to the unencrypted boot partition.\n\nNote: You can print this text by clicking the 'Print' button below. If you save a copy of this text or print it (strongly recommended, unless your printer stores copies of documents it prints on its internal drive), you should destroy any copies of it after removing the extra boot partition (otherwise, if such a copy was found, it might indicate that there is a hidden operating system on this computer). Advarsel: Der er uallokeret område mellem system partition og den første partition bag den. Efter du har oprettet det skjulte operativsystem, må du ikke oprette nogle nye partitioner i det uallokerede område. Ellers vil det skjulte operativsystem være umuligt at boote (indtil du sletter sådanne nyoprettede partitioner). Denne algoritme er for tiden ikke supporteret til system kryptering. This algorithm is not supported for TrueCrypt mode. PIM (Personal Iterations Multiplier) not supported for TrueCrypt mode. Password must contain 20 or more characters in order to use the specified PIM.\nShorter passwords can only be used if the PIM is 485 or greater. Pre-boot authentication Password must contain 20 or more characters in order to use the specified PIM.\nShorter passwords can only be used if the PIM is 98 or greater. Keyfiles are currently not supported for system encryption. Advarsel: VeraCrypt kunne ikke gendanne det originale keyboard layout. Dette kan medføre at du indtaster et kodeord ukorrekt. Fejl: Kan ikke indstille keyboard layoutet for VeraCrypt til standard US keyboard layout.\n\nBemærk at kodeordet skal indtastes i før-boot miljøet (før Windows starter) hvor ikke-US Windows keyboard layouts ikke er tilgængelige. Derfor skal kodeordet altid skrives ved brug af standard US keyboard layout. Da VeraCrypt midlertidigt har ændret keyboard layout til standard US keyboard layout, det er ikke muligt at indtaste karakterer ved trykke på taster mens den højre Alt tast holdes nede. Derimod kan du indtaste de fleste af disse karakterer, ved at trykke de passende taster mens Shift tasten holdes nede. VeraCrypt forhindrede ændring af keyboard layout. Bemærk: Kodeordet skal indtastes i før-boot miljøet (før Windows starter) hvor ikke-US Windows keyboard layouts ikke er tilgængelige. Derfor, bør kodeordet altid indtastes ved brug af standard US keyboard layout. Derimod er det vigtigt at bemærke at du IKKE behøver et rigtigt US keyboard. VeraCrypt sikrer automatisk at du roligt kan indtaste kodeordet (lige nu og i før-boot miljøet) selv om du ikke har et rigtigt US keyboard. Before you can encrypt the partition/drive, you must create a VeraCrypt Rescue Disk (VRD), which serves the following purposes:\n\n- If the VeraCrypt Boot Loader, master key, or other critical data gets damaged, the VRD allows you to restore it (note, however, that you will still have to enter the correct password then).\n\n- If Windows gets damaged and cannot start, the VRD allows you to permanently decrypt the partition/drive before Windows starts.\n\n- The VRD will contain a backup of the present content of the first drive track (which typically contains a system loader or boot manager) and will allow you to restore it if necessary.\n\nThe VeraCrypt Rescue Disk ISO image will be created in the location specified below. 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. The Rescue Disk image has been created and stored in this file:\n%s\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. The Rescue Disk image has been created and stored in this file:\n%s\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. 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 Launch Microsoft Windows Disc Image Burner 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. Fejl: Kan ikke gemme system krypterings indstillinger. Kan ikke påbegynde system krypterings første test. Kan ikke påbegynde processen med at oprette det skjulte operativsystem. Udviske Tilstand 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. 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. Wiping \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. \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. Do you want to abort the process of wiping? Warning: The entire content of the selected partition/device will be erased and lost. 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. 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? Ingen (hurtigst) 1-pass (random data) 3-passager (US DoD 5220.22-M) 7-passager (US DoD 5220.22-M) 35-pass ("Gutmann") 256-pass Antal Operativsystemer ADVARSEL: Uerfarne brugere bør aldrig forsøge at kryptere Windows i multi-boot konfigurationer.\n\nFortsæt? 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? VeraCrypt does not support this multi-boot configuration when creating/using a hidden operating system. Boot Drev 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'. VeraCrypt supporterer for tiden ikke kryptering af operativsystemer der ikke booter fra drevet hvorpå det er installeret. Antal System Drev 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'. 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. Flere Systemer på et Drev 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'. Ikke-Windows Boot Loader 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'. Multi-Boot 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. 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. Kryptering af værts beskyttet område 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? Type af System Kryptering Vælg dette hvis du ønsker at kryptere system partitionen eller hele system drevet. It may happen that you are forced by somebody to decrypt the operating system. There are many situations where you cannot refuse to do so (for example, due to extortion). If you select this option, you will create a hidden operating system whose existence should be impossible to prove (provided that certain guidelines are followed). Thus, you will not have to decrypt or reveal the password to the hidden operating system. For a detailed explanation, please click the link below. It may happen that you are forced by somebody to decrypt the operating system. There are many situations where you cannot refuse to do so (for example, due to extortion).\n\nUsing this wizard, you can create a hidden operating system whose existence should be impossible to prove (provided that certain guidelines are followed). Thus, you will not have to decrypt or reveal the password for the hidden operating system. Skjult Operativsystem In the following steps, you will create two VeraCrypt volumes (outer and hidden) within the first partition behind the system partition. The hidden volume will contain the hidden operating system (OS). VeraCrypt will create the hidden OS by copying the content of the system partition (where the currently running OS is installed) to the hidden volume. To the outer volume, you will copy some sensitive looking files that you actually do NOT want to hide. They will be there for anyone forcing you to disclose the password for the hidden OS partition. You can reveal the password for the outer volume within the hidden OS partition (the existence of the hidden OS remains secret).\n\nFinally, on the system partition of the currently running OS, you will install a new OS, so-called decoy OS, and encrypt it. It must not contain sensitive data and will be there for anyone forcing you to reveal your pre-boot authentication password. In total, there will be three passwords. Two of them can be disclosed (for the decoy OS and outer volume). If you use the third one, the hidden OS will start. Detekterer Skjulte Sektorer Vent venligst mens VeraCrypt detekterer mulige skjulte sectorer sidst på system drevet. Bemærk at det kan tage lang tid at fuldføre.\n\nBemærk: I meget sjældne tilfælde, på nogle computere, kan systemet blive låst og ikke svare under denne detektions process. Hvis dette sker, genstart computeren, start VeraCrypt, gentag de tidligere trin men spring over denne detektions process. Bemærk at dette ikke er forårsaget af en fejl i VeraCrypt. Område til kryptering Select this option if you want to encrypt the entire drive on which the currently running Windows system is installed. The whole drive, including all its partitions, will be encrypted except the first track where the VeraCrypt Boot Loader will reside. Anyone who wants to access a system installed on the drive, or files stored on the drive, will need to enter the correct password each time before the system starts. This option cannot be used to encrypt a secondary or external drive if Windows is not installed on it and does not boot from it. Indsamler tilfældig data Generede nøgler VeraCrypt has found no CD/DVD burner connected to your computer. VeraCrypt needs a CD/DVD burner to burn a bootable VeraCrypt Rescue Disk containing a backup of the encryption keys, VeraCrypt boot loader, original system loader, etc.\n\nWe strongly recommend that you burn the VeraCrypt Rescue Disk. I have no CD/DVD burner but I will store the Rescue Disk ISO image on a removable drive (e.g. USB flash drive). I will connect a CD/DVD burner to my computer later. Terminate the process now. A CD/DVD burner is connected to my computer now. Continue and write the Rescue Disk. Please follow these steps:\n\n1) Connect a removable drive, such as a USB flash drive, to your computer now.\n\n2) Copy the VeraCrypt Rescue Disk image file (%s) to the removable drive.\n\nIn case you need to use the VeraCrypt Rescue Disk in the future, you will be able to connect your removable drive (containing the VeraCrypt Rescue Disk image) to a computer with a CD/DVD burner and create a bootable VeraCrypt Rescue Disk by burning the image to a CD or DVD. IMPORTANT: Note that the VeraCrypt Rescue Disk image file must be written to the CD/DVD as an ISO disk image (not as an individual file). Optager nødhjælps disk Nødhjælps Disk Oprettet System krypterings første test Nødhjælps disk kontrolleret \nVeraCrypt Nødhjælps disk er blevet kontrolleret med succes. Fjern den venligst fra drevet nu og opbevar den på et sikkert sted.\n\nKlik Næste for at fortsætte. ADVARSEL: Under de næste trin må VeraCrypt Nødhjælps Disk ikke være i drevet. Ellers vil det ikke være muligt at gennemføre trinene korrekt.\n\nFjern den venligst fra drevet nu og gem den på et sikkert sted. Klik så på OK. Advarsel: På grund af tekniske begrænsninger i før boot miljøet, vil tekster vist af VeraCrypt i før boot miljøet (dvs. før Windows starter) ikke blive lokaliseret. VeraCrypt Boot Loader bruger interface er helt på Engelsk.\n\nFortsæt? Før kryptering af din system partition eller drev, er det nødvendigt at VeraCrypt kontrollerer at alting virker korrekt.\n\nEfter du klikker på Test, vil alle de nødvendige komponenter (for eksempel, før-boot godkendelses komponent, VeraCrypt Boot Loader) blive installeret og din computerer vil blive genstartet. Så skal du indtaste dit kodeord i VeraCrypt Boot Loader skærmbilledet der kommer frem før Windows starter. Efter Windows er startet, vil du automatisk blive informeret omkring resultetet af denne indledende test.\n\nDen følgende enhed bliver modificeret: Drev #%d\n\n\nHvis du klikker på Fortryd nu, vil ingenting blive indstalleret og den indledende test vil ikke blive udført. IMPORTANT NOTES -- PLEASE READ OR PRINT (click 'Print'):\n\nNote that none of your files will be encrypted before you successfully restart your computer and start Windows. Thus, if anything fails, your data will NOT be lost. However, if something does go wrong, you might encounter difficulties in starting Windows. Therefore, please read (and, if possible, print) the following guidelines on what to do if Windows cannot start after you restart the computer.\n\n What to Do If Windows Cannot Start\n------------------------------------------------\n\nNote: These instructions are valid only if you have not started encrypting.\n\n- If Windows does not start after you enter the correct password (or if you repeatedly enter the correct password but VeraCrypt says that the password is incorrect), do not panic. Restart (power off and on) the computer, and in the VeraCrypt Boot Loader screen, press the Esc key on your keyboard (and if you have multiple systems, choose which to start). Then Windows should start (provided that it is not encrypted) and VeraCrypt will automatically ask whether you want to uninstall the pre-boot authentication component. Note that the previous steps do NOT work if the system partition/drive is encrypted (nobody can start Windows or access encrypted data on the drive without the correct password even if he or she follows the previous steps).\n\n - If the previous steps do not help or if the VeraCrypt Boot Loader screen does not appear (before Windows starts), insert the VeraCrypt Rescue Disk into your CD/DVD drive and restart your computer. If the VeraCrypt Rescue Disk screen does not appear (or if you do not see the 'Repair Options' item in the 'Keyboard Controls' section of the VeraCrypt Rescue Disk screen), it is possible that your BIOS is configured to attempt to boot from hard drives before CD/DVD drives. If that is the case, restart your computer, press F2 or Delete (as soon as you see a BIOS start-up screen), and wait until a BIOS configuration screen appears. If no BIOS configuration screen appears, restart (reset) the computer again and start pressing F2 or Delete repeatedly as soon as you restart (reset) the computer. When a BIOS configuration screen appears, configure your BIOS to boot from the CD/DVD drive first (for information on how to do so, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance). Then restart your computer. The VeraCrypt Rescue Disk screen should appear now. In the VeraCrypt Rescue Disk screen, select 'Repair Options' by pressing F8 on your keyboard. From the 'Repair Options' menu, select 'Restore original system loader'. Then remove the Rescue Disk from your CD/DVD drive and restart your computer. Windows should start normally (provided that it is not encrypted).\n\n Note that the previous steps do NOT work if the system partition/drive is encrypted (nobody can start Windows or access encrypted data on the drive without the correct password even if he or she follows the previous steps).\n\n\nNote that even if you lose your VeraCrypt Rescue Disk and an attacker finds it, he or she will NOT be able to decrypt the system partition or drive without the correct password. Indledende test fuldført The pretest has been successfully completed.\n\nWARNING: Please note that if power supply is suddenly interrupted while encrypting existing data in place, or when the operating system crashes due to a software error or hardware malfunction while VeraCrypt is encrypting existing data in place, portions of the data will be corrupted or lost. Therefore, before you start encrypting, please make sure that you have backup copies of the files you want to encrypt. If you do not, please back up the files now (you can click Defer, back up the files, then run VeraCrypt again anytime, and select 'System' > 'Resume Interrupted Process' to start encrypting).\n\nWhen ready, click Encrypt to start encrypting. You can click Pause or Defer anytime to interrupt the process of encryption or decryption, exit this wizard, restart or shut down your computer, and then resume the process, which will continue from the point it was stopped. To prevent slowdown when the system or applications write or read data from the system drive, VeraCrypt automatically waits until the data is written or read (see Status above) and then automatically continues encrypting or decrypting. \n\nYou can click Pause or Defer anytime to interrupt the process of encryption, exit this wizard, restart or shut down your computer, and then resume the process, which will continue from the point it was stopped. Note that the volume cannot be mounted until it has been fully encrypted. \n\nYou can click Pause or Defer anytime to interrupt the process of decryption, exit this wizard, restart or shut down the computer, and then resume the process, which will continue from the point where it was stopped. Note that the volume cannot be mounted until it has been fully decrypted. Hidden System Started Original System Windows creates (typically, without your knowledge or consent) various log files, temporary files, etc., on the system partition. It also saves the content of RAM to hibernation and paging files located on the system partition. Therefore, if an adversary analyzed files stored on the partition where the original system (of which the hidden system is a clone) resides, he might find out, for example, that you used the VeraCrypt wizard in the hidden-system-creation mode (which might indicate the existence of a hidden operating system on your computer).\n\nTo prevent such issues, VeraCrypt will, in the next steps, securely erase the entire content of the partition where the original system resides. Afterwards, in order to achieve plausible deniability, you will need to install a new system on the partition and encrypt it. Thus you will create the decoy system and the whole process of creation of the hidden operating system will be completed. The hidden operating system has been successfully created. However, before you can start using it (and achieve plausible deniability), you need to securely erase (using VeraCrypt) the entire content of the partition where the currently running operating system is installed. Before you can do that, you need to restart the computer and, in the VeraCrypt Boot Loader screen (which appears before Windows starts), enter the pre-boot authentication password for the hidden operating system. Then, after the hidden system starts, the VeraCrypt wizard will be launched automatically.\n\nNote: If you choose to terminate the process of creation of the hidden operating system now, you will NOT be able to resume the process and the hidden system will NOT be accessible (because the VeraCrypt Boot Loader will be removed). You have scheduled the process of creation of a hidden operating system. The process has not been completed yet. To complete it, you need to restart the computer and, in the VeraCrypt Boot Loader screen (which appears before Windows starts), enter the password for the hidden operating system.\n\nNote: If you choose to terminate the process of creation of the hidden operating system now, you will NOT be able to resume the process. Restart the computer and proceed Permanently terminate the process of creation of the hidden operating system Do nothing now and ask again later \nIF POSSIBLE, PLEASE PRINT THIS TEXT (click 'Print' below).\n\n\nHow and When to Use VeraCrypt Rescue Disk (After Encrypting)\n-----------------------------------------------------------------------------------\n\n I. How to Boot VeraCrypt Rescue Disk\n\nTo boot a VeraCrypt Rescue Disk, insert it into your CD/DVD drive and restart your computer. If the VeraCrypt Rescue Disk screen does not appear (or if you do not see the 'Repair Options' item in the 'Keyboard Controls' section of the screen), it is possible that your BIOS is configured to attempt to boot from hard drives before CD/DVD drives. If that is the case, restart your computer, press F2 or Delete (as soon as you see a BIOS start-up screen), and wait until a BIOS configuration screen appears. If no BIOS configuration screen appears, restart (reset) the computer again and start pressing F2 or Delete repeatedly as soon as you restart (reset) the computer. When a BIOS configuration screen appears, configure your BIOS to boot from the CD/DVD drive first (for information on how to do so, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance). Then restart your computer. The VeraCrypt Rescue Disk screen should appear now. Note: In the VeraCrypt Rescue Disk screen, you can select 'Repair Options' by pressing F8 on your keyboard.\n\n\n II. When and How to Use VeraCrypt Rescue Disk (After Encrypting)\n\n 1) If the VeraCrypt Boot Loader screen does not appear after you start your computer (or if Windows does not boot), the VeraCrypt Boot Loader may be damaged. The VeraCrypt Rescue Disk allows you to restore it and thus to regain access to your encrypted system and data (however, note that you will still have to enter the correct password then). In the Rescue Disk screen, select 'Repair Options' > 'Restore VeraCrypt Boot Loader'. Then press 'Y' to confirm the action, remove the Rescue Disk from your CD/DVD drive and restart your computer.\n\n 2) If you repeatedly enter the correct password but VeraCrypt says that the password is incorrect, the master key or other critical data may be damaged. The VeraCrypt Rescue Disk allows you to restore them and thus to regain access to your encrypted system and data (however, note that you will still have to enter the correct password then). In the Rescue Disk screen, select 'Repair Options' > 'Restore key data'. Then enter your password, press 'Y' to confirm the action, remove the Rescue Disk from your CD/DVD drive, and restart your computer.\n\n 3) If the VeraCrypt Boot Loader is damaged, you can avoid running it by booting directly from the VeraCrypt Rescue Disk. Insert your Rescue Disk into your CD/DVD drive and then enter your password in the Rescue Disk screen.\n\n 4) If Windows is damaged and cannot start, the VeraCrypt Rescue Disk allows you to permanently decrypt the partition/drive before Windows starts. In the Rescue Disk screen, select 'Repair Options' > 'Permanently decrypt system partition/drive'. Enter the correct password and wait until decryption is complete. Then you can e.g. boot your MS Windows setup CD/DVD to repair your Windows installation.\n\n Note: Alternatively, if Windows is damaged (cannot start) and you need to repair it (or access files on it), you can avoid decrypting the system partition/drive by following these steps: If you have multiple operating systems installed on your computer, boot the one that does not require pre-boot authentication. If you do not have multiple operating systems installed on your computer, you can boot a WinPE or BartPE CD/DVD or you can connect your system drive as a secondary or external drive to another computer and then boot the operating system installed on the computer. After you boot a system, run VeraCrypt, click 'Select Device', select the affected system partition, click 'OK', select 'System' > 'Mount Without Pre-Boot Authentication', enter your pre-boot authentication password and click 'OK'. The partition will be mounted as a regular VeraCrypt volume (data will be on-the-fly decrypted/encrypted in RAM on access, as usual).\n\n\n Note that even if you lose your VeraCrypt Rescue Disk and an attacker finds it, he or she will NOT be able to decrypt the system partition or drive without the correct password. \n\nI M P O R T A N T -- PLEASE PRINT THIS TEXT IF POSSIBLE (click 'Print' below).\n\n\nNote: This text will be automatically displayed each time you start the hidden system until you start creating the decoy system.\n\n\n How to Create Decoy System Safely and Securely\n----------------------------------------------------------------------------\n\nIn order to achieve plausible deniability, you need to create the decoy operating system now. To do so, follow these steps:\n\n 1) For security reasons, shut down your computer and leave it powered off for at least several minutes (the longer, the better). This is required to clear the memory, which contains sensitive data. Then turn on the computer but do not boot the hidden system.\n\n 2) Install Windows on the partition whose content has been erased (i.e. on the partition where the original system, of which the hidden system is a clone, was installed).\n\nIMPORTANT: WHEN YOU START INSTALLING THE DECOY SYSTEM, THE HIDDEN SYSTEM WILL *NOT* BE POSSIBLE TO BOOT (because the VeraCrypt Boot Loader will be erased by the Windows system installer). THIS IS NORMAL AND EXPECTED. PLEASE DO NOT PANIC. YOU WILL BE ABLE TO BOOT THE HIDDEN SYSTEM AGAIN AS SOON AS YOU START ENCRYPTING THE DECOY SYSTEM (because VeraCrypt will then automatically install the VeraCrypt Boot Loader on the system drive).\n\nImportant: The size of the decoy system partition must remain the same as the size of the hidden volume (this condition is now met). Moreover, you must not create any partition between the decoy system partition and the partition where the hidden system resides.\n\n 3) Boot the decoy system (which you installed in step 2 and install VeraCrypt on it).\n\nKeep in mind that the decoy system must never contain any sensitive data.\n\n 4) On the decoy system, run VeraCrypt and select 'System' > 'Encrypt System Partition/Drive'. The VeraCrypt Volume Creation Wizard window should appear.\n\nThe following steps apply to the VeraCrypt Volume Creation Wizard.\n\n 5) In the VeraCrypt Volume Creation Wizard, do NOT select the 'Hidden' option. Leave the 'Normal' option selected and click 'Next'.\n\n 6) Select the option 'Encrypt the Windows system partition' and then click 'Next'.\n\n 7) If there are only the hidden system and the decoy system installed on the computer, select the option 'Single-boot' (if there are more than these two systems installed on the computer, select 'Multi-boot'). Then click 'Next'.\n\n 8) IMPORTANT: In this step, FOR THE DECOY SYSTEM, YOU MUST SELECT THE SAME ENCRYPTION ALGORITHM AND HASH ALGORITHM THAT YOU SELECTED FOR THE HIDDEN SYSTEM! OTHERWISE, THE HIDDEN SYSTEM WILL BE INACCESSIBLE! In other words, the decoy system must be encrypted with the same encryption algorithm as the hidden system. Note: The reason is that the decoy system and the hidden system will share a single boot loader, which supports only a single algorithm, selected by the user (for each algorithm, there is a special version of the VeraCrypt Boot Loader).\n\n 9) In this step, choose a password for the decoy operating system. This will be the password that you will be able to reveal to an adversary if you are asked or forced to disclose your pre-boot authentication password (the other password you can reveal is the one for the outer volume). The existence of the third password (i.e. of the pre-boot authentication password for the hidden operating system) will remain secret.\n\nImportant: The password you choose for the decoy system must be substantially different from the one you chose for the hidden volume (i.e. for the hidden operating system).\n\n 10) Follow the remaining instructions in the wizard so as to encrypt the decoy operating system.\n\n\n\n After Decoy System Is Created\n------------------------------------------------\n\nAfter you encrypt the decoy system, the whole process of creation of the hidden operating system will be completed and you will be able to use these three passwords:\n\n1) Pre-boot authentication password for the hidden operating system.\n\n2) Pre-boot authentication password for the decoy operating system.\n\n3) Password for the outer volume.\n\n If you want to start the hidden operating system, you will just need to enter the password for the hidden operating system in the VeraCrypt Boot Loader screen (which appears after you turn on or restart your computer).\n\nIf you want to start the decoy operating system, you will just need to enter the password for the decoy operating system in the VeraCrypt Boot Loader screen.\n\nThe password for the decoy system can be disclosed to anyone forcing you to reveal your pre-boot authentication password. The existence of the hidden volume (and of the hidden operating system) will remain secret.\n\n The third password (for the outer volume) can be disclosed to anyone forcing you to reveal the password for the first partition behind the system partition, where both the outer volume and the hidden volume (containing the hidden operating system) reside. The existence of the hidden volume (and of the hidden operating system) will remain secret.\n\n\n If you revealed the password for the decoy system to an adversary and he asked you why the free space of the (decoy) system partition contains random data, you could answer, for example: "The partition previously contained a system encrypted by VeraCrypt, but I forgot the pre-boot authentication password (or the system was damaged and stopped booting), so I had to reinstall Windows and encrypt the partition again."\n\n\n If all the instructions are followed and if the precautions and requirements listed in the section "Security Requirements and Precautions Pertaining to Hidden Volumes" in the VeraCrypt User's Guide are followed, it should be impossible to prove that the hidden volume and hidden operating system exist, even when the outer volume is mounted or when the decoy operating system is decrypted or started.\n\nIf you save a copy of this text or print it (strongly recommended, unless your printer stores copies of documents it prints on its internal drive), you should destroy any copies of it after you have created the decoy system and after you have understood all the information contained in the text (otherwise, if such a copy was found, it might indicate that there is a hidden operating system on this computer).\n\n WARNING: IF YOU DO NOT PROTECT THE HIDDEN VOLUME (for information on how to do so, refer to the section "Protection of Hidden Volumes Against Damage" in the VeraCrypt User's Guide), DO NOT WRITE TO THE OUTER VOLUME (note that the decoy operating system is NOT installed in the outer volume). OTHERWISE, YOU MAY OVERWRITE AND DAMAGE THE HIDDEN VOLUME (AND THE HIDDEN OPERATING SYSTEM WITHIN IT)! Operating System Cloning In the next steps, VeraCrypt will create the hidden operating system by copying the content of the system partition to the hidden volume (data being copied will be encrypted on the fly with an encryption key different from the one that will be used for the decoy operating system).\n\nPlease note that the process will be performed in the pre-boot environment (before Windows starts) and it may take a long time to complete; several hours or even several days (depending on the size of the system partition and on the performance of your computer).\n\nYou will be able to interrupt the process, shut down your computer, start the operating system and then resume the process. However, if you interrupt it, the entire process of copying the system will have to start from the beginning (because the content of the system partition must not change during cloning). Ønsker du at afbryde hele processen med at oprette det skjulte operativsystem?\n\nBemærk: Du vil IKKE være i stand til at fortsætte processen hvis du afbryder nu. Ønsker du at afbryde system krypteringens indledende test? The VeraCrypt system encryption pretest failed. Do you want to try again?\n\nIf you select 'No', the pre-boot authentication component will be uninstalled.\n\nNotes:\n\n- If the VeraCrypt Boot Loader did not ask you to enter the password before Windows started, it is possible that your operating system does not boot from the drive on which it is installed. This is not supported.\n\n- If you used an encryption algorithm other than AES and the pretest failed (and you entered the password), it may have been caused by an inappropriately designed driver. Select 'No', and try encrypting the system partition/drive again, but use the AES encryption algorithm (which has the lowest memory requirements).\n\n- For more possible causes and solutions, see: https://www.veracrypt.fr/en/Troubleshooting.html System partition/drev ser ikke ud til at være krypteret (hverken delvist eller helt). Det system partition/drev er krypteret (delvist eller helt).\n\nDekrypter venligst dit system partition/drev helt før du fortsætter. For at gøre dette, vælg 'System' > 'Dekrypter System Partition/Drev Permanent' fra menulinien i VeraCrypt hovedvinduet. When the system partition/drive is encrypted (partially or fully), you cannot downgrade VeraCrypt (but you can upgrade it or reinstall the same version). Dit system partition/drev bliver nu krypteret, dekrypteret, eller ændret på anden måde. Afbryd venligst kryptering/dekryptering/modifikations processen (eller vent til den er fuldført) før du fortsætter. Et eksemplar af VeraCrypt Bind Oprettelsesguide kører nu på systemet og udfører eller forbereder kryptering/dekryptering af system partition/drev. Før du fortsætter, vent venligst på det afslutter eller luk det. Hvis du ikke kan lukke det, genstart venligst din computer før du fortsætter. Processen med kryptering eller dekryptering af system partition/drev er ikke fuldført. Vent venligst indtil det er fuldført før du fortsætter. Fejl: Krypteringsproces på partition/drev er ikke fuldført. Det skal færdiggøres først. Error: The process of encryption of the partition/volume has not been completed. It must be completed first.\n\nNote: To resume the process, select 'Volumes' > 'Resume Interrupted Process' from the menu bar of the main VeraCrypt window. Kodeordet er korrekt, VeraCrypt har dekrypteret bind etiketten med succes og detekteret at dette bind er et skjult system bind. Du kan dog ikke ændre etiketten på et skjult system bind på denne måde.\n\nFor at ændre kodeord på et skjult system bind, boot operativsystemet der ligger i det skjulte bind, og vælg da 'System' > 'Ændre kodeord' fra menulinien i hoved VeraCrypt vinduet.\n\nFor at vælge etiket nøgle oprindelses algoritme, boot op på det skjulte operativsystem og vælg da 'System' > 'Indstil etiket nøgle oprindelses algoritme'. VeraCrypt supporterer ikke på-stedet dekryptering af en skjult system partition.\n\nBemærk: Hvis du ønsker at dekryptere aflednings system partitionen, boot op på aflednings systemet, og vælg da 'System' > 'Dekrypter System Partition/Drev permanent' fra menulinien i hoved VeraCrypt vinduet. Fejl: Ukorrect/ugyldig parameter. Du har valgt en partition eller enhed men oprettelsesguide tilstanden du har valgt er kun passende til fil beholdere.\n\nØnsker du at ændre oprettelsesguide tilstand? Ønsker du at oprette en VeraCrypt fil beholder istedet? You have selected the system partition/drive (or the boot partition), but the wizard mode you selected is suitable only for non-system partitions/drives.\n\nDo you want to set up pre-boot authentication (which means that you will need to enter your password each time before Windows boots/starts) and encrypt the system partition/drive? Er du sikker på du ønsker at dekryptere system partition/drev permanent? FORSIGTIG: Hvis du dekrypterer system partition/drev permantent, vil ukrypteret data blive skrevet der til.\n\nEr du helt sikker på du vil dekryptere system partition/drev permanent? Are you sure you want to permanently decrypt the following volume? CAUTION: If you permanently decrypt the VeraCrypt volume, unencrypted data will be written to the disk.\n\nAre you really sure you want to permanently decrypt the selected volume? Warning: If you use a cascade of ciphers for system encryption, you may encounter the following issues:\n\n1) The VeraCrypt Boot Loader is larger than normal and, therefore, there is not enough space in the first drive track for a backup of the VeraCrypt Boot Loader. Hence, whenever it gets damaged (which often happens, for example, during inappropriately designed anti-piracy activation procedures of certain programs), you will need to use the VeraCrypt Rescue Disk to boot or to repair the VeraCrypt Boot Loader.\n\n2) On some computers, resuming from hibernation takes longer.\n\nThese potential issues can be prevented by choosing a non-cascade encryption algorithm (e.g. AES).\n\nAre you sure you want to use a cascade of ciphers? Hvis du oplever nogle af de tidligere beskrevne problemer, dekrypter partition/drev (hvis det er krypteret) og prøv så at kryptere det igen ved brug af en ikke-kaskade krypterings algorithme (f.eks. AES). WARNING: For safety and security reasons, you should update VeraCrypt on the decoy operating system before you update it on the hidden operating system.\n\nTo do so, boot the decoy system and run the VeraCrypt installer from within it. Then boot the hidden system and run the installer from within it as well.\n\nNote: The decoy system and the hidden system share a single boot loader. If you upgraded VeraCrypt only on the hidden system (but not on the decoy system), the decoy system would contain a VeraCrypt driver and VeraCrypt applications whose version numbers are different from the version number of the VeraCrypt Boot Loader. Such a discrepancy might indicate that there is a hidden operating system on this computer.\n\n\nDo you want to continue? Versions nummeret på den VeraCrypt Boot Loader der bootede dette operativsystem er forskellig fra det versions nummer på den VeraCrypt driver (og VeraCrypt applikationer) der er installeret på dette system.\n\nDu bør køre VeraCrypt installering (med det samme versions nummer som VeraCrypt Boot Loader) for at opdatere VeraCrypt på dette operativsystem. The version number of the VeraCrypt Boot Loader that booted this operating system is different from the version number of the VeraCrypt driver (and of the VeraCrypt applications) installed on this system. Note that older versions may contain bugs fixed in later versions.\n\nIf you did not boot from the VeraCrypt Rescue Disk, you should reinstall VeraCrypt or upgrade it to the latest stable version (the boot loader will be updated too).\n\nIf you booted from the VeraCrypt Rescue Disk, you should update it ('System' > 'Create Rescue Disk'). VeraCrypt Boot Loader er blevet opgraderet.\n\nDet anbefales kraftigt at du opretter en ny VeraCrypt Nødhjælps Disk (som vil indeholde den nye version af VeraCrypt Boot Loader) ved at vælge 'System' > 'Opret Nødhjælps Disk' efter du har genstartet din computer. VeraCrypt Boot Loader er blevet opgraderet.\n\nDet anbefales kraftigt at du booter aflednings operativsystemet og så opretter en ny VeraCrypt Nødhjælps Disk (som vil indeholde den nye version af VeraCrypt Boot Loader) ved at vælge 'System' > 'Opret Nødhjælps Disk'. Fejl i opgradering af VeraCrypt Boot Loader. VeraCrypt failed to detect the real size of the system drive and, therefore, the size reported by the operating system (which may be smaller than the real size) will be used. Also note that this is not a bug in VeraCrypt. ADVARSEL: Det ser ud til at VeraCrypt allerede har forsøgt at detektere skjulte sektorer på dette system drev. Hvis du oplevede nogen problemer under den tidligere detektions proces, kan du undgå disse problemer ved at undlade detektion af skjulte sektorer nu. Bemærk at hvis du gør dette, vil VeraCrypt bruge størrelsen oplyst af operativsystemet (hvilket kan være mindre end den reelle størrelse på drevet).\n\nBemærk at dette problem ikke er forårsaget af en fejl i VeraCrypt. Undlad detektion af skjulte sektorer (brug størrelsen oplyst af operativsystemet) Forsøg at detektere skjulte sektorer igen Error: Content of one or more sectors on the disk cannot be read (probably due to a physical defect).\n\nThe process of in-place encryption can continue only when the sectors have been made readable again. VeraCrypt can attempt to make these sectors readable by writing zeros to the sectors (subsequently such all-zero blocks would be encrypted). However, note that any data stored in the unreadable sectors will be lost. If you want to avoid that, you can attempt to recover portions of the corrupted data using appropriate third-party tools.\n\nNote: In case of physically damaged sectors (as opposed to mere data corruption and checksum errors) most types of storage devices internally reallocate the sectors when data is attempted to be written to them (so the existing data in the damaged sectors may remain unencrypted on the drive).\n\nDo you want VeraCrypt to write zeroes to unreadable sectors? Error: Content of one or more sectors on the disk cannot be read (probably due to a physical defect).\n\nTo be able to proceed with decryption, VeraCrypt will have to discard the content of the unreadable sectors (the content will be replaced with pseudorandom data). Please note that, before proceeding, you can attempt to recover portions of any corrupted data using appropriate third-party tools.\n\nDo you want VeraCrypt to discard data in the unreadable sectors now? Note: VeraCrypt has replaced the content of %I64d unreadable sectors (%s) with encrypted all-zero plaintext blocks. Note: VeraCrypt has replaced the content of %I64d unreadable sectors (%s) with pseudorandom data. Enter password/PIN for token '%s': In order to allow VeraCrypt to access a security token or smart card, you need to install a PKCS #11 software library for the token or smart card first. Such a library may be supplied with the device or it may be available for download from the website of the vendor or other third parties.\n\nAfter you install the library, you can either select it manually by clicking 'Select Library' or you can let VeraCrypt find and select it automatically by clicking 'Auto-Detect Library' (only the Windows system directory will be searched). Note: For the filename and location of the PKCS #11 library installed for your security token or smart card, please refer to the documentation supplied with the token, card, or third-party software.\n\nClick 'OK' to select the path and filename. In order to allow VeraCrypt to access a security token or smart card, you need to select a PKCS #11 software library for the token/card first. To do so, select 'Settings' > 'Security Tokens'. Failed to initialize PKCS #11 security token library.\n\nPlease make sure the specified path and filename refer to a valid PKCS #11 library. To specify a PKCS #11 library path and filename, select 'Settings' > 'Security Tokens'. No PKCS #11 library has been found in the Windows system directory.\n\nPlease make sure that a PKCS #11 library for your security token (or for your smart card) is installed (such a library may be supplied with the token/card or it may be available for download from the website of the vendor or other third parties). If it is installed in a directory other than the Windows system directory, click 'Select Library' to locate the library (e.g. in the folder where the software for the token/card is installed). No security token found.\n\nPlease make sure your security token is connected to your computer and the correct device driver for your token is installed. Security token keyfile not found. A security token keyfile with the same name already exists. Do you want to delete the selected files? Security token keyfile path is invalid. Security token error Password for security token is incorrect. The security token does not have enough memory/space to perform the requested operation.\n\nIf you are attempting to import a keyfile, you should select a smaller file or use a keyfile generated by VeraCrypt (select 'Tools' > 'Keyfile Generator'). All open security token sessions have been closed. Select Security Token Keyfiles Slot Token name File name IMPORTANT: Please note that pre-boot authentication passwords are always typed using the standard US keyboard layout. Therefore, a volume that uses a password typed using any other keyboard layout may be impossible to mount using a pre-boot authentication password (note that this is not a bug in VeraCrypt). To allow such a volume to be mounted using a pre-boot authentication password, follow these steps:\n\n1) Click 'Select File' or 'Select Device' and select the volume.\n2) Select 'Volumes' > 'Change Volume Password'.\n3) Enter the current password for the volume.\n4) Change the keyboard layout to English (US) by clicking the Language bar icon in the Windows taskbar and selecting 'EN English (United States)'.\n5) In VeraCrypt, in the field for the new password, type the pre-boot authentication password.\n6) Confirm the new password by retyping it in the confirmation field and click 'OK'.\nWARNING: Please keep in mind that if you follow these steps, the volume password will always have to be typed using the US keyboard layout (which is automatically ensured only in the pre-boot environment). System favorite volumes will be mounted using the pre-boot authentication password. If any system favorite volume uses a different password, it will not be mounted. Please note that if you need to prevent normal VeraCrypt volume actions (such as 'Dismount All', auto-dismount, etc.) from affecting system favorite volumes, you should enable the option 'Allow only administrators to view and dismount system favorite volumes in VeraCrypt'. In addition, when VeraCrypt is run without administrator privileges (the default on Windows Vista and later), system favorite volumes will not be displayed in the drive letter list in the main VeraCrypt application window. IMPORTANT: Please keep in mind that if this option is enabled and VeraCrypt does not have administrator privileges, mounted system favorite volumes are NOT displayed in the VeraCrypt application window and they cannot be dismounted. Therefore, if you need e.g. to dismount a system favorite volume, please right-click the VeraCrypt icon (in the Start menu) and select 'Run as administrator' first. The same limitation applies to the 'Dismount All' function, 'Auto-Dismount' functions, 'Dismount All' hot keys, etc. Note that this setting takes effect only after the operating system is restarted. Error while parsing command line. Nødhjælps Disk Select &File and Mount... Select &Device and Mount... Allow only administrators to view and dismount system favorite volumes in VeraCrypt Mount system favorite volumes when Windows starts (in the initial phase of the startup procedure) Warning: The filesystem on the volume mounted as '%s' was not cleanly dismounted and thus may contain errors. Using a corrupted filesystem can cause data loss or data corruption.\n\nNote: Before you physically remove or switch off a device (such as a USB flash drive or an external hard drive) where a mounted VeraCrypt volume resides, you should always dismount the VeraCrypt volume in VeraCrypt first.\n\n\nDo you want Windows to attempt to detect and fix errors (if any) on the filesystem? Warning: One or more system favorite volumes were not cleanly dismounted and thus may contain filesystem errors. Please see the system event log for further details.\n\nUsing a corrupted filesystem can cause data loss or data corruption. You should check the affected system favorite volume(s) for errors (right-click each of them in VeraCrypt and select 'Repair Filesystem'). Warning: Repairing a damaged filesystem using the Microsoft 'chkdsk' tool might cause loss of files in damaged areas. Therefore, it is recommended that you first back up the files stored on the VeraCrypt volume to another, healthy, VeraCrypt volume.\n\nDo you want to repair the filesystem now? Volume '%s' has been mounted as read-only because write access was denied.\n\nPlease make sure the security permissions of the file container allow you to write to it (right-click the container and select Properties > Security).\n\nNote that, due to a Windows issue, you may see this warning even after setting the appropriate security permissions. This is not caused by a bug in VeraCrypt. A possible solution is to move your container to, e.g., your 'Documents' folder.\n\nIf you intend to keep your volume read-only, set the read-only attribute of the container (right-click the container and select Properties > Read-only), which will suppress this warning. Volume '%s' had to be mounted as read-only because write access was denied.\n\nPlease make sure no other application (e.g. antivirus software) is accessing the partition/device on which the volume is hosted. Volume '%s' has been mounted as read-only because the operating system reported the host device to be write-protected.\n\nPlease note that some custom chipset drivers have been reported to cause writable media to falsely appear write-protected. This problem is not caused by VeraCrypt. It may be solved by updating or uninstalling any custom (non-Microsoft) chipset drivers that are currently installed on this system. Note that the Hyper-Threading technology provides multiple logical cores per a single physical core. When Hyper Threading is enabled, the number selected above represents the number of logical processors/cores. %d threads Note that hardware-accelerated AES is disabled, which will affect benchmark results (worse performance).\n\nTo enable hardware acceleration, select 'Settings' > 'Performance' and enable the corresponding option. Note that the number of threads is currently limited, which will affect benchmark results (worse performance).\n\nTo utilize the full potential of the processor(s), select 'Settings' > 'Performance' and disable the corresponding option. Do you want VeraCrypt to attempt to disable write protection of the partition/drive? WARNING: This setting may degrade performance.\n\nAre you sure you want to use this setting? Warning: VeraCrypt volume auto-dismounted Before you physically remove or turn off a device containing a mounted volume, you should always dismount the volume in VeraCrypt first.\n\nUnexpected spontaneous dismount is usually caused by an intermittently failing cable, drive (enclosure), etc. This volume was created with TrueCrypt %x.%x but VeraCrypt supports only TrueCrypt volumes created with TrueCrypt 6.x/7.x series Test Nøglefil Backspace Tab Clear Retur Pause Caps Lock Mellemrum Page Up Page Down End Home Pil Venstre Pil Op Pil Højre Pil Ned Vælg Tast Print Tast Execute Tast Print Skærm Insert Delete Applikations Tast Sleep Num Lock Scroll Lock Stifinder Tilbage Stifinder Frem Stifinder Opdater Stifinder Stop Stifinder Søg Stifinder Favoritter Stifinder Hjem Lydløs Volume Ned Volume Op Næste Spor Forrige Spor Stop Medie Afspil/Pause Medie Åbn Post Tast Vælg Medie Tast Applikation 1 Applikation 2 Attn CrSel ExSel Afspil Zoom Numerisk Shift Ctrl Alt Win B KB MB GB TB PB B/s KB/s MB/s GB/s TB/s PB/s … Include &PIM when caching pre-boot authentication password Include PIM when caching a password Make disconnected network drives available for mounting The entered password is too long: its UTF-8 representation exceeds %d bytes. The entered password contains Unicode characters that couldn't be converted to UTF-8 representation. Error: Failed to load a system library. The volume file size specified in the command line is incompatible with selected exFAT filesystem. Randomness Collected From Mouse Movements Volume ID: Volume ID Use Volume ID to mount favorite The Volume ID value is invalid No Volume with the specified ID was found on the system Copy Value to Clipboard... Do not request PIM in the pre-boot authentication screen (PIM value is stored unencrypted on disk) WARNING: Please keep in mind that if you enable this option, the PIM value will be stored unencrypted on the disk.\n\nAre you sure you want to enable this option? Personal Iterations Multiplier (PIM) maximum value is 2147468. Skip Rescue Disk verification Don't show wait message dialog when performing operations Do not request Hash algorithm in the pre-boot authentication screen Kuznyechik is a block cipher first published in 2015 and defined in the National Standard of the Russian Federation GOST R 34.12-2015 and also in RFC 7801. 256-bit key, 128-bit block. Mode of operation is XTS. Jointly developed by Mitsubishi Electric and NTT of Japan. First published on 2000. 256-bit key, 128-bit block. Mode of operation is XTS. It has been approved for use by the ISO/IEC, the European Union's NESSIE project and the Japanese CRYPTREC project. Tid Iterations Pre-Boot Before you can encrypt the partition, you must create a VeraCrypt Rescue Disk (VRD), which serves the following purposes:\n\n- If the VeraCrypt Boot Loader, master key, or other critical data gets damaged, the VRD allows you to restore it (note, however, that you will still have to enter the correct password then).\n\n- If Windows gets damaged and cannot start, the VRD allows you to permanently decrypt the partition before Windows starts.\n\n- The VRD will contain a backup of the present EFI boot loader and will allow you to restore it if necessary.\n\nThe VeraCrypt Rescue Disk ZIP image will be created in the location specified below. The Rescue Disk ZIP image has been created and stored in this file:\n%s\n\nNow you need to extract it to a USB stick that is formatted as FAT/FAT32.\n\n%lsAfter you create the Rescue Disk, click Next to verify that it has been correctly created. The Rescue Disk ZIP image has been created and stored in this file:\n%s\n\nNow you should either extract the image to a USB stick that is formatted as FAT/FAT32 or move it to a safe location for later use.\n\n%lsClick Next to continue. IMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\n Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk, please eject and reinsert the USB stick; then click Next to try again. If this does not help, please try another USB stick and/or another ZIP software.\n\nIf you have not extracted the Rescue Disk yet, please do so, and then click Next.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created before you started this wizard, please note that such Rescue Disk cannot be used, because it was created for a different master key. You need to extract the newly generated Rescue Disk ZIP image. Cannot verify that the Rescue Disk has been correctly extracted.\n\nIf you have extracted the Rescue Disk image to a USB stick, please eject it and reinsert it; then try again. If this does not help, please try other ZIP software and/or medium.\n\nIf you attempted to verify a VeraCrypt Rescue Disk created for a different master key, password, salt, etc., please note that such Rescue Disk will always fail this verification. To create a new Rescue Disk fully compatible with your current configuration, select 'System' > 'Create Rescue Disk'. The Rescue Disk image has been created and stored in this file:\n%s\n\nNow you need to extract the Rescue Disk image to a USB stick that is formatted as FAT/FAT32.\n\nIMPORTANT: Note that the zip file must be extracted directly to the root of the USB stick. For example, if the drive letter of the USB stick is E: then extracting the zip file should create a folder E:\\EFI on the USB stick.\n\nAfter you create the Rescue Disk, select 'System' > 'Verify Rescue Disk' to verify that it has been correctly created. Use Secure Desktop for password entry The volume file size specified in the command line is incompatible with selected ReFS filesystem. Edit Boot Loader Configuration Display EFI Platform Information Boot Loader Configuration File EFI Platform Information WARNING: Inexperienced users should never attempt to manually edit boot loader configurations.\n\nContinue? WARNING: Failed to validate the XML format of the Boot Loader configuration. Please check your modifications. Advanced Options It is strongly recommended that you create a new VeraCrypt Rescue Disk (which will contain the new version of the VeraCrypt Boot Loader) by selecting 'System' > 'Create Rescue Disk'.\nDo you want to do it now? Allow TRIM command for non-system SSD partition/drive Block TRIM command on system partition/drive ERROR: Windows EFI system loader could not be located on the disk. Operation will be aborted. It is currently not possible to encrypt a system if SecureBoot is enabled and if VeraCrypt custom keys are not loaded into the machine firmware. SecureBoot needs to be disabled in the BIOS configuration in order to allow system encryption to proceed. Pasted text truncated because the password maximum length is %d characters Password already reached its maximum length of %d characters.\nNo additional character is allowed. Vælg det sprog der skal vises under installationen: ERROR: The size of the file container is larger than the available free space on disk. Allow Windows Disk Defragmenter to defragment non-system partition/drive WARNING: Defragmenting non-system partitions/drives may leak metadata about their content or cause issues with hidden volumes they may contain.\n\nContinue? Virtual Device The selected mounted volume is not associated with its drive letter in Windows and so it can not be opened in Windows Explorer. Clear encryption keys from memory if a new device is inserted IMPORTANT NOTES:\n - Please keep in mind that this option will not persist after a shutdown/reboot so you will need to select it again next time the machine is started.\n\n - With this option enabled and after a new device is connected, the machine will freeze and it will eventually crash with a BSOD since Windows can not access the encrypted disk after its keys are cleared from memory.\n Starting Use CPU hardware random generator as an additional source of entropy Use legacy maximum password length (64 characters) Activate encryption of keys and passwords stored in RAM Benchmark: Only create virtual device without mounting on selected drive letter The entered password is too long: its UTF-8 representation exceeds 64 bytes. The Hidden volume can't have the same password, PIM and keyfiles as the Outer volume VeraCrypt does not support encrypting a system drive that is already encrypted by BitLocker. Automatically fix boot configuration issues that may prevent Windows from starting Force machine to boot on VeraCrypt in the next startup Force the presence of VeraCrypt entry in the EFI firmware boot menu Force VeraCrypt entry to be the first in the EFI firmware boot menu WARNING: RAM encryption is not compatible with Windows Hibernate and Windows Fast Startup features. VeraCrypt needs to disable them before activating RAM encryption.\n\nContinue? WARNING: Windows Fast Startup is enabled and it is known to cause issues when working with VeraCrypt volumes. It is advised to disable it for better security and usability.\n\nDo you want to disable Windows Fast Startup? In order to enable your operating system to mount your new volume, it has to be formatted with a filesystem. Please select a filesystem type.\n\nIf your volume is going to be hosted on a device or partition, you can use 'Quick format' to skip encryption of free space of the volume. Do not accelerate AES encryption/decryption by using the AES instructions of the processor Add All Mounted Volumes to Favorites... Task Icon Menu Items Open Mounted Volumes Dismount Mounted Volumes Free space available: {0} Please specify the size of the container to create. Note that the minimum possible size of a volume is 292 KiB. WARNING: You have selected a filesystem other than FAT for the outer volume.\nPlease Note that in this case VeraCrypt can't calculate the exact maximum allowed size for the hidden volume and it will use only an estimation that can be wrong.\nThus, it is your responsibility to use an adequate value for the size of the hidden volume so that it does not overlap the outer volume.\n\nDo you want to continue using the selected filesystem for the outer volume? Security Mount Options Background Task System Integration Filesystem Explorer Performance Keyfiles Security Tokens Kernel Services Do not use kernel cryptographic services Filesystem Mount options: Cross-Platform Support I will mount the volume on other platforms Choose this option if you need to use the volume on other platforms. I will mount the volume only on {0} Choose this option if you do not need to use the volume on other platforms. Deselect Enter your user password or administrator password: Administrator privileges required VeraCrypt is already running. System Encryption password is longer than {0} characters. Mount partition &using system encryption (preboot authentication) Do &not mount Mount at directory: Se&lect... Dismount All Volumes When System is entering power saving mode Actions to Perform when User Logs On Close all Explorer windows of volume being dismounted Hotkeys System-Wide Hotkeys Play system notification sound after mount/dismount Display confirmation message box after dismount VeraCrypt quits Open Finder window for successfully mounted volume Please note that this setting takes effect only if use of the kernel cryptographic services is disabled. Disabling the use of kernel cryptographic services can degrade performance.\n\nAre you sure? Please note that disabling this option may have no effect on volumes mounted using kernel cryptographic services. Please note that any currently mounted volumes need to be remounted before they can use this setting. Unknown exception occurred. "Disk Utility will be launched after you press 'OK'.\n\nPlease select your volume in the Disk Utility window and press 'Verify Disk' or 'Repair Disk' button on the 'First Aid' page. Mount All Devices Error while loading configuration files located in Please select a free drive slot from the list. \n\nDo you want to show this message next time you mount such a volume? Warning Error This feature is currently supported only in text mode. Free space on drive {0}: is {1}. Please note that if your operating system does not allocate files from the beginning of the free space, the maximum possible hidden volume size may be much smaller than the size of the free space on the outer volume. This is not a bug in VeraCrypt but a limitation of the operating system. Maximum possible hidden volume size for this volume is {0}. Open Outer Volume Outer volume has been successfully created and mounted as '{0}'. To this volume you should now copy some sensitive-looking files that you actually do NOT want to hide. The files will be there for anyone forcing you to disclose your password. You will reveal only the password for this outer volume, not for the hidden one. The files that you really care about will be stored in the hidden volume, which will be created later on. When you finish copying, click Next. Do not dismount the volume.\n\nNote: After you click Next, the outer volume will be analyzed to determine the size of uninterrupted area of free space whose end is aligned with the end of the volume. This area will accommodate the hidden volume, so it will limit its maximum possible size. The procedure ensures no data on the outer volume are overwritten by the hidden volume. Error: You are trying to encrypt a system drive.\n\nVeraCrypt can encrypt a system drive only under Windows. Error: You are trying to encrypt a system partition.\n\nVeraCrypt can encrypt system partitions only under Windows. WARNING: Formatting of the device will destroy all data on filesystem '{0}'.\n\nDo you want to continue? The filesystem of the selected device is currently mounted. Please dismount '{0}' before proceeding. The Hidden volume can't have the same password, PIM and keyfiles as the Outer volume Please note that the volume will not be formatted with a FAT filesystem and, therefore, you may be required to install additional filesystem drivers on platforms other than {0}, which will enable you to mount the volume. Error: The hidden volume to be created is larger than {0} TB ({1} GB).\n\nPossible solutions:\n- Create a container/partition smaller than {0} TB.\n - Use a drive with 4096-byte sectors to be able to create partition/device-hosted hidden volumes up to 16 TB in size .\n (not supported by components available on this platform).\n Your system uses an old version of the Linux kernel.\n\nDue to a bug in the Linux kernel, your system may stop responding when writing data to a VeraCrypt volume. This problem can be solved by upgrading the kernel to version 2.6.24 or later. Volume {0} has been dismounted. Volume {0} has been mounted. Out of memory. Failed to obtain administrator privileges Command {0} returned error {1}. VeraCrypt Command Line Help \n\nWarning: Hidden files are present in a keyfile path. If you need to use them as keyfiles, remove the leading dot from their filenames. Hidden files are visible only if enabled in system options. Storage device and VC volume sector size mismatch This operation must be performed only when the system hosted on the volume is running. Not enough data available. Kernel cryptographic service test failed. The cryptographic service of your kernel most likely does not support volumes larger than 2 TB.\n\nPossible solutions:\n- Upgrade the Linux kernel to version 2.6.33 or later.\n- Disable use of the kernel cryptographic services (Settings > Preferences > System Integration) or use 'nokernelcrypto' mount option on the command line. Failed to set up a loop device. A required argument is missing. Volume data missing. Mount point required. Mount point is already in use. No password or keyfile specified. \n\nNote that pre-boot authentication passwords need to be typed in the pre-boot environment where non-US keyboard layouts are not available. Therefore, pre-boot authentication passwords must always be typed using the standard US keyboard layout (otherwise, the password will be typed incorrectly in most cases). However, note that you do NOT need a real US keyboard; you just need to change the keyboard layout in your operating system. \n\nNote: If you are attempting to mount a partition located on an encrypted system drive without pre-boot authentication or to mount the encrypted system partition of an operating system that is not running, you can do so by selecting 'Options >' > 'Mount partition using system encryption'. Password is longer than {0} characters. Partition device required. Incorrect password to the protected hidden volume or the hidden volume does not exist. Incorrect keyfile(s) and/or password to the protected hidden volume or the hidden volume does not exist. Invalid characters encountered. Error while parsing formatted string. Failed to create a file or directory in a temporary directory.\n\nPlease make sure that the temporary directory exists, its security permissions allow you to access it, and there is sufficient disk space. Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, outer volumes hosted on the drive cannot be mounted using hidden volume protection.\n\nPossible solutions:\n- Use a drive with 512-byte sectors.\n- Create a file-hosted volume (container) on the drive.\n- Backup the contents of the hidden volume and then update the outer volume. Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes on the drive can only be mounted using kernel cryptographic services.\n\nPossible solutions:\n- Enable use of the kernel cryptographic services (Preferences > System Integration).\n- Use a drive with 512-byte sectors.\n- Create a file-hosted volume (container) on the drive. Error: The drive uses a sector size other than 512 bytes.\n\nDue to limitations of components available on your platform, partition/device-hosted volumes cannot be created/used on the drive.\n\nPossible solutions:\n- Create a file-hosted volume (container) on the drive.\n- Use a drive with 512-byte sectors.\n- Use VeraCrypt on another platform. The host file/device is already in use. Volume slot unavailable. VeraCrypt requires OSXFUSE 2.5 or above. Exception occurred Enter password Enter VeraCrypt Volume Password Mount Mount Directory No volumes mounted. Specify a New VeraCrypt Volume Parameter incorrect Select Keyfiles Start VeraCrypt The volume {0} is already mounted. Unknown option Volume Location WARNING: The host file/device {0} is already in use!\n\nIgnoring this can cause undesired results including system instability. All applications that might be using the host file/device should be closed before mounting the volume.\n\nContinue mounting? VeraCrypt was previously installed using an MSI package and so it can't be updated using the standard installer.\n\nPlease use the MSI package to update your VeraCrypt installation. Use all available free space VeraCrypt cannot be upgraded because the system partition/drive was encrypted using an algorithm that is not supported anymore.\nPlease decrypt your system before upgrading VeraCrypt and then encrypt it again. Supported terminal application could not be found, you need either xterm, konsole or gnome-terminal (with dbus-x11). Mount Without Cache :: VeraCrypt Expander ::\n\nExpand a VeraCrypt volume on the fly without reformatting\n\n\nAll kind of volumes (container files, disks and partitions) formatted with NTFS are supported. The only condition is that there must be enough free space on the host drive or host device of the VeraCrypt volume.\n\nDo not use this software to expand an outer volume containing a hidden volume, because this destroys the hidden volume!\n 1. Select the VeraCrypt volume to be expanded\n2. Click the 'Mount' button Volume: File system: Current size: New size: Enter new volume size Fill new space with random data Quick Expand Fill new space: %s free space available on host drive This is a device-based VeraCrypt volume.\n\nThe new volume size will be choosen automatically as the size of the host device. Please specify the new size of the VeraCrypt volume (must be at least %I64u KB larger than the current size). WARNING: You should use Quick Expand only in the following cases:\n\n1) The device where the file container is located contains no sensitive data and you do not need plausible deniability.\n2) The device where the file container is located has already been securely and fully encrypted.\n\nAre you sure you want to use Quick Expand? IMPORTANT: Move your mouse as randomly as possible within this window. The longer you move it, the better. This significantly increases the cryptographic strength of the encryption keys. Then click 'Continue' to expand the volume. Click 'Continue' to expand the volume. Error: volume expansion failed. Error: operation aborted by user. Finished. Volume successfully expanded. Warning: Volume expansion is in progress!\n\nStopping now may result in a damaged volume.\n\nDo you really want to cancel? Starting volume expansion ...\n An outer volume containing a hidden volume can't be expanded, because this destroys the hidden volume.\n A VeraCrypt system volume can't be expanded. Not enough free space to expand the volume Warning: The container file is larger than the VeraCrypt volume area. The data after the VeraCrypt volume area will be overwritten.\n\nDo you want to continue? Warning: The VeraCrypt volume contains a FAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue? Warning: The VeraCrypt volume contains an exFAT file system!\n\nOnly the VeraCrypt volume itself will be expanded, but not the file system.\n\nDo you want to continue? Warning: The VeraCrypt volume contains an unknown or no file system!\n\nOnly the VeraCrypt volume itself will be expanded, the file system remains unchanged.\n\nDo you want to continue? New volume size too small, must be at least %I64u kB larger than the current size. New volume size too large, not enough space on host drive. Maximum file size of %I64u MB on host drive exceeded. Error: Failed to get necessary privileges to enable Quick Expand!\nPlease uncheck Quick Expand option and try again. Maximum VeraCrypt volume size of %I64u TB exceeded!\n Full Format Fast Create WARNING: You should use Fast Create only in the following cases:\n\n1) The device contains no sensitive data and you do not need plausible deniability.\n2) The device has already been securely and fully encrypted.\n\nAre you sure you want to use Fast Create?