• 0

Iperf 3.9 Windows build


Question

+BudMan

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

 

  • Like 12
Link to post
Share on other sites

Recommended Posts

  • 0
+BudMan

So I prettied up the dir listing, got rid of some old versions.  And enabled https for those that think everything should be https ;)

 

https://files.budman.pw

 

If anyone wants/needs version prior to 3.1.1 just let me know and can put it up.

  • Like 1
Link to post
Share on other sites
  • 0
+BudMan

Added 3.3

 

Budman@I5-WIN D:\Iperf\iperf3.3_32
> iperf3.exe -v
iperf 3.3 (cJSON 1.5.2)
CYGWIN_NT-6.3-WOW i5-win 2.9.0(0.318/5/3) 2017-09-12 10:41 i686
Optional features available: authentication

 

Budman@I5-WIN D:\Iperf\iperf3.3_64
> iperf3.exe -v
iperf 3.3 (cJSON 1.5.2)
CYGWIN_NT-6.3 i5-win 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64
Optional features available: authentication

 

File: iperf3.3_64.zip
MD5: 49095ccb2442101d2a1ffc6213f3d1b9
SHA-256: 1fea7ae97b8ec5ab1c61ef1afcf7afd491d37ef41061a845f9bb8477425c66db

 

File: iperf3.3_32.zip
MD5: b6ad4c094a18196e0798e1a2825bc609
SHA-256: 919978ac0b574d7662d5b0e58174a6107002db96e7592929a9a28938516a2c5f

 

https://files.budman.pw/

 

 

 

  • Like 1
Link to post
Share on other sites
  • 0
+BudMan

New 3.4 is out

 

Budman@I5-WIN D:\iperf3.4_64

> iperf3.exe -v
iperf 3.4 (cJSON 1.5.2)
CYGWIN_NT-6.3 i5-win 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64
Optional features available: CPU affinity setting, authenticatio

 

Budman@I5-WIN D:\iperf3.4_32
> iperf3.exe -v
iperf 3.4 (cJSON 1.5.2)
CYGWIN_NT-6.3-WOW i5-win 2.10.0(0.325/5/3) 2018-02-02 15:21 i686
Optional features available: authentication

 

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

 

https://github.com/esnet/iperf/blob/master/RELEASE_NOTES

release notes

== iperf 3.4 2018-02-14 ==

