• 0

Iperf 3.10.1 Windows build


 Share

Question

So there has been an on going thread about powerline adapters, well the OP finally got some - and I was curious about speed he is seeing, etc.  So told him would post up links to some tools.

 

This lead me to compiling the latest version of iperf3 I could find for windows ;) Since I couldn't find one.  So figured post it up if anyone is interested.

 

Got the source from here https://github.com/esnet/iperf

Found a blog post how to compile on windows here http://www.embeddedsystemtesting.com/2014/08/how-to-compile-iperf3-for-windows.html

 

So few minutes later I end up with a copy of the current iperf3 that works on windows.  Needs a few cygwin dlls, included in the zip.  But other than that unzip and go.

 

It has lots of new options compared to the older versions

 

Been a fan of iperf for years, so will prob keep this current when new versions come out since doesn't seem like anyone else is posting up the windows builds, etc.

You can grab all my compiled versions here https://files.budman.pw/

Any questions on its use, just ask -- post up some tests as well!!

 

edit: updated this on 02/25/17 new build 3.1.6

http://software.es.net/iperf/news.html#iperf-3-1-6-released

This version of iperf3 contains two minor fixes. Notably, one of them unbreaks JSON output with UDP tests.

 

edit2:  5/23/17 Thanks to @Datalink for letting me know site was down.  Back up now, if your having issues flush your dns had to move it to different host.  Added site to my monitoring so next time it goes down will know right away ;)

BTW 3.1.7 just typo's so no reason to compile it

2017-03-06: iperf-3.1.7 released

This version of iperf3 contains two documentation fixes, but is otherwise identical to the prior release.

 

edit3: 7/6/17 Updated to new 3.2 build

http://files.budman.pw/iperf3.2_32bit.zip

CRC32: 9e4b913c
MD5: ff7fc42f6ba29e9f83c8bb8e0066f722
SHA-1: 68ad3a0f0c2f30c1756f0a5eb39e1062e6beb6f4

http://files.budman.pw/iperf3.2_64bit.zip

CRC32: add96290
MD5: 7a014ff67b1d678f546ead2360820d47
SHA-1: 98ed98ac6d392a4484e5151ab2f714390c99b52e

 

edi4: 11/18/17 Updated to new 3.3 build

https://files.budman.pw/iperf3.3_64.zip

MD5: 49095ccb2442101d2a1ffc6213f3d1b9
SHA-256: 1fea7ae97b8ec5ab1c61ef1afcf7afd491d37ef41061a845f9bb8477425c66db

 

https://files.budman.pw/iperf3.3_32.zip

MD5: b6ad4c094a18196e0798e1a2825bc609
SHA-256: 919978ac0b574d7662d5b0e58174a6107002db96e7592929a9a28938516a2c5f

 

edit5: 02/16/2018 Updated to new 3.4 build see post in thread

https://files.budman.pw/iperf3.4_32.zip

MD5: 3b805d0895e7bb4d005429ed5859dd00
SHA-256: 82a933bbf96731a615ee5ae40bc1e6986ffcdd0b83c7c4e9cd024a996b3c0808
https://files.budman.pw/iperf3.4_64.zip

MD5: e4c0d2d8bda22ebbb710a9a65aacddf9
SHA-256: 7a3f83d211d22102d05dcf0eb24f4ff8cd3d9083aada9a27c88ba7ced0a0eccc

 

edit6: 03/05/2018 Updated to 3.5 build, see post in thread

https://files.budman.pw/iperf3.5_64.zip

CRC32: 18962237
MD5: 840a2d5e0f81d8a6dc0d8be854caf61a
SHA-1: 1a18185c79645b082392dcd024b7e53900dc38bd
SHA-256: 94a0ec4e486904a6a8ebe390eca37871f47a097599908c3647d6ad1d0bbdff59
 

https://files.budman.pw/iperf3.5_32.zip

CRC32: 21d8a0eb
MD5: dd79fe69c86e62c780e45e6e0d2ec66d
SHA-1: 2c63c1f9ef35be23170869a6a7eb048241aa2f14
SHA-256: bf4b95a58e54ceda101e33b0b908c581df1ce4a217f233e1092dc3278572de43

 

edit7:

https://files.budman.pw/iperf3.6_64bit.zip

CRC32: A9B23E64
MD5: 3530BD3C837EA146C8F98106FA94E395
SHA-1: 7E09239B207739714294A4EA1DA9C69623374740
SHA-256: DE958C4CF72DBC64DCBB42130BD466D9FD367E4519C5C3F78A6675CA87E12B7D

 

edit8: Updated 7/6/2019 New 3.7 build, see post in thread

https://files.budman.pw/iperf3.7_64.zip

CRC32: 13EB9AD9
MD5: 96C2C058B0128BEC346BD0D034D7B31E
SHA-1: 83978F54B7EDDA073CC4E865493AA6544862879A
SHA-256: 93FB4641810C06DE554E97FD4E6B44CEFBD8ECB8EA8CFEA3CC550B823C3E89CE

 

edit9: Updated 3/11/2020 updated cygwin, guess there was some bug in the cygwindll, see post in thread.

https://files.budman.pw/iperf3.7_64_updated_cygwin1dll.zip

CRC32: ABCA3CAA
MD5: C3594A08967FD57BF36F757980480F9D
SHA-1: DF6C8B3D18941DABBC5AB21ACB5844A062620092
SHA-256: B1A14F8B2435AAA98D26F8499DF23BF6532B5F0EA2288DA04E0C28333EDBC48E

 

