I checked and the date is 10/30/2015.  I haven't experienced any problems with printing, and was surprised to even find the errors in the event monitor. But why would Pmail be waiting on this anyway, when trying to download mail? There are 3 more copies in the WinSxS folder, which is apparently where the Windows update files are stored.  I'm going to try to clean that up in case that's part of the problem.  The Wait chain doesn't specify the path, although I would think it would be only in the C:|Windows directory - WinSxS is a subdirectory.

<p>Running Windows 10 on a DIY computer (no recent hardware upgrades).  I was having problems showing up in the Event Monitor, mostly with Explorer, and ran sfc /scannow, then DISM, then repeated sfc /scannow.  These are commands to repair files in the OS, and the repairs were made.  That fixed THAT problem, but that's when I found I could no longer download messages. Here's what shows on the log:</p><p>05:12:47.044: Connect to 'pop.nemont.net', timeout 300 seconds.</p><p>05:12:48.045: >> +OK Ready.<cr><lf></p><p>05:12:48.045: << USER userid<cr><lf></p><p>05:12:48.069: >> +OK<cr><lf></p><p>05:12:48.070: << PASS pswd<cr><lf></p><p>05:12:48.094: >> +OK Logged in.<cr><lf></p><p>05:12:48.096: << STAT<cr><lf></p><p>05:12:48.376: >> +OK 64 3200437<cr><lf></p><p>05:12:48.377: << LIST<cr><lf></p><p>05:12:48.400: >> +OK 64 messages:<cr><lf></p><p><span style="font-size: 10pt;">05:12:48.400: >> 1 5515<cr><lf></span><span style="font-size: 10pt;"> </span></p><p>{snipped more of the same - the other 62 messages}</p><p>05:12:48.422: >> 64 36761<cr><lf></p><p>05:12:48.422: >> .<cr><lf></p><p>05:12:48.425: << RETR 1<cr><lf></p><p>05:12:48.454: >> +OK 5515 octets<cr><lf></p><p>05:17:48.601: 8: Socket read timeout</p><p>05:17:48.601: >> </p><p>05:18:08.631: << QUIT<cr><lf></p><p>05:23:08.782: 8: Socket read timeout</p><p>05:23:08.782: >> </p><p>05:23:08.783: --- Connection closed normally at 14 Nov 2016, 5:23:08.783. ---</p><p>05:23:08.783: </p><p>I can send mail and click on links successfully. </p><p>Most of the posts I've read talk about checking/changing the MTU size, but I've never messed with that.  I did check that the timeout was 300 secs on both the general and POP3 tabs. There are no warning or error messages in the Event Log that appear relevant, except an error for the Print Spooler.  I don't know if I'm chasing this down a rabbit hole or not -- why would dowloading mail be involved with the system print spooler? However, i<span style="font-size: 10pt;">f I go to the system Resource Monitor after initiating a download, then right click on winpm-32.exe and choose Analyze Wait Chain, I see this:</span></p><p><span style="font-size: 10pt;">winpm-32.exe (PID:21744) Thread 32372</span></p><p><span style="font-size: 10pt;">winpm-32.exe (PID:21744) Thread 22592</span></p><p><span style="font-size: 10pt;"><span class="Apple-tab-span" style="white-space:pre"> </span>splwow64.exe (PID:32116)</span></p><p><span style="font-size: 10pt;">The ending splwow64.exe, the apparent cause of the wait, is the printer spooler driver.  There are 2 errors in the event log from about the time I initiated the mail download, but also at the time I successfully printed 2 pages.  </span></p><p>I had been running 4.71 and tried upgrading to 4.72 -- no change.  I then tried doing an uninstall and reinstalling 4.72, again no change.</p><p>Help!</p><p>Litewriter </p><p>UPDATE:</p><p><span style="font-size: 10pt;">I ended up doing a clean install of Windows 10, and as soon as the system was up and running, I installed Pegasus mail and tried a test, and it worked fine.  I think the problem must have been in the OS -- I was seeing other glitches and this was just the last straw. </span></p><p> </p>

<p>I suggest you check on the file date of your SplWow64.exe file.  As you can see from the filename, it is intended to 64-bit Windows, and this program has quite a bit of maintenance from Microsoft patching.</p><p>In its current version (Nov 2014) it seems to be stable finally, I had similar problems to those you mention. Basically my printer only responded to print commands just after rebooting, and would then fall asleep and not perform any further print spooling. </p><p>Martin </p>