Rufus is a utility that helps format and create bootable USB flash drives.

Overview

Rufus: The Reliable USB Formatting Utility

Build status Coverity Scan Build Status Build contributors Github stats Release Licence

Rufus logo

Rufus is a utility that helps format and create bootable USB flash drives.

Features

  • Format USB, flash card and virtual drives to FAT/FAT32/NTFS/UDF/exFAT/ReFS/ext2/ext3
  • Create DOS bootable USB drives, using FreeDOS or MS-DOS (Windows 8.1 or earlier)
  • Create BIOS or UEFI bootable drives, including UEFI bootable NTFS
  • Create bootable drives from bootable ISOs (Windows, Linux, etc.)
  • Create bootable drives from bootable disk images, including compressed ones
  • Create Windows To Go drives
  • Create persistent Linux partitions
  • Download official Microsoft Windows 8 or Windows 10 retail ISOs
  • Compute MD5, SHA-1 and SHA-256 checksums of the selected image
  • Twice as fast as Microsoft's USB/DVD tool or UNetbootin, on ISO → USB creation (1)
  • Perform bad blocks checks, including detection of "fake" flash drives
  • Modern and familiar UI, with 38 languages natively supported
  • Small footprint. No installation required.
  • Portable
  • 100% Free Software (GPL v3)

Compilation

Use either Visual Studio 2019 (version 16.0 or later with SDK 10.0.18362 installed) or MinGW and then invoke the .sln or configure/make respectively.

Visual Studio

Rufus is an OSI compliant Open Source project. You are entitled to download and use the freely available Visual Studio Community Edition to build, run or develop for Rufus. As per the Visual Studio Community Edition license, this applies regardless of whether you are an individual or a corporate user.

Additional information

Rufus provides extensive information about what it is doing, either through its easily accessible log, or through the Windows debug facility.

Enhancements/Bugs

Please use the GitHub issue tracker for reporting problems or suggesting new features.

(1) Tests carried out with a 16 GB USB 3.0 ADATA pen drive on a Core 2 duo/4 GB RAM platform running Windows 7 x64. ISO: en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso

Name of tool Version Time
Windows USB/DVD Download Tool v1.0.30 8 mins 10s
UNetbootin v1.1.1.1 6 mins 20s
Rufus v1.1.0 3 mins 25s
You might also like...
Pseudofermion functional renormalization group solver for (frustrated) quantum magnets in two and three spatial dimensions.
Pseudofermion functional renormalization group solver for (frustrated) quantum magnets in two and three spatial dimensions.

SpinParser SpinParser ("Spin Pseudofermion Algorithms for Research on Spin Ensembles via Renormalization") is a software platform to perform pseudofer

Fundamentals of Data structures and algorithms in c++
Fundamentals of Data structures and algorithms in c++

Data Structures & Algorithms About the repository: Contains theories and programming questions related to fundamentals of data structures and algorith

CXXGraph is a Header-Only C++ Library for Graph Representation and Algorithms
CXXGraph is a Header-Only C++ Library for Graph Representation and Algorithms

CXXGraph is a small library, header only, that manages the Graph and it's algorithms in C++. In other words a "Comprehensive C++ Graph Library".

Official ACM CSS PEC repository for resources and all things Open source

Contributing Guidelines Ahoy there! Welcome to the PEC-ACM Open Source Repository. We request you to read the whole guidelines before making any pull

Header-only C++ library for robotics, control, and path planning algorithms.
Header-only C++ library for robotics, control, and path planning algorithms.

Header-only C++ library for robotics, control, and path planning algorithms.

c++ library including few algorithms and datastructures

c++ library including few algorithms and datastructures

A simple single header C/C++ Library for AABB Collision detection and resolution.
A simple single header C/C++ Library for AABB Collision detection and resolution.

A simple single header C/C++ Library for AABB Collision detection and resolution

My attempt at implementing the fast voxel traversal algorithm by Amanatides and Woo using OpenGL

Attempt at implementing the fast voxel traversal algorithm Works on both Linux and Windows. Recommended software: Linux: Visual Studio Code / Windows:

Quick sort is a highly efficient sorting algorithm and is based on partitioning of array of data into smaller arrays.
Quick sort is a highly efficient sorting algorithm and is based on partitioning of array of data into smaller arrays.