edit10: Updated 6/9/2020 New 3.8 build, see post in thread

https://files.budman.pw/iperf3.8_64bit.zip

MD5: 38A01DC0D4CC67058B094A96274A6F49
SHA-256: E37B0885EFA60106A3333CDAE878815B2306B434175F2BFBAF2DBF709BAB2049

 

edit11: updated 6/10/2020 New 3.8.1, see post in thread

https://files.budman.pw/iperf3.8.1_64.zip

CRC32: 69CE7B06
MD5: 1157B038DC04646B074A822A171E77A7
SHA-1: A692D6E5FAD3004A229C92661EC4448004EA269E
SHA-256: CD337C2EEB5ACF02713867990E4F9F0656CC0CAEA850F3B3C289DD79305DF1A1

 

edit12: updated 8/17/2020 New 3.9, see post in thread

https://files.budman.pw/iperf3.9_64.zip

Name: iperf3.9_64.zip
Size: 1542276 bytes (1506 KiB)
SHA256: 15D2D3C2A8B9A69EFD9991FEFE5206E31D6055399F7A4C663C3CB6D77B6770F8

 

edit13: updated 5/31/2021, see post in thread

https://files.budman.pw/iperf3.10_64bit.zip

SHA256: 098f276552939acec2a9a7d6990e79bac17e45fb951d32ce59c2d764cdcaf15a

 

edit14: updated 6/4/2021, released a new build

https://files.budman.pw/iperf3.10.1_64bit.zip

sha256     2cf3ff3671f9f4f57cf01ab8b2d960feb9e087d450f3b58aaf4ab82333262be0

iperf 3.10.1 fixes a problem with the configure script that made it make not work correctly in some circumstances. It is functionally identical to iperf 3.10.

I didn't seem to have any issues with my 3.10 build, but redid to keep with current version numbers.

 

Link to comment
Share on other sites

Recommended Posts

  • 0

I reply to myself: error for missing diff is fixed (adding "diffutils" package) but still having error for missing nanosleep function)

Link to comment
Share on other sites

  • 0

Damn, this was not enough, I got a runtime error now:

> iperf3.exe
iperf3:./.libs/lt-iperf3.c:524: FATAL: error accessing file "/usr": No such file or directory.

 

Any idea ? :wacko:

Link to comment
Share on other sites

  • 0

I pretty much just installed cygwin and it compiled without errors..  I could do a clean cygwin install on a vm.. Sounds like to me your cygwin install is borked.  I see you see the blog post I used, since you posted your question there.  Did you make the edits to source that are listed in the blog post?

 

I did this, per the blog post

BudMan@i5-w7 /iperf-3.1b3
$ cd src
BudMan@i5-w7 /iperf-3.1b3/src
$ find ./ -iname "*.[ch]" |xargs -n1 sed -i s'#iprintf#newprintf#g'

 

End then edited src/iperf_api.c

char template[] = "/tmp/iperf3.XXXXXX";
to
char template[] = "./iperf3.XXXXXX";

 

edit:
Updated to build 3.1b3
updated Cygwin 2.1.0-1
$ uname -a
CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64 Cygwin
 
BudMan@i5-w7 /usr/local/bin
$ cygcheck iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin
 
D:\iperf3.1_b3>iperf3.exe -v
iperf 3.1b3
CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64
Optional features available: None
 
D:\iperf3.1_b3>iperf3.exe -h
Usage: iperf [-s|-c host] [options]
       iperf [-h|--help] [-v|--version]

Server or Client:
  -p, --port      #         server port to listen on/connect to
  -f, --format    [kmgKMG]  format to report: Kbits, Mbits, KBytes, MBytes
  -i, --interval  #         seconds between periodic bandwidth reports
  -F, --file name           xmit/recv the specified file
  -B, --bind      <host>    bind to a specific interface
  -V, --verbose             more detailed output
  -J, --json                output in JSON format
  --logfile f               send output to a log file
  -d, --debug               emit debugging output
  -v, --version             show version information and quit
  -h, --help                show this message and quit
Server specific:
  -s, --server              run in server mode
  -D, --daemon              run the server as a daemon
  -I, --pidfile file        write PID file
  -1, --one-off             handle one client connection then exit
Client specific:
  -c, --client    <host>    run in client mode, connecting to <host>
  -u, --udp                 use UDP rather than TCP
  -b, --bandwidth #[KMG][/#] target bandwidth in bits/sec (0 for unlimited)
                            (default 1 Mbit/sec for UDP, unlimited for TCP)
                            (optional slash and packet count for burst mode)
  -t, --time      #         time in seconds to transmit for (default 10 secs)
  -n, --bytes     #[KMG]    number of bytes to transmit (instead of -t)
  -k, --blockcount #[KMG]   number of blocks (packets) to transmit (instead of -t or -n)
  -l, --len       #[KMG]    length of buffer to read or write
                            (default 128 KB for TCP, 8 KB for UDP)
  --cport         <port>    bind to a specific client port (TCP and UDP, default: ephemeral port)
  -P, --parallel  #         number of parallel client streams to run
  -R, --reverse             run in reverse mode (server sends, client receives)
  -w, --window    #[KMG]    set window size / socket buffer size
  -M, --set-mss   #         set TCP/SCTP maximum segment size (MTU - 40 bytes)
  -N, --no-delay            set TCP/SCTP no delay, disabling Nagle's Algorithm
  -4, --version4            only use IPv4
  -6, --version6            only use IPv6
  -S, --tos N               set the IP 'type of service'
  -Z, --zerocopy            use a 'zero copy' method of sending data
  -O, --omit N              omit the first n seconds
  -T, --title str           prefix every output line with this string
  --get-server-output       get results from server
  --udp-counters-64bit      use 64-bit counters in UDP test packets

