# Checksums do not match

**URL:** <https://forums.balena.io/t/checksums-do-not-match/36537>\
**Category:** balenaEtcher\
**Created:** [October 14, 2019, 12:29am UTC](https://forums.balena.io/t/checksums-do-not-match/36537 "2019-10-14T00:29:45Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

**Author:** ![zvin](https://avatars.discourse-cdn.com/v4/letter/z/a5b964/32.png) [@zvin](https://forums.balena.io/u/zvin)\
**Post date:** [October 18, 2019, 3:13pm UTC](https://forums.balena.io/t/checksums-do-not-match/36537/38 "2019-10-18T15:13:27Z")

</div>

The raspbian image has 2 partitions:

- a 256MiB fat32 one starting at 4MiB;
- a 3.3GiB ext4 one just after;

There are 359 bytes that differ between the 2 images.  
All differences are located between 4MiB and 261MiB, only affecting the fat32 partition.  
That makes sense as it is the only partition windows can handle.

I’ve compared the 2 fat32 partitions using `meld`.  
Turns out the difference is a new `System Volume Information` folder containing `IndexerVolumeGuid` and `WPSettings.dat` files.  
These look like files added by Windows so I guess there’s nothing to worry about.

It is strange that it only happens on this computer.  
I’ll try to check if we can lock the drive on windows when I find some time.

 ![Capture%20d%E2%80%99%C3%A9cran%20de%202019-10-18%2016-56-09](https://global.discourse-cdn.com/balena/original/2X/6/6b4f35922ec3936cc1b67f38060e091b5b8210d8.png)

---

_[View the full topic](https://forums.balena.io/t/checksums-do-not-match/36537)._