Quick sort is a highly efficient sorting algorithm and is based on partitioning of array of data into smaller arrays. A large array is partitioned into two arrays one of which holds values smaller than the specified value, say pivot, based on which the partition is made and another array holds values greater than the pivot value.

Comments
  • When trying to install Rufus, it is registering as open within task manager under details but nothing is showing on the screen.

    When trying to install Rufus, it is registering as open within task manager under details but nothing is showing on the screen.

    

    Checklist

    • [x] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
    • [x] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.
    • [ ] I clicked the 'Log' button or pressed Ctrl-L in Rufus, and copy/pasted the log into the line that says <FULL LOG> below.
    • [ ] The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

    Additionally (if applicable):

    • [ ] I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
    • [ ] I also tried one or more of the following:
      • [ ] Using a different USB drive.
      • [ ] Plugging the USB into a different port.
      • [ ] Running Rufus on a different computer.
    • [ ] If using an image, I clicked on the (✓) button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.

    Issue description

    Log

    <FULL LOG>
    
    opened by brewdog90gaming 6
  • feature request: add option to Disable BitLocker automatic device encryption

    feature request: add option to Disable BitLocker automatic device encryption

    Can you please add option to Disable BitLocker automatic device encryption? It's anoying that bitlocker encryption is turned on all all drivers by default on my new HP notebook with 12gen cpu.

    This can be done by adding registry key as below.

    https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-bitlocker#disable-bitlocker-automatic-device-encryption

    Disable BitLocker automatic device encryption OEMs can choose to disable device encryption and instead implement their own encryption technology on a device. To disable BitLocker automatic device encryption, you can use an Unattend file and set PreventDeviceEncryption to True. Alternately, you can update this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker Value: PreventDeviceEncryption equal to True (1).

    Thank you.

    opened by lwlwlwlw 1
  • ERROR: unable to assign a drive letter

    ERROR: unable to assign a drive letter

    

    Checklist

    • [x] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
    • [x] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.
    • [x] I clicked the 'Log' button or pressed Ctrl-L in Rufus, and copy/pasted the log into the line that says <FULL LOG> below.
    • [x] The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

    Additionally (if applicable):

    • [ ] I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
    • [ ] I also tried one or more of the following:
      • [x] Using a different USB drive.
      • [x] Plugging the USB into a different port.
      • [ ] Running Rufus on a different computer.
    • [ ] If using an image, I clicked on the (✓) button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.

    Issue description

    Attached you can find a screenshot. You can see the ERROR message. Captura de pantalla (5)

    Log

    <FULL LOG>
    ```Rufus x86 v3.21.1949
    Windows version: Windows 10 Home, 64-bit (Build 19044.2364)
    Syslinux versions: 4.07/2013-07-25, 6.04/pre1
    Grub versions: 0.4.6a, 2.06
    System locale ID: 0x0C0A (es-ES)
    Detected installed Windows Language Pack for 0x0409 (English (English))
    SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
    Localization set to 'en-US'
    Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.
    Found USB 2.0 device 'Generic Flash Disk USB Device' (058F:6387)
    1 device found
    Disk type: Removable, Disk size: 16 GB, Sector size: 512 bytes
    Cylinders: 1950, Tracks per cylinder: 255, Sectors per track: 63
    Partition type: MBR, NB Partitions: 1
    Disk ID: 0x7A18C285
    Drive has an unknown Master Boot Record
    Partition 1:
      Type: NTFS (0x07)
      Detected File System: NTFS
      Size: 14.9 GB (16041979904 bytes)
      Start Sector: 2408, Boot: No
    
    opened by Almaar72 0
  • Resolve symlinks/change path when mounting boot.wim

    Resolve symlinks/change path when mounting boot.wim

    

    Checklist

    • [x] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
    • [x] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log.
    • [x] I clicked the 'Log' button or pressed Ctrl-L in Rufus, and copy/pasted the log into the line that says <FULL LOG> below.
    • [x] The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

    Additionally (if applicable):

    • [x] I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
    • [x] I also tried one or more of the following:
      • [ ] Using a different USB drive.
      • [x] Plugging the USB into a different port.
      • [ ] Running Rufus on a different computer.
    • [x] If using an image, I clicked on the (✓) button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.

    Issue description

    When 'C:\Temp' is a symlink(SSD => HDD), mounting boot.wim fails with the Could not mount 'F:\sources\boot.wim [2]' on 'C:\Temp\Ruf70C9.tmp': [0x00000057] The parameter is incorrect. error. When symlink is replaced with real folder, all succeeds. So, symlink can be resolved and real path to mount point obtained or some another REAL path could be used instead, whatever is easier. User should never be forced to change configuration which OS itself, all the drivers and another programs accept.

    Log

    Rufus x86 v3.20.1929 (Portable)
    Windows version: Windows 11 (Unknown Edition 0xBF), 64-bit (Build 22000.1098)
    Syslinux versions: 4.07/2013-07-25, 6.04/pre1
    Grub versions: 0.4.6a, 2.06
    System locale ID: 0x0409 (en-US)
    Will use default UI locale 0x0409
    SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
    Localization set to 'en-US'
    Found USB 2.0 device 'JetFlash Transcend 32GB USB Device' (8564:1000)
    1 device found
    Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
    Cylinders: 3801, Tracks per cylinder: 255, Sectors per track: 63
    Partition type: GPT, NB Partitions: 1
    Disk GUID: {BFFB9266-AEA2-4853-AADD-7C8B8C22AEBA}
    Max parts: 128, Start Offset: 17408, Usable = 31264306688 bytes
    Partition 1:
      Type: Microsoft Basic Data Partition
      Name: 'Main Data Partition'
      Detected File System: FAT32
      ID: {159B6386-3AAF-4C5E-A215-315642B3B0E5}
      Size: 29.1 GB (31263275520 bytes)
      Start Sector: 2048, Attributes: 0x0000000000000000
    Scanning image...
    ISO analysis:
      Image is a UDF image
    Disk image analysis:
      Image does not have a Boot Marker
    ISO label: 'CCSA_X64FRE_EN-US_DV5'
      Detected: Windows 11 ISO (Build 22000.1157)
      Size: 4.9 GB (Projected)
      Has a >4GB file
      Uses: EFI
      Uses: Bootmgr (BIOS and UEFI)
      Uses: Install.wim (version 0.13.1)
    Using image: 22000.1219.221105-0007.CO_RELEASE_SVC_PROD1_CLIENTMULTI_X64FRE_EN-US.ISO (4.9 GB)
    
    Format operation started
    Requesting disk access...
    Will use 'F:' as volume mountpoint
    Opened \\.\PhysicalDrive7 for shared write access
    Analyzing existing boot records...
    Drive has a Zeroed Master Boot Record
    Clearing MBR/PBR/GPT structures...
    Erasing 128 sectors
    Initializing disk...
    Partitioning (GPT)...
    ● Creating Main Data Partition (offset: 1048576, size: 29.1 GB)
    ● Creating UEFI:NTFS Partition (offset: 31263241216, size: 1 MB)
    Writing UEFI:NTFS data...
    Waiting for logical drive to reappear...
    Formatting to NTFS (using IFS)
    Using cluster size: 4096 bytes
    Quick format was selected
    Creating file system...
    Format completed.
    Opened \\.\PhysicalDrive7 for shared write access
    Writing Master Boot Record...
    Using Rufus protective MBR
    Writing protective message SBR
    Found volume \\?\Volume{c3941621-f62a-4a95-a11b-c1bb9226ff4c}\
    Disabling file indexing...
    Successfully remounted \\?\Volume{c3941621-f62a-4a95-a11b-c1bb9226ff4c}\ as F:
    Extracting files...
    Image is a UDF image
    Extracting: F:\autorun.inf (128 bytes)
    ..........................................................
    
    Oh, huck!!! - Comment is too long (maximum is 65536 characters)
    
    There was an error creating your Issue: body is too long (maximum is 65536 characters). 
    
    ...........................................................
    
    Extracting: F:\support\logging\winsetupetw.dll (72.5 KB)
    Applying Windows customization:
    Renamed 'F:\sources\appraiserres.dll' → 'F:\sources\appraiserres.bak'
    Created 'F:\sources\appraiserres.dll' placeholder
    Mounting 'F:\sources\boot.wim'...
    Could not mount 'F:\sources\boot.wim [2]' on 'C:\Temp\Ruf70C9.tmp': [0x00000057] The parameter is incorrect.
    Finalizing, please wait...
    F:autorun.inf already exists - keeping it
    NTFS Fixup (Checkdisk)...
    
    Found USB 2.0 device 'JetFlash Transcend 32GB USB Device' (8564:1000)
    1 device found
    Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
    Cylinders: 3801, Tracks per cylinder: 255, Sectors per track: 63
    Partition type: GPT, NB Partitions: 2
    Disk GUID: {24FAE298-0B23-437D-9BAB-101AA77884E3}
    Max parts: 128, Start Offset: 17408, Usable = 31264306688 bytes
    Partition 1:
      Type: Microsoft Basic Data Partition
      Name: 'Main Data Partition'
      Detected File System: NTFS
      ID: {C3941621-F62A-4A95-A11B-C1BB9226FF4C}
      Size: 29.1 GB (31262192640 bytes)
      Start Sector: 2048, Attributes: 0x0000000000000000
    Partition 2 (UEFI:NTFS):
      Type: Microsoft Basic Data Partition
      Name: 'UEFI:NTFS'
      Detected File System: FAT12
      ID: {41A7F8CD-F254-4BEC-A32E-714F4BCBB37F}
      Size: 1 MB (1048576 bytes)
      Start Sector: 61061018, Attributes: 0x9000000000000000
    
    Format operation started
    Requesting disk access...
    Will use 'F:' as volume mountpoint
    Opened \\.\PhysicalDrive7 for shared write access
    Analyzing existing boot records...
    Drive has a Zeroed Master Boot Record
    Clearing MBR/PBR/GPT structures...
    Erasing 128 sectors
    Initializing disk...
    Partitioning (GPT)...
    ● Creating Main Data Partition (offset: 1048576, size: 29.1 GB)
    ● Creating UEFI:NTFS Partition (offset: 31263241216, size: 1 MB)
    Writing UEFI:NTFS data...
    Waiting for logical drive to reappear...
    Formatting to NTFS (using IFS)
    Using cluster size: 4096 bytes
    Quick format was selected
    Creating file system...
    Format completed.
    Opened \\.\PhysicalDrive7 for shared write access
    Writing Master Boot Record...
    Using Rufus protective MBR
    Writing protective message SBR
    Found volume \\?\Volume{1b6f4479-2d9b-4a15-9ffb-0c6e8610e9e0}\
    Disabling file indexing...
    Successfully remounted \\?\Volume{1b6f4479-2d9b-4a15-9ffb-0c6e8610e9e0}\ as F:
    Extracting files...
    Image is a UDF image
    Extracting: F:\autorun.inf (128 bytes)
    Extracting: F:\boot\bcd (16 KB)
    ..........................................................
    
    Oh, huck!!! - Comment is too long (maximum is 65536 characters)
    
    There was an error creating your Issue: body is too long (maximum is 65536 characters). 
    
    ...........................................................
    
    Extracting: F:\support\logging\winsetupetw.dll (72.5 KB)
    Applying Windows customization:
    Renamed 'F:\sources\appraiserres.dll' → 'F:\sources\appraiserres.bak'
    Created 'F:\sources\appraiserres.dll' placeholder
    Mounting 'F:\sources\boot.wim'...
    Could not mount 'F:\sources\boot.wim [2]' on 'C:\Temp\RufBF44.tmp': [0x00000057] The parameter is incorrect.
    Finalizing, please wait...
    F:autorun.inf already exists - keeping it
    NTFS Fixup (Checkdisk)...
    
    Found USB 2.0 device 'JetFlash Transcend 32GB USB Device' (8564:1000)
    1 device found
    Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
    Cylinders: 3801, Tracks per cylinder: 255, Sectors per track: 63
    Partition type: GPT, NB Partitions: 2
    Disk GUID: {67F81D14-5021-43C8-8338-8FEED8BDE750}
    Max parts: 128, Start Offset: 17408, Usable = 31264306688 bytes
    Partition 1:
      Type: Microsoft Basic Data Partition
      Name: 'Main Data Partition'
      Detected File System: NTFS
      ID: {1B6F4479-2D9B-4A15-9FFB-0C6E8610E9E0}
      Size: 29.1 GB (31262192640 bytes)
      Start Sector: 2048, Attributes: 0x0000000000000000
    Partition 2 (UEFI:NTFS):
      Type: Microsoft Basic Data Partition
      Name: 'UEFI:NTFS'
      Detected File System: FAT12
      ID: {4ADD7B42-6054-4642-A895-7DEFFDDB4D08}
      Size: 1 MB (1048576 bytes)
      Start Sector: 61061018, Attributes: 0x9000000000000000
    
    Format operation started
    Requesting disk access...
    Will use 'F:' as volume mountpoint
    Opened \\.\PhysicalDrive7 for shared write access
    Analyzing existing boot records...
    Drive has a Zeroed Master Boot Record
    Clearing MBR/PBR/GPT structures...
    Erasing 128 sectors
    Initializing disk...
    Partitioning (GPT)...
    ● Creating Main Data Partition (offset: 1048576, size: 29.1 GB)
    ● Creating UEFI:NTFS Partition (offset: 31263241216, size: 1 MB)
    Writing UEFI:NTFS data...
    Waiting for logical drive to reappear...
    Formatting to NTFS (using IFS)
    Using cluster size: 4096 bytes
    Quick format was selected
    Creating file system...
    Format completed.
    Opened \\.\PhysicalDrive7 for shared write access
    Writing Master Boot Record...
    Using Rufus protective MBR
    Writing protective message SBR
    Found volume \\?\Volume{6bbd157b-7a9a-463e-a457-d36466e23e33}\
    Disabling file indexing...
    Successfully remounted \\?\Volume{6bbd157b-7a9a-463e-a457-d36466e23e33}\ as F:
    Extracting files...
    Image is a UDF image
    Extracting: F:\autorun.inf (128 bytes)
    ..........................................................
    
    Oh, huck!!! - Comment is too long (maximum is 65536 characters)
    
    There was an error creating your Issue: body is too long (maximum is 65536 characters). 
    
    ...........................................................
    
    Extracting: F:\support\logging\winsetupetw.dll (72.5 KB)
    Applying Windows customization:
    Renamed 'F:\sources\appraiserres.dll' → 'F:\sources\appraiserres.bak'
    Created 'F:\sources\appraiserres.dll' placeholder
    Mounting 'F:\sources\boot.wim'...
    Mounted 'F:\sources\boot.wim [2]' on 'C:\Temp\Ruf3671.tmp'
    Mounted offline registry hive 'C:\Temp\Ruf3671.tmp\Windows\System32\config\SYSTEM' to 'HKLM\RUFUS_OFFLINE_HIVE'
    Created 'HKLM\SYSTEM\Setup\LabConfig\BypassTPMCheck' registry key
    Created 'HKLM\SYSTEM\Setup\LabConfig\BypassSecureBootCheck' registry key
    Created 'HKLM\SYSTEM\Setup\LabConfig\BypassRAMCheck' registry key
    Created 'F:\sources\$OEM$\$$\Panther\unattend.xml'
    Unmounted offline registry hive 'HKLM\RUFUS_OFFLINE_HIVE'
    Unmounting 'F:\sources\boot.wim'...
    Unmounted 'C:\Temp\Ruf3671.tmp [2]'
    Finalizing, please wait...
    F:autorun.inf already exists - keeping it
    NTFS Fixup (Checkdisk)...
    Volume label is CCSA_X64FRE_EN-US_DV5.
    
    Stage 1: Examining basic file system structure ...
      1280 file records processed.
    File verification completed.
     Phase duration (File record verification): 65.58 milliseconds.
      0 large file records processed.
     Phase duration (Orphan file record recovery): 4.42 milliseconds.
      0 bad file records processed.
     Phase duration (Bad file record checking): 6.24 milliseconds.
    
    Stage 2: Examining file name linkage ...
      1476 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 214.68 milliseconds.
     Phase duration (Orphan reconnection): 0.11 milliseconds.
     Phase duration (Orphan recovery to lost and found): 0.01 milliseconds.
      0 reparse records processed.
      0 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 8.57 milliseconds.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 20.20 milliseconds.
      98 data files processed.
     Phase duration (Data attribute verification): 4.56 milliseconds.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
      30529484 KB total disk space.
       5182112 KB in 944 files.
           344 KB in 100 indexes.
         44384 KB in use by the system.
         41760 KB occupied by the log file.
      25302644 KB available on disk.
          4096 bytes in each allocation unit.
       7632371 total allocation units on disk.
       6325661 allocation units available on disk.
    Total duration: 335.24 milliseconds (335 ms).
    NTFS Fixup completed.
    
    Found USB 2.0 device 'JetFlash Transcend 32GB USB Device' (8564:1000)
    1 device found
    Disk type: Removable, Disk size: 32 GB, Sector size: 512 bytes
    Cylinders: 3801, Tracks per cylinder: 255, Sectors per track: 63
    Partition type: GPT, NB Partitions: 2
    Disk GUID: {9A7F558D-F8D6-4692-AF95-4EEAED0B9415}
    Max parts: 128, Start Offset: 17408, Usable = 31264306688 bytes
    Partition 1:
      Type: Microsoft Basic Data Partition
      Name: 'Main Data Partition'
      Detected File System: NTFS
      ID: {6BBD157B-7A9A-463E-A457-D36466E23E33}
      Size: 29.1 GB (31262192640 bytes)
      Start Sector: 2048, Attributes: 0x0000000000000000
    Partition 2 (UEFI:NTFS):
      Type: Microsoft Basic Data Partition
      Name: 'UEFI:NTFS'
      Detected File System: FAT12
      ID: {321E06FF-13B4-4200-8409-96E99D6D91B4}
      Size: 1 MB (1048576 bytes)
      Start Sector: 61061018, Attributes: 0x9000000000000000
    
    
    deferred 
    opened by powerbroker 1
Releases(v3.21)
Owner
Pete Batard
A Free Software Developer, with more decades of experience than we care to admit — It is through this lens that we see Stallman's foresight being vindicated...
Pete Batard
C++ fundamentals and questions for beginners and intermediates. Welcoming developers, content writers, and programming enthusiasts.

Rules To Contribute To This Repo You can write solutions only in C++ for Data Structure and Algorithms (if you dont know C++ you can submit only algor

Sushree Satarupa 210 Dec 11, 2022
Collection of algorithms and data structures in C++ and Java

Collection of algorithms and data structures in C++ and Java

Andrei Navumenka 1.7k Jan 2, 2023
Organic Maps is a better fork of MAPS.ME, an Android & iOS offline maps app for travelers, tourists, hikers, and cyclists based on top of crowd-sourced OpenStreetMap data and curated with love by MAPS.ME founders.

?? Organic Maps is a better fork of MAPS.ME, an Android & iOS offline maps app for travelers, tourists, hikers, and cyclists based on top of crowd-sourced OpenStreetMap data and curated with love by MAPS.ME founders. No ads, no tracking, no data collection, no crapware.

Organic Maps 4.4k Jan 2, 2023
WasmEdge Runtime is a high-performance, extensible, and hardware optimized WebAssembly Virtual Machine for automotive, cloud, AI, and blockchain applications.

WasmEdge Runtime is a high-performance, extensible, and hardware optimized WebAssembly Virtual Machine for automotive, cloud, AI, and blockchain applications.

null 5.1k Jan 5, 2023
Emusicchain is a blockchain built using Cosmos SDK and Tendermint and created with Starport.

emusicchain emusicchain is a blockchain built using Cosmos SDK and Tendermint and created with Starport. Get started starport chain serve serve comma

null 2 May 13, 2022
A library of common data structures and algorithms written in C.

C Algorithms The C programming language includes a very limited standard library in comparison to other modern programming languages. This is a coll

Simon Howard 2.9k Jan 9, 2023
Several algorithms and data structures implemented in C++ by me (credited to others where necessary).

Algorithms This repository contains my implementations of several algorithms and data structures in C++ (credited to others where necessary). It has i

Petar Veličković 589 Dec 19, 2022
C++ implementations of well-known (and some rare) algorithms, while following good software development practices

ProAlgos: C++ This project is focused on implementing algorithms and data structures in C++, while following good software engineering practices, such

ProAlgos 485 Dec 7, 2022
Xournal++ is a handwriting notetaking software with PDF annotation support. Written in C++ with GTK3, supporting Linux (e.g. Ubuntu, Debian, Arch, SUSE), macOS and Windows 10. Supports pen input from devices such as Wacom Tablets.

Xournal++ is a hand note taking software written in C++ with the target of flexibility, functionality and speed. Stroke recognizer and other parts are based on Xournal Code

Xournalpp 7.9k Jan 7, 2023
Provide building blocks (software, hardware and algorithms) for implementing SLAM using small sensors

RemoteSLAM The purpose of this repo is to provide the building blocks (software drivers, hardware and algorithms) for implementing SLAM systems using

Autonomous Drones Lab, Tel Aviv University 38 Jan 20, 2022