[Solved] Slow Windows 10 installation via USB thumbdrive

Was installing a fresh copy of Windows 10 on a new SSD (yep, wanted to avoid the windows 8.1 baggage so went this path)...

Unfortunately, the installation was SLOW!!! it took more than 12 hours to get to the screen where you can choose which drive to setup the Windows OS on.

Yes, more than 12 hours.

After I tried to create a partition on the new SSD, it went through a super super super slow motion of working, I gave up. It just doesn't make sense that a Windows 10 install would take 2 days (ok, i was out for half a day on day 1 so it could have been "faster").

I Googled and realized that this was mentioned on many forums such as tom's hardware, bleeping computer, and so on.

I force shutdown the PC. Unplugged all the 5 other harddisks on the system and tried installation again.

This time, it took less than 10 minutes and the PC was booting up from the new C:\ on the SSD.

SSD - Samsung 850 Evo
Motherboard - Old Asus motherboard (pre 2010 era), with the first generation Intel core i7 cpu.
USB thumbdrive was a USB3 Sandisk Extreme Pro 64GB drive plugged into a USB2 port on the system (yeah, the thought crossed my mind that it could be due to USB2, but USB2 is not this slow.. 12 hours for a 7GB file copy? nahh...)

the mystery of the borken server, SOLVED

Acknowledgements

Thanks to maxsec (from MS's irc channel) and Jules (creator) of MailScanner!


Summary

Problem was two-fold:

1. I did not notice that Mail::ClamAV and Mail::SpamAssassin packages were not installed properly when running the install script provided in install-Clam-0.92-SA-3.2.4.tar.gz (error information below)
   
2. My system had /tmp mounted as "noexec" (is this a default BlueQuartz setting, or did I change this when the system was hardened previously?)
   

MailScanner diagnosis procedure

1. After installing MailScanner, run MailScanner --lint, check for any errors that get thrown out.
   
2. If there is any issue, run MailScanner -v to see the versions of the installed modules, make sure that they are correct.
   
3. If it is not conclusive, run MailScanner --debug or MailScanner --debug --debug-sa (if you have SpamAssassin)
4. If problem persists, Google it and search the MS Mailing List Archive (it is active).
5. If there is still nothing conclusive, go to the IRC channel and ask for help.
6. Subscribe and post the problem in the MS Mailing List too.

Error Information

An error was thrown during installation of Mail::SpamAssassin when I ran the install script in install-Clam-0.92-SA-3.2.4.tar.gz. (Remind myself to maximize the Putty screen next time).


Setting a soft-link from spam.assassin.prefs.conf into the SpamAssassin
site rules directory.
spam.assassin.prefs.conf is read directly by the SpamAssassin startup
code, so make sure you have a link from the site_rules directory to
this file in your MailScanner/etc directory.
Perl could not find your SpamAssassin installation.
Strange, I just installed it.
You should fix this!

Making backup of pre files to /tmp/backup.pre.3457.tar
tar: *pre: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors
Now go and find your v310.pre and v320.pre files,
echo which may well be in the /etc/mail/spamassassin directory.
You need to save a copy of your old v320.pre file and rename
the v320.pre file to v320.pre.


Moving on

*sigh* :)

Now I have to keep reminding myself to be extra careful when updating this server in the future. Not sure about why the other servers are fine. Maybe the manual installation of SpamAssassin source helped but I didn't do it for this server due to its custom configurations.

In the future updates of MailScanner, I will need to:

1. Download and unpack the new MS package / installer.
2. Go into the perl-tar directories and list all the PERL modules.
3. Open up CPAN (perl -MCPAN -e shell) and compare the version of the installed modules vs those with the MS package / installer.
4. If the versions are not ok, unpack those files that came with the MS package / installer, manually update them via the usual perl Makefile.PL -> make -> make test -> make install as root.

Ok, that's it for now!

Thanks to the advice and help from the people in MS's IRC channel, and especially to maxsec and Jules!