EliteBytes VeloSSD Changelog

What's new in EliteBytes VeloSSD 4.0.4.0

Jan 22, 2024
  • Update contains only a number of updated points. A detailed exposure is coming soon. This version is Microsoft certified.

New in EliteBytes VeloSSD 3.6.1.4 (Apr 4, 2022)

  • Compatibility Update for Storage Spaces.
  • New Engine Update !

New in EliteBytes VeloSSD 3.6.1.1 (Mar 31, 2022)

  • Compatibility Update for Storage Spaces.
  • New Engine Update !

New in EliteBytes VeloSSD 3.6.1.0 (Mar 13, 2022)

  • Windows 11 ready. Older versions may have a problem with it.
  • More velocity for the masses. It got better optimized:
  • Massive reduction of write cycles to SSD. Faster and greener.
  • Online activation problems solved.
  • Still back compatible with vintage versions of Windows.

New in EliteBytes VeloSSD 3.6.0.2 (Jul 9, 2021)

  • Bug fix in Power Safe Mode. ( Sleep / Hibernate)
  • The bug caused long shutdown / hibernation / sleep times / malfunctions.
  • Rather important to update to this version.

New in EliteBytes VeloSSD 3.6.0.1 (Jun 18, 2021)

  • New Easy to understand SSD wear save controls.
  • This includes "Write through", and other options.Consequently
  • some low performance old code was removed in the SSD cache allocation.
  • Additionally to usual cryptographic signatures, valid for all compatible plattforms.

New in EliteBytes VeloSSD 3.6.0.0 (Feb 2, 2021)

  • Basically took original old code base, tested and solidified it for 3 months.

New in EliteBytes VeloSSD 3.5.0.1 (Sep 24, 2020)

  • Storage Space For Client / Server reworked

New in EliteBytes VeloSSD 3.5.0.0 (May 19, 2020)

  • APP
  • S.M.A.R.T removed.
  • Hebrew language works.
  • Activation overworked.
  • VS Driver
  • Source Code base was taken from MaxVeloSSD and VeloRam. All products have same base now.
  • This improves VeloSSD reliability and stability a lot. Because Maxvelossd and VeloRAM
  • Is the main source base, VeloSSD was the earliest product.
  • Recovery after accidental power off / reset / bsod works much better.
  • Problem of sometimes slow shutdown removed.
  • Write cache bettered

New in EliteBytes VeloSSD 3.0.2.0 (Dec 15, 2019)

  • BugFix in Setup / driver. Bugfix for Deinstall BSOD Bug.

New in EliteBytes VeloSSD 3.0.0.4 (Jul 9, 2019)

  • The Driver is Digitally counter Signed by Microsoft.
  • Compatible with Windows 10 Client versions:1506, 1511 (TH2),
  • 1607, 1703, 1709, 1803, 1809 (RS1-5).
  • This has no impact on vintage Windows Client and Server Versions compatibility.
  • Several Bug fixes in drivers and Application.
  • Latest Runtime and libraries.
  • New Activation System. Read more.

New in EliteBytes VeloSSD 3.0.0.1 (Jan 19, 2019)

  • The Driver is Digitally counter Signed by Microsoft.
  • Compatible with Windows 10 Client versions:1506, 1511 (TH2),
  • 1607, 1703, 1709, 1803, 1809 (RS1-5).
  • This has no impact on vintage Windows Client and Server Versions compatibility.
  • Several Bug fixes in drivers and Application.

New in EliteBytes VeloSSD 2.5.2.2 (Jun 7, 2018)

  • The Driver is Digitally counter Signed by Microsoft.
  • Compatible with Windows 10 Client versions:1506, 1511, 1607 and RedStone 2,3,4
  • This has no impact on vintage Windows Client and Server Versions compatibility.
  • Bug fix for the EB000006 C000000D 203 Error message.
  • The inf file was corrected to the latest standars

New in EliteBytes VeloSSD 2.5.2.1 (Apr 10, 2018)

  • Small fix on OS version detection.
  • Power Mgt. Code removed a bug that could lead to BSOD.

New in EliteBytes VeloSSD 2.5.2.0 (Apr 5, 2018)

  • OS version detection rewritten.
  • New activation code, better compatibility with Telekom routers.
  • Writeback code rollback, better stability.

New in EliteBytes VeloSSD 2.5.1.1 (Mar 2, 2018)

  • The trial time is 30 days. An error shortened it to 10 days. fixed.
  • Bug with cached Data Volume removed.

New in EliteBytes VeloSSD 2.5.0.4 (Feb 12, 2018)

  • This Update: Multi Language switch - no manual restart necessary Several bugs removed that could lead to wrong behaviour. New Graphics for 2.5 2018 versions. Better driver conformity with the verifier.

New in EliteBytes VeloSSD 2.5.0.1 (Jan 23, 2018)

  • Allows Setup on Windows 7 again.

New in EliteBytes VeloSSD 2.5.0.0 (Jan 23, 2018)

  • Complies to highest security Standards ( Signed with Extended Verification Certificate and countersigned by Microsoft WHQL ) (Now Windows 10 Secure Boot Compatible !)
  • Was tested positive on latest Windows 10 1709 and build 16251 / Server 2016
  • Updated the build environment to the Visual Studio 2015 Build tool chain.

New in EliteBytes VeloSSD 2.3.4.1 (Oct 5, 2017)

  • Cross signed by Microsoft, runs in Windows 10 Secure Boot Mode. Stable on Win 10 16251

New in EliteBytes VeloSSD 2.3.0.2 (Jul 12, 2017)

  • Build Integrity Check option add. This means a stricter Code signing policy compared to earlier builds.

New in EliteBytes VeloSSD 2.2.6.6 (Nov 29, 2016)

  • Compatibility with newest Windows 10 and Server 2016 verified.
  • Several minor issues fixed.

New in EliteBytes VeloSSD 2.2.6.5 (Nov 4, 2016)

  • Allowed Cache Size raised, now double size !!!
  • Cluster shared volume compatibility added
  • reaffirmed compatibility with Bitlocker(tm)
  • Bugs fixed:
  • 1 possible crash during removal fixed.
  • Problem with refs on cache volume and newer servers removed
  • Pie chart alignment fixed.
  • Problem condition after reset/power off removed

New in EliteBytes VeloSSD 2.2.6.0 (Nov 18, 2015)

  • This version doubles the SSD Cache Size limit for the Personal edition to 128GB Cache. A few decent bug fixes improve stability.

New in EliteBytes VeloSSD 2.2.5.0 (Sep 25, 2015)

  • This version is a big jump ahead since it adds many features from the MaxVeloSSD CodeBase. S.M.A.R.T and Performance monitoring, WriteThrough, Scan Resistant and Maximum Host Capacity Limits ( now 2 PetaByte ). Thoroughly tested under Windows 10. Bugs with multiple cache Data Volumes removed. Bugs in the Cache engine were removed. Bugs with recovery after power loss were removed. Recovery is now quicker, especially when the write cache is filled up. Earlier versions needed to write the Write Cache back completely before boot. That could result in frustrating long boot times.