[KMG] indicates options that support a K/M/G suffix for kilo-, mega-, or giga-

iperf3 homepage at: http://software.es.net/iperf/
Report bugs to:     https://github.com/esnet/iperf

D:\iperf3.1_b3>
 
Also -j option works

D:\iperf3.1_b3>iperf3.exe -s -J
{
        "start":        {
                "connected":    [{
                                "socket":       5,
                                "local_host":   "192.168.9.100",
                                "local_port":   5201,
                                "remote_host":  "192.168.9.8",
                                "remote_port":  49901
                        }],
                "version":      "iperf 3.1b3",
                "system_info":  "CYGWIN_NT-6.1 i5-w7 2.1.0(0.287/5/3) 2015-07-14 21:28 x86_64",
                "timestamp":    {
                        "time": "Tue, 21 Jul 2015 12:09:33 GMT",
                        "timesecs":     1437480573
                },
                "accepted_connection":  {
                        "host": "192.168.9.8",
                        "port": 49900
                },
                "cookie":       "storage.1437480588.553719.440b648674",
                "tcp_mss_default":      0,
                "test_start":   {
                        "protocol":     "TCP",
                        "num_streams":  1,
                        "blksize":      131072,
                        "omit": 0,
                        "duration":     10,
                        "bytes":        0,
                        "blocks":       0,
                        "reverse":      0
                }
        },
        "intervals":    [{
                        "streams":      [{
                                        "socket":       5,
                                        "start":        0,
                                        "end":  1,
                                        "seconds":      1,
                                        "bytes":        108701028,
                                        "bits_per_second":      869608224,
                                        "omitted":      false
 
<snipped>  Full output was too long to post

== iperf 3.1.0 ????-??-?? ==

The release notes for iperf 3.1.0 describe changes and new
functionality in iperf 3.1.0, but not present in 3.0.11 or any earlier
3.0.x release.

* Selected user-visible changes

  * SCTP support has been added (with the --sctp flag), on Linux,
    FreeBSD, and Solaris (issue #131).

  * Setting CPU affinity now works on FreeBSD.

  * Selection of TCP congestion now works on FreeBSD, and is now
    called --congestion (the old --linux-congestion option works
    but is now deprecated).

  * A new -I option for the server causes it to write a PID file,
    mostly useful for daemon mode (issue #120).

  * A --logfile argument can now force all output to go to a file,
    rather than to a file.  This is especially useful when running an
    iperf3 server in daemon mode (issue #119).

  * Various compatibility fixes for Android (issue #184, issue #185),
    NetBSD (issue #248), Solaris (issue #175, issue #178, issue #180,
    issue #211), vxWorks (issue #268).

  * A --udp-counters-64bit flag has been added to support very
    long-running UDP tests, which could cause a counter to overflow
    (issue #191).

  * A --cport option to specify the client-side port has been added
    (issue #207, issue #209, issue #239).

  * Some calculation errors with the -O feature have been fixed (issue
    #236).

  * A potential crash in the iperf3 server has been fixed (issue #257,
    issue #258).

  * Many miscellaneous bug fixes.

* Selected developer-visible changes

  * Consumers of libiperf can now get the JSON output for a
    just-completed test (issue #147).

  * Detection of various optional features has been improved to check
    for the presence or absence of platform functionality, not the name
    of platforms.

  * Out-of-tree builds now work (issue #265).

Updated first post in thread with new build number and link to file.

Link to comment
Share on other sites

  • 0

You're right, I found this morning, that I added "debug" package instead of "devel" .. (well well, I know)

 

Now it compiles (and works !) in x64 like a charm ! :)

Link to comment
Share on other sites

  • 0

BudMan, the x86 version you provided to us some month ago is not based on the same source code I've downloaded some days ago, even if it is the same version 3.0.11 (?!)

Some command line parameters are missing (particularly "--logfile"), so I've recompiled it.

For the ones who are interested in, here is iperf 3.0.11 for x64 and x86 including the corresponding html documentation : http://www.audouy.fr/share/iperf3.7z

Hope it will help :)

Regards,

Dji.

Link to comment
Share on other sites

  • 0

Yeah I switched over to 64 bit a few versions back, I can do a 32 bit version sure.. If work doesn't get to hectic today will do pretty soon - if not later tonight or tmrw morning when I get home.. I will do the 3.0.11 version and the new 3.1b3 version in 32bit for those still 32 bit ;)

 

Where did you get source from - I was not aware of any different revision in code for the 3.0.11

Link to comment
Share on other sites

  • 0

Of course, I've downloaded sources from github repository: https://github.com/esnet/iperf

 

Well for my really specific needs, I need both x86 and x64 for server side (because I have to install it from Windows 20012 x64 to Windows 2003 x86 servers... yes still exists !) but only x64 for client side (Windows PE 4.0 x64)

Link to comment
Share on other sites

  • 0

Yeah I can understand that there are some 32bit stuff out there.. I got side tracked yesterday and didn't get a chance to upload the 32bit version.  But sounds like you compiled yourself.. But there may be others in your situation so I will start putting both 32 and 64 bit versions out there.

 

I am no guru in compiling stuff, but basic stuff like this is fairly straight forward and easy to test working, etc.  And I have plenty of server space and bandwidth so if I can help out the next guy looking for a windows version of this great software I love doing it.

 

I wish I could figure out how I could compile it to run on windows without cygwin dll, etc. I did a bit of research if possible to imbed the dll in the ext but from my quick search doesn't seem like something that is supported by cygwin.

Link to comment
Share on other sites

  • 0

well I built the 32 bit versions the other day, but on neowin was down.  And now I am on the road - prob have to wait til I get back home to post them up.

Link to comment
Share on other sites

  • 0

well I built the 32 bit versions the other day, but on neowin was down.  And now I am on the road - prob have to wait til I get back home to post them up.

Working fine here, many thanks. I'd had issues with performance consistency with a previous build.

Are cyggcc_s-1.dll and cygstdc++-6.dll still required?

Link to comment
Share on other sites

  • 0

So look at the cygcheck output it lists the dlls that are used.  I will be posting up the other builds here as soon as I get some coffee ;)

 

edit: ok updated the front page with links to the 32bit versions.  The 32bit one of 3.11 still shows it needed this cygwin1 and cyggcc_s-1.dll

$ cygcheck iperf3.exe
Found: D:\cygwin\usr\local\bin\iperf3.exe
D:\cygwin\usr\local\bin\iperf3.exe
  D:\cygwin\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  D:\cygwin\bin\cyggcc_s-1.dll

BudMan@i5-w7 /usr/local/bin

Edited by BudMan
Link to comment
Share on other sites

  • 0

So 3.1 released today... So have compiled both 32 and 64 bit, also updated cygwin to 2.2.1

Here are the details. https://github.com/esnet/iperf

= iperf 3.1 2015-10-16 ==

The release notes for iperf 3.1 describe changes and new
functionality in iperf 3.1, but not present in 3.0.11 or any earlier
3.0.x release.

* Selected user-visible changes

  * SCTP support has been added (with the --sctp flag), on Linux,
    FreeBSD, and Solaris (issue #131).

  * Setting CPU affinity now works on FreeBSD.

  * Selection of TCP congestion now works on FreeBSD, and is now
    called --congestion (the old --linux-congestion option works
    but is now deprecated).

  * A new -I option for the server causes it to write a PID file,
    mostly useful for daemon mode (issue #120).

  * A --logfile argument can now force all output to go to a file,
    rather than to a file.  This is especially useful when running an
    iperf3 server in daemon mode (issue #119).

  * Various compatibility fixes for Android (issue #184, issue #185),
    iOS (issue #288), NetBSD (issue #248), Solaris (issue #175, issue
    #178, issue #180, issue #211), vxWorks (issue #268).

  * A --udp-counters-64bit flag has been added to support very
    long-running UDP tests, which could cause a counter to overflow
    (issue #191).

  * A --cport option to specify the client-side port has been added
    (issue #207, issue #209, issue #239).

  * Some calculation errors with the -O feature have been fixed (issue
    #236).

  * A potential crash in the iperf3 server has been fixed (issue #257,
    issue #258).

  * Many miscellaneous bug fixes.

* Selected developer-visible changes

  * Consumers of libiperf can now get the JSON output for a
    just-completed test (issue #147).

  * Detection of various optional features has been improved to check
    for the presence or absence of platform functionality, not the name
    of platforms.

  * Out-of-tree builds now work (issue #265).

$ cygcheck.exe iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin

D:\iperf3.1_64>iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1 i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:42 x86_64
Optional features available: None

32bit version

BudMan@i5-w7 /usr/local/bin
$ iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1-WOW i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:40 i686
Optional features available: None

BudMan@i5-w7 /usr/local/bin
$ cygcheck.exe iperf3.exe
Found: D:\cygwin\usr\local\bin\iperf3.exe
D:\cygwin\usr\local\bin\iperf3.exe
  D:\cygwin\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  D:\cygwin\bin\cyggcc_s-1.dll

BudMan@i5-w7 /usr/local/bin

D:\iperf3.1_32>iperf3.exe -v
iperf 3.1
CYGWIN_NT-6.1-WOW i5-w7 2.2.1(0.289/5/3) 2015-08-20 11:40 i686
Optional features available: None

D:\iperf3.1_32>

 

 

 

 

Link to comment
Share on other sites

  • 0

ok updated to 3.1.1, updated cygwin to 2.3.1

 

BudMan@i5-w7 /usr/local/bin
$ ./iperf3.exe -v
iperf 3.1.1
CYGWIN_NT-6.1 i5-w7 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64
Optional features available: None

BudMan@i5-w7 /usr/local/bin
$ cygcheck.exe iperf3.exe
Found: C:\cygwin64\usr\local\bin\iperf3.exe
C:\cygwin64\usr\local\bin\iperf3.exe
  C:\cygwin64\bin\cygwin1.dll
    C:\Windows\system32\KERNEL32.dll
      C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
      C:\Windows\system32\ntdll.dll
      C:\Windows\system32\KERNELBASE.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
      C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll

BudMan@i5-w7 /usr/local/bin
$

 

The 32bit version shows that it needs cyggcc_s-1.dll as well, so that is included in the 32bit zip.

 

== iperf 3.1.1 2015-11-19 ==

The release notes for iperf 3.1.1 describe changes and new
functionality in iperf 3.1.1, but not present in 3.1.

* User-visible changes

  * Some markup fixes have been made in the manpages for Debian
    compatibility (issue #291).

  * A bug where the -T title option was not being output correctly
    in JSON output has been fixed (issue #292).

  * Argument handling for some command-line options has been improved
    (issue #316).

* Developer-visible changes

  * A regression with C++ compatibility in one of the iperf header
    files has been fixed (issue #323).

 

files can be found here

http://files.budman.pw/iperf3.1.1_64.zip

http://files.budman.pw/iperf3.1.1_32.zip

 

Link to comment
Share on other sites

  • 0

Updated to 3.1.2 both 32 and 64, updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw

 

This release fixes a couple of minor bugs, including one that results in invalid JSON being emitted for UDP tests.

Link to comment
Share on other sites

  • 0

Updated to 3.1.3 both 32 and 64, and 3.0.12 both 32 and 64.  Updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw

 

sha256 for the new files are

98798CE0062217E0FF3F095AD56DA1A0DE5607FE    iperf3.1.3_32.zip
84B707F94005A70AA5B5373A47D9B00C55ED6C63    iperf3.0.12_32.zip
7AB40186AEC5490C8A6F34776D4FE09B073A62BC    iperf3.1.3_64.zip
4B10AC4227267AC0724F75B360A82D1808F93534    iperf3.0.12_64.zip

 

md5 of the new files are

6C30678073E6A180B197E1CFB8E27262    iperf3.0.12_32.zip
3439BF23397D16C5F44434DF3278669C    iperf3.1.3_32.zip
495B469D8FFF51E872F57CD47A07F09B    iperf3.0.12_64.zip
3218D0D8E067FB55F2CA9B3F647AE90B    iperf3.1.3_64.zip

 

Link to comment
Share on other sites

  • 0

Updated both 32 and 64 bit to 3.1.4 using latest cygwin 2.6.0, updated first post in thread with new download links

 

Or you can just go here and browse http://files.budman.pw


Budman@I5-WIN C:\build\iperf_3.1.4_32
> iperf3.exe -v
iperf 3.1.4
CYGWIN_NT-6.3-WOW i5-win 2.6.0(0.304/5/3) 2016-08-31 14:27 i686
Optional features available: None

 

Budman@I5-WIN C:\build\iperf_3.1.4_64
> iperf3.exe -v
iperf 3.1.4
CYGWIN_NT-6.3 i5-win 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64
Optional features available: None

 

File: iperf_3.1.4_32.zip
CRC-32: 7ff84eef
MD5: a8c7536370d5886269418dfe1cb5adf4
SHA-1: 10e06f0f5e81de881f3da806b6c1e0ad4c9f4e07

 

File: iperf_3.1.4_64.zip
CRC-32: 01507ea5
MD5: 878277454ff14cadc52af0839f55fd46
SHA-1: a0aad4d2429634d3408a90ab6d24a2792aedecbb

Link to comment
Share on other sites

  • 0

updated  to 3.1.5 using latest cygwin 2.6.1

 

http://files.budman.pw

 

Budman@I5-WIN C:\iperf\iperf3.1.5_32
> iperf3.exe -v
iperf 3.1.5
CYGWIN_NT-6.3-WOW i5-win 2.6.1(0.305/5/3) 2016-12-16 11:50 i686
Optional features available: None

 

Budman@I5-WIN C:\iperf\iperf3.1.5_64
> iperf3.exe -v
iperf 3.1.5
CYGWIN_NT-6.3 i5-win 2.6.1(0.305/5/3) 2016-12-16 11:55 x86_64
Optional features available: None

 

iperf3.1.5_32.zip

CRC32: 893af4ec
MD5: 445689c8344ced172930c508174e1bb8
SHA-256: ef12541b8ed10510cc8f0c08bae353be1065a2a49ab0f68c1a162a4a681f5ac3

 

iperf3.1.5_64.zip

CRC32: f2d11a99
MD5: 28828388a16fb458ab41994cce68640b
SHA-256: efe14c556a285e9651ddd4c3be33b583a4e0c962959d6199e0f9d5b5757022a9

Link to comment
Share on other sites

  • 0

Updated to 3.1.6 using latest cygwin 2.7

 

http://files.budman.pw

 

Budman@I5-WIN D:\iperf3.1.6_64bit
> iperf3.exe -v
iperf 3.1.6
CYGWIN_NT-6.3 i5-win 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64
Optional features available: None

 

File: iperf3.1.6_32bit.zip
CRC-32: 9a4953c2
MD5: 560d83225a6b9b6a0ec3cd6dedbb3b63
SHA-1: 627e11542df56ab1f64a0c89372eb7718717b3a5

 

File: iperf3.1.6_64bit.zip
CRC-32: 32a446a3
MD5: db88fd4e4f65dc5082d021874970c44f
SHA-1: cd0273f20dbe2bcaf704815db87ef34ccb55959b

 

Link to comment
Share on other sites

  • 0

New 3.2 build out

 

Budman@I5-WIN D:\iperf3.2_32bit
> iperf3.exe -v
iperf 3.2 (cJSON 1.5.2)
CYGWIN_NT-6.3-WOW i5-win 2.8.1(0.312/5/3) 2017-07-03 14:06 i686
Optional features available: authentication

 

Budman@I5-WIN D:\iperf3.2_64bit
> iperf3.exe -v
iperf 3.2 (cJSON 1.5.2)
CYGWIN_NT-6.3 i5-win 2.8.1(0.312/5/3) 2017-07-03 14:11 x86_64
Optional features available: authentication

 

http://files.budman.pw/iperf3.2_32bit.zip

CRC32: 9e4b913c
MD5: ff7fc42f6ba29e9f83c8bb8e0066f722
SHA-1: 68ad3a0f0c2f30c1756f0a5eb39e1062e6beb6f4

http://files.budman.pw/iperf3.2_64bit.zip

CRC32: add96290
MD5: 7a014ff67b1d678f546ead2360820d47
SHA-1: 98ed98ac6d392a4484e5151ab2f714390c99b52e
 

Link to comment
Share on other sites

  • 0

Really?  Thanks I will look into - but the only thing on there are iperf zips and md5 files.. But thanks for bring that to my attention.  Do you have a link that explains why?  I will try and query the eset database.

 

Wow that company freaking sucks!  I have to email them and wait 2 days maybe?  And they don't list WHY its listed..

 

it shows clean on every scanner I check..  Other then them..

 

scan.thumb.png.943469e6a0955c10e9b2f4bf93003521.png

 

Total virus shows it clean - other than eset.. Such BS!!  Thanks for bringing to my attention!  If you could report it in your tool as false and let them rescan it that would be great, I already have email out to samples@eset.com to have them double check.. Some actual details of what they detected.. Your not going to list what is detected, then your full of it!!

Link to comment
Share on other sites

  • 0

Unflagged as false positive.

 

Apparently they fixed the isssue, I'm able to get to that URL without disabling Eset now.

Link to comment
Share on other sites

  • 0

Yeah just got this email few hours ago

unblocked.thumb.png.2f4122fb09f8ad18f0c1259da9d73b9a.png

 

Thanks for bringing to my attention @Marshall

 

And now virustotal scan shows clean on all 66, the eset listing is gone

scan.thumb.png.45eed021dbb8f6f788969787810af2df.png

 

  • Like 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Usama Jawad96
      Microsoft Office 2021 is coming on October 5, LTSC available today
      by Usama Jawad

      Back in February, Microsoft announced upcoming updates to two variants of Office, namely Office Long Term Servicing Channel (LTSC) and Office 2021. Both are quite similar in nature with a key difference being that the former is meant for organizational use and the latter is intended for consumers. Both offer five years of mainstream support via a one-time "perpetual" license purchase, but that also means that they won't get any new features or updates until the next perpetual license release. They are primarily intended for organizations and consumers who can't migrate to the cloud to take advantage of Microsoft 365, which gets updated way more frequently.

      Microsoft announced a commercial preview of its LTSC releases in April, and now it has announced that Office LTSC has become generally available (GA) to organizations starting today while Office 2021 will hit GA on October 5, which is the same date as Windows 11's general rollout.

      Microsoft has emphasized that Microsoft 365's subscription-based system is its preferred direction for the future, it understands that in some scenarios, organizations can't migrate to the cloud or connect certain services to the internet. As such, LTSC releases has more value for them. Although this LTSC release contains performance enhancements and improved accessibility, Microsoft has noted that it cannot take advantage of cloud-driven hybrid security capabilities, AI automation, and real-time collaboration. The company has noted that it will be making "investments" to make it easier for LTSC customers to shift to Microsoft 365 in the future.

      Although you can dive into the full feature-set in Microsoft's documentation here, some highlights are that Office LTSC supports OpenDocument format (ODF 1.3), includes more Office Add-ins JavaScript APIs, and features new languages. It is also getting Dynamic Arrays and the new XLOOKUP function in Excel, Line Focus in Word, and the ability to record a slideshow with narration in PowerPoint.

      Another major change from previous releases is that Office LTSC ships with Teams as part of the installed features, rather than Skype for Business, but Teams is treated differently than other Office apps. Unlike the others, it will continue to get updates continuously over time, but you also only get access to the free version of Teams, since the premium version is licensed separately. You can learn more about managing the free version of Teams here.

      Office 2021 is the consumer version of "perpetual" Office and will replace Office 2019 on October 5, 2021. It will be available on Windows and macOS just like Office LTSC. If you're an IT admin at an organization looking to upgrade to Office LTSC generally available today, you can go through Microsoft's deployment instructions here.

    • By Usama Jawad96
      PSA: Microsoft is ending support for Silverlight next month
      by Usama Jawad

      Silverlight is Microsoft's framework for the development of web applications. It was released in 2007 and its most recent release came almost three years ago. As of now, the legacy framework is only supported on Internet Explorer, and that is set to change soon as well. Silverlight is reaching end of support on October 12, 2021, as pointed out by Tero Alhonen on Twitter.



      The writing's been on the wall for quite some time now for Silverlight. Silverlight 4 was the primary development platform for Windows Phone, and we all know what happened to that. Even way back in 2011, we had former Microsoft executives proclaiming the death of Silverlight. Netflix transitioned from Silverlight to HTML5 in 2013 too. Microsoft Edge does not support Silverlight outside of IE mode, Google Chrome ended support for it in September 2015, and Mozilla Firefox did the same in March 2017.

      The dedicated Microsoft Silverlight portal shows a banner about impending end of support and points to a support document detailing some more information.

      Microsoft says that until the end of support date on October 12, it will continue providing technical assistance to customers using Silverlight 5 only. This includes paid support for Silverlight applications running on Internet Explorer 11 (IE11) on the following platforms:

      Windows 10 Windows Server 2016 Windows 8.1 Windows Server 2012 R2 Windows Server 2012 Windows Embedded 8.1 Industry Windows Embedded 8 Standard POSReady 7 Thin PC 7 Microsoft has emphasized that it is not planning any move to kill off Silverlight applications but it is important to note that software running on this framework will not get any security or feature updates. Similarly, customers who purchased Silverlight perpetual licenses are still legally licensed to utilize it, without support. No customer is eligible for extended support past October 12, even if they offer to pay for it. The company has also warned that the perpetual Silverlight license cannot be redistributed.

      After the aforementioned date, the Silverlight portal will still be accessible, but it will not offer an installer. For web-based applications, Microsoft has recommended Blazor as an alternative, while WinUI 3 with Windows App SDK has been encouraged if you're considering moving to a desktop-based application not dependent upon the browser.

      Although Internet Explorer 11 - the last browser that currently supports Silverlight - is being phased out, Microsoft says that Silverlight apps will continue to work in IE mode in Edge.

    • By Usama Jawad96
      Microsoft: Running Windows 11 on M1 Macs is not a supported scenario
      by Usama Jawad

      Around a month ago, Parallels announced that its Desktop 17 software supports running Windows 11 on both Intel and M1 Macs. However, users would only be able to emulate the Windows on ARM variant of the OS. It is important to note that in order to get Windows on ARM up and running on virtualization software like Parallels, you have to grab and utilize a virtual hard disk file from a Windows Insider Preview build, as noted by XDA.

      That said, in a statement issued to The Register recently, a Microsoft spokesperson has confirmed that running Windows 11 on M1 Mac devices isn't a "supported scenario". What this means is that while you can install the OS via Parallels on an M1 Mac, if you run into any issue, Microsoft isn't responsible for providing a workaround or a fix. Furthermore, if at any point in the future, Microsoft makes changes to the OS that renders this virtualization impossible, people who paid for software like Parallels Desktop will be left out in te cold.

      It is important to understand the importance of this caveat as a Windows 11 Dev Channel build recently starting throwing errors related to hardware compatibility on M1 Macs, and although Parallels was able to update its software to resolve the issue, there might be a future scenario where a quick fix is not possible. Interestingly, Thurrott does say that a source told him that Windows on ARM for M1 Macs would be officially supported by Microsoft in September. However, this seems to be very unlikely to happen now, in light of the recent statement.

    • By Abhay V
      Microsoft Weekly: Windows 11 builds, new zero-day vulnerability, and gaming news
      by Abhay V



      Another week has passed, and a lot has happened in the world of Microsoft. There were new Windows 11 builds for both the Dev and Beta channels, information about another refreshed app for the OS came from Windows chief Panos Panay, a few vulnerabilities were reported on - including a zero-day that affects all Windows versions, some security fixes, and a bunch of gaming news. Check all this out and much more in our weekly Microsoft digest for September 5 – September 11.

      Windows 11 builds, new apps, and a rebranded service


      As was expected, Microsoft released new Windows 11 builds for both Dev and Beta channel users. While Dev channel users got build 22454, Beta channel users were served build 22000.184. The Dev channel build brought a few minor UI improvements, such as a modern right-click menu for the Recycle Bin and more. It also included a ton of bug fixes, something that the Beta channel did not see, as those users received a couple of fixes to address translation inconsistencies. The firm did, however, note that fixes that were made as part of the Dev channel build will be released to the stable version in the way of servicing updates after the OS releases on October 5, which does seem odd. Additionally, Dev channel users that wanted to perform a clean install could download new ISO images of build 22454.

      The week also brought news of a Photos app refresh, a welcome addition for those who have hoped for the in-box app to be more aesthetically pleasing and feature-rich. Of course, another expectation is that the app brings some much-needed reliability and performance improvements. It is to be seen if that is the case, as the app is yet to begin rolling out.

      Speaking of refreshes, Microsoft announced a rebrand of its news service to Microsoft Start. The new service doesn’t bring much in the way of additions or features and the branding change is being applied across platforms, including on the web, in Windows, and the mobile apps. In the area of updates, there is also a new Edge 95 build for the Dev channel. It does not come with many new features, which is because it is still an early build for major version 95.

      For those still on the fence about installing Windows 11 builds on their machines, we have been looking at the various components of the OS and documenting them in our Closer Look series. This week, we went over the improvements and changes coming to the Virtual Desktop experience in Windows 11 and compared it to that in Windows 10. And to gin up enthusiasm about the upcoming OS, Microsoft has posted a new ad on YouTube and is also speaking about how the OS makes the best of new hardware.

      Windows zero-day vulnerability, Outlook bug, and Azure patch


      There were a couple of security issues reported this week, the most significant of which was the zero-day in Windows that can enable specially tailored Office files to let attackers perform remote code execution. Microsoft acknowledged the vulnerability, adding that it is currently being exploited in the wild. The firm has said that it is working on a fix and expects to release a fix soon. The zero-day affects all Windows versions going back to Windows 7 and the corresponding Windows Server release.

      Another security vulnerability affected Outlook users, where a bug had the potential to falsely flag phishing emails as genuine, thanks to the service not filtering IDs from Internationalized Domain Names (IDNs). While the firm denied having plans to fix the issue to the researcher that discovered it, it appeared that the firm changed its mind and fixed the issue, which is always a good thing.

      On the positive side of things, the Redmond firm changed how Microsoft 365 apps deal with Trusted Documents to make them more secure. Now, Trusted Documents no longer override the Protected View restrictions and adheres to pre-set policies. Another fix – this time affecting commercial customers – came in the way of a patch for a vulnerability in the Azure Container Instances (ACI) service. The issue risked data leaks across the same clusters, but the firm was quick to note that it found no indication of active exploits.

      Halo Infinite’s next multiplayer preview, Alan Wake Remastered screenshots, and more
      Starting off the week’s gaming roundup is news about Halo Infinite’s next multiplayer preview, which starts September 24. However, the sign-up cut-off is soon approaching, with the date set for September 13. Those eligible will receive invites on both the PC and Xbox platforms. As for the changes, 343 Industries detailed the tweaks it is planning to make based on the first technical preview's feedback.

      For those excited about Alan Wake Remastered, screenshots of the game appeared on Amazon UK before the official announcement arrived with details on the changed elements and PC system requirements.

      An extended look at Marvel's Midnight Suns also came this week in the form of visceral gameplay footage. Considering that the footage is of the game in its alpha stages, the animations and visuals were still unpolished but gave a better look at the villains. Fallout 76 Worlds Update also began rolling out, bringing Public and Custom Worlds. However, only Fallout 1st subscribers will be able to host Custom Worlds. Xbox Game Pass Ultimate subscribers, luckily, will receive Fallout 1st subscription for one month. Bethesda also acknowledged an issue with Season 5’s rank-ups, which is why it extended the season by two weeks.

      Square Enix revealed the Fall and Winter 2021 Roadmap for Marvel’s Avengers, noting that it is working to address player’s concerns and bringing improvements to Gear, Resources, and Cosmetics.

      Coming to Microsoft’s gaming subscriptions, this week’s Deals with Gold included hefty discounts on games from BioShock, Borderlands, and Dragon Ball franchises. Additionally, this week’s Xbox Free Play Days games included Madden NFL 22, Tom Clancy’s Rainbow Six Siege, and Blasphemous.

      For Forza Horizon 5 fans, we have listed the current list of cars confirmed by Playground Games , which is over 400 in number. Cars from the likes of BMW and Tesla are obvious omissions and there is no word on whether they are expected later. This week, we also posted a list of every 120FPS supported game on Xbox Series X and PlayStation 5 (PS5).

      Rounding off gaming news is Flight Simulator’s next World Update. This time, central European nations are receiving love, including Austria, Germany, and Switzerland. As usual, there are a bunch of new airports, New Bush Trips, landing challenges, and Discovery flights, and overall improvements to the visuals in those countries.

      Dev channel:
      Microsoft will soon let chat supervisors delete messages in Teams chats Microsoft acquires a video-editing software startup named Clipchamp Xbox Insiders will receive an update for their controllers that improves latency Microsoft offers GPU-accelerated ML training on Windows 10 and WSL via TensorFlow-DirectML Benchmarks show Ubuntu 21.10 outperform Windows 11 in certain use-cases You can still use proper Internet Explorer (IE) in Windows 11 using a Chrome extension Logging off:


      When Windows 11 began being offered to testers, it was discovered that Windows 11 Home users could not complete the setup process without an internet connection. We found out a workaround, which was soon patched. Now, there is yet another way to bypass this block, which we have detailed in our guide here. Big thanks to Neowin member warwagon for sharing with us the method.

      Missed any of the previous columns? Check them all out at this link.



      If you’d like to get a daily digest of news from Neowin, we have a Newsletter you can sign up to either via the ‘Get our newsletter’ widget in the sidebar, or through this link.

    • By hellowalkman
      Latest Ubuntu 21.10 blows the wind out of Windows 10 / 11 in certain performance tests
      by Sayan Sen

      Microsoft's next-gen Windows 11 OS is set to release publicly on the 5th of October which is about a week earlier than the release date for Ubuntu 21.10 (codenamed "Impish Indri"), the latter being on October 14. As a result, folks over at Phoronix were curious and wondered what the performances differences might be like between the two upcoming operating systems.

      According to the benchmark results obtained in the comparison across several workstation applications, it seems Ubuntu 21.10 is quite a bit ahead by around 50%, or much more, in some of the tests especially those that involve more dependency on the CPU, indicating that the OS is probably better at utilizing the available CPU resources than Windows. GPU-based applications however have generally tended to favor Microsoft's OS, however, the performance gaps aren't as big in Windows' favor.

      The test system used by the publication consists of:

      AMD Ryzen 9 5900X GeForce RTX 3090 16GB RAM Windows 10 21H1 / Windows 11 Build 22000.168 Ubuntu 21.10







      From the numbers, it is noticeable that Windows 11 doesn't really offer much of any significant improvement, if at all, over Windows 10, at least with this build version. The final image that shows WebP image encoding exhibits a certain anomaly as it is observed that the Windows 10 system is much faster than the Windows 11 one, possibly indicating some bug in the latter.



      Overall, Ubuntu 21.10 appears to be ~10% faster than Windows 10 and slightly more so in the succeeding Windows 11 build. You can find the full performance review with a lot more benchmark numbers on Phoronix's website linked in the source link below.

      Source and images: Phoronix