Pfsense images are constantly corrupt on windows 10 :(
-
you do understand img file is gzipped and has to be uncompressed before you write the image.
That is what the .gz on the end is.. Are you validating your download is good by checking the checksum..
-
I unpacked it using WinRAR. I see no reason why Winrar should struggle with GZIP.
-
It wouldn't - did you validate the hash of the file you downloaded with the hash that is provided on the download page? If that hash does not match then your download is corrupt and yeah your going to have all kinds of issues.,
-
Try the Win32DiskImager, it should accept just about any image file and doesn't try to validate the image in any way. I suspect that the other tools you're using are too smart for their own good and try to recognize and validate the uncompressed image and fail because of the rather peculiar disk layout used by the pfSense memstick images.
https://sourceforge.net/projects/win32diskimager/files/latest/download?source=navbar
Edit: Of course verify the checksums manually first as noted by others.
-
I select DD Image in Rufus, works every time.
-
Hash is fine yet same shit is happening when using 7zip. Just to be clear I downloaded the regular ISO and not the USB version. When downloading the USB version I can copy it with rufus to a USB stick, but the stick never appears in Windows explorer.
-
Hash is fine yet same shit is happening when using 7zip. Just to be clear I downloaded the regular ISO and not the USB version. When downloading the USB version I can copy it with rufus to a USB stick, but the stick never appears in Windows explorer.
Windows explorer will never show anything on the memory stick after the pfSense image is written on it, this is because of the filesystem used on the image that MS Windows does not support.
-
what are the hashes of iso after you extract it? Here I just downloaded the iso your talking about and here are its hashes
pfSense-CE-2.3.1-RELEASE-amd64.iso
CRC32: 356e72c3
MD5: 5f8b814f811b75fb6b081c8a019995b5
SHA-256: 04e517b110ed9cc1350bd9388eb577bf9476b8f8e3f50f781d7baf4ef61ce5c8I mounted this iso just fine..
-
Definitely something peculiar to your environment, bro.
-
what are the hashes of iso after you extract it? Here I just downloaded the iso your talking about and here are its hashes
pfSense-CE-2.3.1-RELEASE-amd64.iso
CRC32: 356e72c3
MD5: 5f8b814f811b75fb6b081c8a019995b5
SHA-256: 04e517b110ed9cc1350bd9388eb577bf9476b8f8e3f50f781d7baf4ef61ce5c8I mounted this iso just fine..
My hash value matches yours so it's certainly something fucked up with Windows not particularly enjoying the ISO file. The thing is PowerISO won't touch it either. I just can't think of anything that would cause this. I mean I can't possibly be the first person trying this on Windows 10 and pretty much every guide I have looked at, where they used another version of Windows, said use Rufus and it will work the same way as it usually does with any other FreeBSD or Windows ISO.
I'm going to give it one last try on a virtual Linux box tomorrow. I just don't have time to tinker any more with this today.
-
Windows 10 here.
I installed the same version two weeks ago and no problems what so ever. Use the USB image file (.img), not the ISO file. Win32 Disk Imager, or USBIT. Works a treat.
I've even downloaded the ISO and burned it to a CD as a "backup", because my McAfee firewall box tends to be very picky about USB sticks. No problems here too.
If there really is some Windows-related problem, I'm afraid it's gonna be something specific to your PC, not a general issue.
Regards,
Tom -
I succesfully wrote 2.3.2-RELEASE memstick and embedded images using Windows 10 a few times yesterday as well, on both USB and SDcard. Works like a charm using Win32DiskImager.
-
Faced the same problem. When installing in Windows, an error occurred checking the checksum.
I downloaded the daily build and everything was fine.
