Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Latest News: Ethereum mailing list breach exposes 35,000 to crypto draining attack

Featured Deal: Upgrade your iPad with an Apple Magic Keyboard Folio for under $90

Latest Buyer's Guide: Best web browsers with built in VPN: Boost online privacy

File size inflation during data migration from SATA HDD to M.2 NVMe

Started by Lilium , Jan 30 2024 06:50 PM

Please log in to reply

No replies to this topic

#1 Lilium

Members
118 posts
OFFLINE

Local time:09:28 AM

Posted 30 January 2024 - 06:50 PM

My attempt to move a folder containing 1.5TB of files from a WD 6TB SATA HDD (model # WD60EZRZ-00RWYB1) that was in a previous Windows 7 x64 Ultimate Edition rig is seen as 3.63TB to my Crucial P3 4TB (model # CT4000P3SSD8) in my current Windows 11 x64 Home Edition Version 23H2 Build 22631.3085 rig. What are potential reasons this occurs and how can I prevent this during future transfers?

Screenshot 2024-01-30 180110.png 227.59KB 1 downloads