* Notable user-visible changes

  * The -A (set processor affinity) command-line flag is now supported
    on Windows (#665).

  * iperf3 now builds on systems lacking a daemon(3) library call
    (#369).

  * A bug in time skew checking under authentication was fixed (#674).

  * IPv6 flow labels now work correctly with multiple parallel streams
    (#694).

  * The client no longer closes its control connection before sending
    end-of-test statistics to the server (#677). This fixes a
    regression introduced in iperf-3.2.

  * Sending output to stdout now makes errors go to stderr, as per
    UNIX convention (#695).

  * A server side crash in verbose output with a client running
    multiple parallel connections has been fixed (#686).

  * The --cport option can now be specified without the --bind option.
    Using the --cport option on Linux can eliminate a problem with
    ephemeral port number allocation that can make multi-stream iperf3
    tests perform very poorly on LAGG links.  Also, the --cport option
    now works on SCTP tests (#697).

* Notable developer-visible changes

  * iperf3 now builds on (some) macOS systems older than 10.7 (#607).

  * Some unused code and header inclusions were eliminated (#667,
    #668).  Also some code was cleaned up to eliminate (or at least
    reduce) compiler warnings (#664, #671).

  • Like 1
Link to post
Share on other sites
  • 0
+BudMan

3.5 is out

 

== iperf 3.5 2018-03-02 ==

* Notable user-visible changes

  * iperf3 no longer counts data received after the end of a test in
    the bytecounts.  This fixes a bug that could, under some
    conditions, artificially inflate the transfer size and measured
    bitrate.  This bug was most noticeable on reverse direction
    transfers on short tests over high-latency or buffer-bloated
    paths.  Many thanks to @FuzzyStatic for providing access to a test
environment for diagnosing this issue (#692).

 

Budman@I5-WIN D:\iperf3.5_32
> iperf3.exe -v
iperf 3.5 (cJSON 1.5.2)
CYGWIN_NT-6.3-WOW i5-win 2.10.0(0.325/5/3) 2018-02-02 15:21 i686
Optional features available: authentication

 

Budman@I5-WIN D:\iperf3.5_64
> iperf3.exe -v
iperf 3.5 (cJSON 1.5.2)
CYGWIN_NT-6.3 i5-win 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64
Optional features available: CPU affinity setting, authentication

 

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
 

Link to post
Share on other sites
  • 0
+BudMan

Yeah like anyone would care?  Its XP... Been dead OS for years and years...

https://www.microsoft.com/en-us/windowsforbusiness/end-of-xp-support

 

So April of 2014 - your talking 4 years ago.. What next you will want it to run in Dos 6.2? ;)

 

Sorry but I am not going to troubleshoot it.. These versions work on my 64 bit system, why I still do the 32 bit I don't really know - but it also runs on my 64 bit system..

 

Hint move to a current 64 bit windows ;)

Link to post
Share on other sites
  • 0
NoNeed4Mercy

anyone encouters this new problem in newer versions!

 

I was running the latest windows version before from the official site (very old from 2016). It was working flawlessly except for udp mode. So i wanted to update and build the code by myself. It seemed to work for the first time, but the server immediatly crashes after the first connect, making a second connect impossible. 

 

I thought i made a bad build and downloaded several versions from here.. All are crashing after the first connect (which is successfull).

 

Oh and one thing i forgot. This only happens in "silent mode" server. If i start the server by myself via cmd, it will stay open. If i start the server from windows server (with no gui) the server crashes after one connect. 

 

Any hint/tip would be great! 

Edited by NoNeed4Mercy
missing information
Link to post
Share on other sites
  • 0
NoNeed4Mercy
50 minutes ago, NoNeed4Mercy said:

anyone encouters this new problem in newer versions!

 

I was running the latest windows version before from the official site (very old from 2016). It was working flawlessly except for udp mode. So i wanted to update and build the code by myself. It seemed to work for the first time, but the server immediatly crashes after the first connect, making a second connect impossible. 

 

I thought i made a bad build and downloaded several versions from here.. All are crashing after the first connect (which is successfull).

 

Oh and one thing i forgot. This only happens in "silent mode" server. If i start the server by myself via cmd, it will stay open. If i start the server from windows server (with no gui) the server crashes after one connect. 

 

Any hint/tip would be great! 

Delete my post! -D is working in newer versions for windows service! 

Link to post
Share on other sites
  • 0
+BudMan

Yeah I grabbed it the other day just haven't gotten around to compile yet.  Prob today

Link to post
Share on other sites
  • 0
+BudMan

Well might take me a bit to get this compiled running into an error

 

budman@i5-win /iperf-3.6
$ make
Making all in src
make[1]: Entering directory '/iperf-3.6/src'
make  all-am
make[2]: Entering directory '/iperf-3.6/src'
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.     -g -O2 -Wall -MT iperf_api.lo -MD -MP -MF .deps/iperf_api.Tpo -c -o iperf_api.lo iperf_api.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -g -O2 -Wall -MT iperf_api.lo -MD -MP -MF .deps/iperf_api.Tpo -c iperf_api.c  -DDLL_EXPORT -DPIC -o .libs/iperf_api.o
In file included from /usr/include/w32api/Windows.h:95:0,
                 from iperf_api.c:67:
/usr/include/openssl/ossl_typ.h:159:29: error: expected ‘)’ before numeric constant
 typedef struct X509_name_st X509_NAME;
                             ^
/usr/include/openssl/ossl_typ.h:207:33: error: expected ‘)’ before numeric constant
 typedef struct ocsp_response_st OCSP_RESPONSE;
                                 ^
make[2]: *** [Makefile:897: iperf_api.lo] Error 1
make[2]: Leaving directory '/iperf-3.6/src'
make[1]: *** [Makefile:665: all] Error 2
make[1]: Leaving directory '/iperf-3.6/src'
make: *** [Makefile:386: all-recursive] Error 1

budman@i5-win /iperf-3.6
$

Link to post
Share on other sites
  • 0
+BudMan

Ok I got it working.. Have not had chance to fully test all features but it compiled

 

In the header file ossl_typ.h I made the change

#ifndef HEADER_OPENSSL_TYPES_H
# define HEADER_OPENSSL_TYPES_H

#include <limits.h>

#ifdef  __cplusplus
extern "C" {
#endif

# include <openssl/e_os2.h>

# include <windows.h>

 

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

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

 

budman@i5-win /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\ntdll.dll
      C:\WINDOWS\system32\KERNELBASE.dll

 

C:\test\iperf3.6_64bit>iperf3.exe -v
iperf 3.6 (cJSON 1.5.2)
CYGWIN_NT-10.0 i5-win 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64
Optional features available: CPU affinity setting

 

  • Like 1
Link to post
Share on other sites
  • 0
rambo007

Awesome! Thanx! It's working flawlessly for me so far ?

Link to post
Share on other sites
  • 0
+BudMan

Great I will get around to the 32bit version maybe this weekend.. Not sure why anyone would still be using 32bit anyway..

  • Haha 1
Link to post
Share on other sites
  • 0
+BudMan

Thanks... Prob do it this weekend...

Link to post
Share on other sites
  • 0
+BudMan

Ok got 3.7 compiled - had to do the same edit to ossl_typ.h as above

 

budman@i5-win /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\ntdll.dll
      C:\WINDOWS\system32\KERNELBASE.dll

budman@i5-win /usr/local/bin
budman@I5-WIN E:\output\iperf3.7_64
$ iperf3.exe -v
iperf 3.7 (cJSON 1.5.2)
CYGWIN_NT-10.0-18362 i5-win 3.0.7-338.x86_64 2019-04-30 18:08 UTC x86_64
Optional features available: CPU affinity setting

The --bidir option is working

budman@I5-WIN E:\output\iperf3.7_64
$ iperf3.exe -c 192.168.9.9 --bidir
warning: Ignoring nonsense TCP MSS -2146716416
Connecting to host 192.168.9.9, port 5201
[  5] local 192.168.9.100 port 53200 connected to 192.168.9.9 port 5201
[  7] local 192.168.9.100 port 53201 connected to 192.168.9.9 port 5201
[ ID][Role] Interval           Transfer     Bitrate
[  5][TX-C]   0.00-1.00   sec  56.6 MBytes   475 Mbits/sec
[  7][RX-C]   0.00-1.00   sec  99.3 MBytes   832 Mbits/sec
[  5][TX-C]   1.00-2.00   sec  42.0 MBytes   352 Mbits/sec
[  7][RX-C]   1.00-2.00   sec   112 MBytes   943 Mbits/sec
[  5][TX-C]   2.00-3.00   sec  52.2 MBytes   438 Mbits/sec
[  7][RX-C]   2.00-3.00   sec   112 MBytes   942 Mbits/sec
[  5][TX-C]   3.00-4.00   sec  56.2 MBytes   472 Mbits/sec
[  7][RX-C]   3.00-4.00   sec   112 MBytes   943 Mbits/sec
[  5][TX-C]   4.00-5.00   sec  58.8 MBytes   493 Mbits/sec
[  7][RX-C]   4.00-5.00   sec   112 MBytes   942 Mbits/sec
[  5][TX-C]   5.00-6.00   sec  24.2 MBytes   203 Mbits/sec
[  7][RX-C]   5.00-6.00   sec   112 MBytes   943 Mbits/sec
[  5][TX-C]   6.00-7.00   sec  53.0 MBytes   445 Mbits/sec
[  7][RX-C]   6.00-7.00   sec   112 MBytes   939 Mbits/sec
[  5][TX-C]   7.00-8.00   sec  69.0 MBytes   579 Mbits/sec
[  7][RX-C]   7.00-8.00   sec   112 MBytes   942 Mbits/sec
[  5][TX-C]   8.00-9.00   sec  26.1 MBytes   219 Mbits/sec
[  7][RX-C]   8.00-9.00   sec   112 MBytes   943 Mbits/sec
[  5][TX-C]   9.00-10.00  sec  62.2 MBytes   522 Mbits/sec
[  7][RX-C]   9.00-10.00  sec   112 MBytes   939 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID][Role] Interval           Transfer     Bitrate
[  5][TX-C]   0.00-10.00  sec   500 MBytes   420 Mbits/sec                  sender
[  5][TX-C]   0.00-10.00  sec   500 MBytes   420 Mbits/sec                  receiver
[  7][RX-C]   0.00-10.00  sec  1.09 GBytes   934 Mbits/sec                  sender
[  7][RX-C]   0.00-10.00  sec  1.08 GBytes   931 Mbits/sec                  receiver

iperf Done.

budman@I5-WIN E:\output\iperf3.7_64

 

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

 

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

 

 

  • Like 2
Link to post
Share on other sites
  • 0
boxsmiley

thanks budman.  you are awesome.  created account just to say thanks for providing the fix for ossl_typ.h.  

Link to post
Share on other sites
  • 0
+BudMan

Thanks - stick around its good place!  So you were trying to compile it yourself and ran into that issue? And found this thread? Trying to recall where I found the fix myself, I am not any sort of guru at compiling stuff... But I get the basics and can follow instructions ;)

  • Like 1
Link to post
Share on other sites
  • 0
spanjokus

Thank you very much for the current version of the utility.

Link to post
Share on other sites
  • 0
+BudMan

@spanjokus Glad you found it and people are making use of it..  When next version comes out, will be posting here as well.  If you notice next release is out before I do - just mention my name here, and I will notice it for sure and post it up.

Link to post
Share on other sites
  • 0
aflurko

there is upgraded version of Cygwin1.dll:

https://github.com/esnet/iperf/issues/960

and i quote: " There was a bug in the cygwin1.dll that limited the receive buffer size for TCP sends. This caps the throughput on all tools that use cygwin including iperf."

 

 maybe it's worth making an upgrade for your compilation?

  • Like 1
Link to post
Share on other sites
  • 0
+BudMan

Thanks for the info... Will for sure do an update!

Link to post
Share on other sites
  • 0
+BudMan

Ok updated cygwin, did a new compile here is the new update

 

$ iperf3.exe -v
iperf 3.7 (cJSON 1.5.2)
CYGWIN_NT-10.0-18363 i5-win 3.1.4-340.x86_64 2020-02-19 08:49 UTC x86_64
Optional features available: CPU affinity setting

 

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

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

edit:  I again had to make the change to ossl_typ.h shown above to get it to compile... My change had gotten over witten with the updated of cygwin.

  • Like 1
Link to post
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
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Nero C
      Windows Terminal to gain Settings UI in the next version
      by Nero Cui

      Microsoft released Windows Terminal in 2019 replacing the default Windows Console that PowerShell and CMD use by default. The new terminal program contains many features that command-line users have been asking for years like tabs, profiles, and modern text rendering. Although the JSON based settings allow users to customize the app, many users have asked for a GUI page (Graphic User Interface) for the settings menu because editing JSON, while flexible, is very hard.

      Today, a program manager (Kayla Cinnamon) from Microsoft teased on Twitter that Settings GUI is coming in the next preview version of Windows Terminal. From the GIF, we can see that the Settings page opens in one of the tabs just like how a new terminal tab would. The design seems to be following the Windows 10 Settings app, featuring a sidebar on the left and a detailed page on the right.



      Users who wish to manually edit the Settings JSON file still have the option to do so according to the GIF, but GUI is a nice feature for most users who just want to quickly launch and change some settings. The sidebar suggests that users will be able to customize areas of the app and each of the profiles.

      This new feature will soon come to a Windows Terminal Preview release. More information is available through Windows Terminal's GitHub page.

      Source: Twitter

    • By Nero C
      Microsoft doubles down on Win32
      by Nero Cui

      Microsoft has been trying to modernize Windows and its development platform for a decade now. With Windows 8's Metro UI, Windows RT, Windows 10's UWP, Project Reunion and Windows 10X, Microsoft are trying their best to convince users and developers to move to a modern platform, but it apparently doesn't mean the end of Win32 as the company had just released a major capability to make it easier to consume Win32 APIs in programming languages other than C or C++.



      According to the blog post, Win32 APIs used to be only available to C and C++ developers, and programs developed in other languages needed to go through an error-prone wrapping or binding process. This process used to be done by the developers and it would only benefit the single language that the developers target. Moreover, the huge number of Win32 APIs available also doesn't make this process easier.

      To make consuming Win32 APIs easier in languages other than C or C++, Microsoft released new tooling called win32metadata. As stated by Microsoft:

      According to Microsoft, developers can use win32metadata to generate wrappers to Win32 APIs making the process much easier and less error-prone than manually writing every single one of them. Following this effort, the C# wrapper library C#/Win32 by Andrew Arnott and Rust wrapper library windows-rs by Microsoft are utilizing win32metadata to make Win32 APIs available in these two languages.

      Microsoft is hoping, with this tool, more languages will be able to make use of Win32 APIs. More information can be found on the project's GitHub page.

      Source: Windows Blog

    • By Abhay V
      A near-final build of Windows 10X has leaked to the web
      by Abhay Venkatesh



      A near-final build of Windows 10X has leaked on to the web, giving those interested in going through the tricky process of installing it a glimpse at Microsoft’s latest OS – a competitor to Google’s lightweight Chrome OS. The initial release is expected to be aimed only at single screened PCs and is reportedly set to launch this spring.

      Windows 10X was first showed off back in October 2019 and was aimed at dual-screened devices like the Surface Neo. However, with the Neo delayed indefinitely, the Redmond giant repurposed the OS for single-screened devices. Additionally, while the OS was expected to debut with support for Win32 apps through a virtualization technology called VAIL, those plans reportedly changed, making Windows 10X an offering slated to debut on low-end devices due to its lightweight nature.

      Microsoft is supposedly planning to add Win32 app support in the future and the OS is not expected to arrive on new form factors – such as dual-screened devices – till at least 2022. A report from The Verge suggests that the leaked build contains support for Win32 apps in a developer-only mode which cannot be accessed by general users. For now, the offering runs UWP apps from the Microsoft Store and Progressive Web Apps through the Chromium-based Edge browser.

      With the development of the company’s lightweight OS now nearing completion, it will be interesting to see when the firm plans to unveil the offering officially. Rumors are making the rounds that the launch will be one without much fanfare. OEM partners are also expected to unveil low-power PCs running Windows 10X aimed at the education market and the like in the coming months.

      Considering the risks and complexities associated with installing leaked builds, we will not be posting links to any resources for the build. Additionally, we always urge users to exercise caution and not install these builds on their main machines.

    • By Abhay V
      New report details the possible changes coming with Windows 10's Sun Valley update
      by Abhay Venkatesh



      Microsoft is said to be working on a major overhaul for Windows 10 due for release in the second half of this year. A recent job listing was also spotted that hinted at a “sweeping visual rejuvenation of Windows”, providing credence to reports about the revamp. While glimpses of what the upcoming designs might look like were provided by the updated Alarms & Clock app and the latest News and interests section in the Insider builds, that’s all there is to work with, currently.

      Now, a new report from Windows Central’s Zac Bowden sheds light on the possible changes coming to Windows 10. The information comes from sources close to the Redmond firm’s plans, based on which the publication has also created a few mockups. Changes and refreshes are expected to be made to the Start Menu, taskbar, Action Center, in-box apps, and more, along with new OS features.

      Windows 10X Action Center mockup | Image credit: Windows Central As reported earlier, the focus is expected to bring about a consistent user interface for the various parts of the OS, including consistent design elements such as rounded corners – something that some apps like Calculator have already begun receiving. The firm is also reportedly aiming to simplify the taskbar design by moving icons into a redesigned Action Center – a component that might be shared with Windows 10X. The Action Center is said to sport individual sections for media, notifications, and quick settings.

      Windows 10 Sun Valley Start Menu mockup | Image credit: Windows Central Unsurprisingly, the Start Menu too will feature rounded corners and an updated design. Bowden speculates that the firm might offer users the option to switch between live tiles and a simplistic menu – like the one expected to debut with Windows 10X. The Start Menu, Action Center, and context menus on the taskbar – such as the Jump Lists might hover over the taskbar and could be “visually separated”. The OS is also said to bring some new animations for a more fluid experience.

      As for OS features, the company is reportedly planning to bring improvements to Settings in the way of a new battery usage chart – akin to what is present in mobile OSes – that provides granular power consumption information. Multitasking abilities are also said to be getting a few new features, with Snap Assist gaining the ability to let users snap two Edge tabs side-by-side and improvements to scaling when moving across different displays. There also could be a new “dashboard” feature in the Task View area that displays users’ account summary and calendar information.

      Windows 10 Sun Valley Snap Assist mockup | Image credit: Windows Central Other enhancements reportedly in the works include improvements to voice and pen input capabilities, a new “gesture layer” aimed at making touch-based navigation easier by introducing trackpad-like gestures to navigate through the OS, and the ability to allow users to uninstall many in-box apps – a feature aimed at “power users”.

      Microsoft is expected to start testing Sun Valley bits with Windows Insiders in the next few weeks. The firm is reportedly planning to sign off the final build sometime in June, with a public release expected to happen in October. It will be interesting to see how this update shapes up. As with all rumors and internal reports, plans could change at any time and the company could decide to delay any of the reported features if they are not ready in time.

      Source: Windows Central

    • By Abhay V
      Microsoft releases Edge Dev 89.0.760.0 with Password Monitor for Mac users
      by Abhay Venkatesh



      Microsoft has released the second Edge Dev build for this year, bringing version 89.0.760.0 to users in the Dev channel. Today’s build adds a few new features, chief of which is the Password Monitor feature for macOS users. While the feature has been available to Insiders on Windows for a while now, it is being enabled for Mac users with this build. As a reminder, the firm added support for Apple Silicon Macs with last week’s build.

      In addition to the password monitor, there are a few other minor additions relating to management and update policies. Here is the complete list of features added with today’s release:

      As usual, the update also brings with it a bunch of reliability improvements. Here is the complete list of fixes:

      And here are all the fixes for changed behavior:

      Lastly, there are a bunch of known issues with the update, some of which are being tracked for a past few releases. Here are all the known issues:

      The browser should automatically be updated in the background for Dev users. However, you can also force-check for an update via Settings > About Microsoft Edge and pull the update manually.