Forums online, news to follow


Recommended Posts

Happy with the new Host ?

Think I saw Neobond say the old host where charging Neowin for extra bandwidth used.

No, I'm personally not. This is on a Cogent powered network. You will notice slower network transfer speeds and higher latency because it's a cheaper provider. The frigging connection between Dallas and Chicago was only 180Kb/s! What the hell is that?

On the upside, there's a bit better hardware available to us now and the codebase is up to the latest version, which has some things that should stop a lot of the freezing that was happening in MySQL before.

Also, I fixed the sync between the two webserver filesystems. I think we'll have to add another webserver soon and then start thinking about MySQL clustering (which gets interesting, to say the least...). These new servers are nice, but there's always room for Jello!

Actually, I'm curious to see how much slower the connection is for everyone. Can you ping these two addresses and post the results? 63.28.242.201 and 67.19.42.49

Should look like this:

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=25ms TTL=242
Reply from 67.19.42.49: bytes=32 time=24ms TTL=242
Reply from 67.19.42.49: bytes=32 time=24ms TTL=242
Reply from 67.19.42.49: bytes=32 time=23ms TTL=242

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 23ms, Maximum = 25ms, Average = 24ms

inging 66.28.242.201 with 32 bytes of data:

eply from 66.28.242.201: bytes=32 time=56ms TTL=109
eply from 66.28.242.201: bytes=32 time=58ms TTL=109
eply from 66.28.242.201: bytes=32 time=57ms TTL=109
eply from 66.28.242.201: bytes=32 time=57ms TTL=109

ing statistics for 66.28.242.201:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
pproximate round trip times in milli-seconds:
   Minimum = 56ms, Maximum = 58ms, Average = 57ms

Hmm.. :/

ping 63.28.242.201

Pinging 63.28.242.201 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 63.28.242.201:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 67.19.41.49

Pinging 67.19.41.49 with 32 bytes of data:

Reply from 67.19.41.49: bytes=32 time=166ms TTL=241

Reply from 67.19.41.49: bytes=32 time=171ms TTL=241

Reply from 67.19.41.49: bytes=32 time=281ms TTL=241

Reply from 67.19.41.49: bytes=32 time=187ms TTL=241

Ping statistics for 67.19.41.49:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 166ms, Maximum = 281ms, Average = 201ms

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=326ms TTL=115

Reply from 66.28.242.201: bytes=32 time=324ms TTL=115

Reply from 66.28.242.201: bytes=32 time=323ms TTL=115

Reply from 66.28.242.201: bytes=32 time=327ms TTL=115

Ping statistics for 66.28.242.201:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss

Approximate round trip times in milli-seconds:

Minimum = 323ms, Maximum = 327ms, Average = 325ms

Reply from 67.19.42.49: bytes=32 time=343ms TTL=239

Reply from 67.19.42.49: bytes=32 time=393ms TTL=239

Reply from 67.19.42.49: bytes=32 time=342ms TTL=239

Reply from 67.19.42.49: bytes=32 time=362ms TTL=239

Ping statistics for 67.19.42.49:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 342ms, Maximum = 393ms, Average = 360ms

No, I'm personally not. This is on a Cogent powered network. You will notice slower network transfer speeds and higher latency because it's a cheaper provider. The frigging connection between Dallas and Chicago was only 180Kb/s! What the hell is that?

On the upside, there's a bit better hardware available to us now and the codebase is up to the latest version, which has some things that should stop a lot of the freezing that was happening in MySQL before.

Also, I fixed the sync between the two webserver filesystems. I think we'll have to add another webserver soon and then start thinking about MySQL clustering (which gets interesting, to say the least...). These new servers are nice, but there's always room for Jello!

Actually, I'm curious to see how much slower the connection is for everyone. Can you ping these two addresses and post the results? 63.28.242.201 and 67.19.42.49

Should look like this:

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=25ms TTL=242
Reply from 67.19.42.49: bytes=32 time=24ms TTL=242
Reply from 67.19.42.49: bytes=32 time=24ms TTL=242
Reply from 67.19.42.49: bytes=32 time=23ms TTL=242

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 23ms, Maximum = 25ms, Average = 24ms

inging 66.28.242.201 with 32 bytes of data:

eply from 66.28.242.201: bytes=32 time=56ms TTL=109
eply from 66.28.242.201: bytes=32 time=58ms TTL=109
eply from 66.28.242.201: bytes=32 time=57ms TTL=109
eply from 66.28.242.201: bytes=32 time=57ms TTL=109

ing statistics for 66.28.242.201:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
pproximate round trip times in milli-seconds:
   Minimum = 56ms, Maximum = 58ms, Average = 57ms

Did you mean 66.28.242.201 and not 63.28.242.201, because I get Request Timed Out on 63.28.242.201, and I noticed you used 66.28.242.201 in your ping results. :p

Anyway, here are my results.

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=57ms TTL=238
Reply from 66.28.242.201: bytes=32 time=97ms TTL=238
Reply from 66.28.242.201: bytes=32 time=156ms TTL=238
Reply from 66.28.242.201: bytes=32 time=45ms TTL=238

Ping statistics for 66.28.242.201:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 45ms, Maximum = 156ms, Average = 88ms

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=46ms TTL=238
Reply from 67.19.42.49: bytes=32 time=135ms TTL=238
Reply from 67.19.42.49: bytes=32 time=46ms TTL=238
Reply from 67.19.42.49: bytes=32 time=46ms TTL=238

Ping statistics for 67.19.42.49:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 46ms, Maximum = 135ms, Average = 68ms

Heh. I woke up to find Neowin still on my computer screen. (it was a thread I left open. lol. I closed it and re-open it to get fresh tthreads or news but got told the servers were down. lol.

btw I am now known as ozgeek, not mr.roberts. (ozgeek stands for Australian geek).

and timdorr how do I ping for you? is it ping via cmd?

Hmmm... I can go to neowin.net/forum, yet all the links inside point to neowin5.net/forum/whatever... Kind of strange... Is this still a result of the DNS servers or what?

Hey I just noticed that now I know how many stars I have to go to reach the end :D Just 3 left...

Mine ...

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=179ms TTL=239

Reply from 67.19.42.49: bytes=32 time=180ms TTL=239

Reply from 67.19.42.49: bytes=32 time=189ms TTL=239

Reply from 67.19.42.49: bytes=32 time=179ms TTL=239

Ping statistics for 67.19.42.49:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 179ms, Maximum = 189ms, Average = 181ms

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=167ms TTL=112

Reply from 66.28.242.201: bytes=32 time=167ms TTL=112

Reply from 66.28.242.201: bytes=32 time=165ms TTL=112

Reply from 66.28.242.201: bytes=32 time=167ms TTL=112

Ping statistics for 66.28.242.201:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 165ms, Maximum = 167ms, Average = 166ms

Reply from 67.19.42.49: bytes=32 time=131ms TTL=236
Reply from 67.19.42.49: bytes=32 time=123ms TTL=236
Reply from 67.19.42.49: bytes=32 time=123ms TTL=237
Reply from 67.19.42.49: bytes=32 time=126ms TTL=237

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 123ms, Maximum = 131ms, Average = 125ms


Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=120ms TTL=113
Reply from 66.28.242.201: bytes=32 time=120ms TTL=113
Reply from 66.28.242.201: bytes=32 time=121ms TTL=113
Reply from 66.28.242.201: bytes=32 time=122ms TTL=113

Ping statistics for 66.28.242.201:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 120ms, Maximum = 122ms, Average = 120ms

Last login: Tue Nov 29 20:55:27 on ttyp1

Welcome to Darwin!

nicholas-pachecos-mac-mini:~ Nicholas$ ping 67.19.42.49

PING 67.19.42.49 (67.19.42.49): 56 data bytes

64 bytes from 67.19.42.49: icmp_seq=0 ttl=241 time=49.703 ms

64 bytes from 67.19.42.49: icmp_seq=1 ttl=241 time=59.904 ms

64 bytes from 67.19.42.49: icmp_seq=2 ttl=241 time=84.557 ms

64 bytes from 67.19.42.49: icmp_seq=3 ttl=241 time=47.258 ms

64 bytes from 67.19.42.49: icmp_seq=4 ttl=241 time=48.742 ms

64 bytes from 67.19.42.49: icmp_seq=5 ttl=241 time=52.378 ms

^C

--- 67.19.42.49 ping statistics ---

6 packets transmitted, 6 packets received, 0% packet loss

round-trip min/avg/max/stddev = 47.258/57.090/84.557/12.945 ms

nicholas-pachecos-mac-mini:~ Nicholas$

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=102ms TTL=243
Reply from 67.19.42.49: bytes=32 time=100ms TTL=243
Reply from 67.19.42.49: bytes=32 time=96ms TTL=243
Reply from 67.19.42.49: bytes=32 time=100ms TTL=243

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 96ms, Maximum = 102ms, Average = 99ms 

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=115ms TTL=105
Reply from 66.28.242.201: bytes=32 time=130ms TTL=105
Reply from 66.28.242.201: bytes=32 time=114ms TTL=105
Reply from 66.28.242.201: bytes=32 time=114ms TTL=105

Ping statistics for 66.28.242.201:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 114ms, Maximum = 130ms, Average = 118ms

No, I'm personally not. This is on a Cogent powered network. You will notice slower network transfer speeds and higher latency because it's a cheaper provider. The frigging connection between Dallas and Chicago was only 180Kb/s! What the hell is that?

On the upside, there's a bit better hardware available to us now and the codebase is up to the latest version, which has some things that should stop a lot of the freezing that was happening in MySQL before.

Also, I fixed the sync between the two webserver filesystems. I think we'll have to add another webserver soon and then start thinking about MySQL clustering (which gets interesting, to say the least...). These new servers are nice, but there's always room for Jello!

Actually, I'm curious to see how much slower the connection is for everyone. Can you ping these two addresses and post the results? 63.28.242.201 and 67.19.42.49

Timdorr, Other than ping time the thing interests me is the number of hops inside the network look at the number of hops once I get inside the cogentco network.

traceroute to neowin.net (66.28.242.203), 30 hops max, 40 byte packets
 1  vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177)  0.335 ms  0.202 ms  0.258 ms
 2  10GigabitEthernet9-0.win-core1.Melbourne.telstra.net (203.50.79.129)  0.357 ms  0.389 ms  0.259 ms
 3  Pos-Channel2.ken-core4.Sydney.telstra.net (203.50.6.21)  12.936 ms  12.972 ms  12.984 ms
 4  10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86)  32.545 ms  12.983 ms  12.982 ms
 5  10GigabitEthernet2-2.syd-core02.Sydney.net.reach.com (203.50.13.42)  13.234 ms  13.208 ms  13.17 ms
 6  i-0-0.wil-core02.net.reach.com (202.84.144.101)  161.363 ms  161.335 ms  161.353 ms
 7  unknown.net.reach.com (202.84.251.166)  160.962 ms  160.91 ms  160.872 ms
 8  unassign.net.reach.com (134.159.63.66)  160.952 ms  160.934 ms  160.844 ms
 9  p6-0.core01.lax01.atlas.cogentco.com (154.54.2.209)  162.04 ms  162.152 ms  162.201 ms
10  p5-0.core01.san01.atlas.cogentco.com (66.28.4.78)  163.916 ms  163.649 ms  163.72 ms
11  p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5)  195.383 ms  195.381 ms  195.81 ms
12  p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106)  223.775 ms  223.66 ms  223.736 ms
13  p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34)  234.876 ms  235.536 ms  234.794 ms
14  p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154)  234.369 ms  234.337 ms  234.413 ms
15  p2-0.core01.ord04.atlas.cogentco.com (154.54.3.42)  235.05 ms  234.902 ms  234.985 ms
16  g3-1.hc01.ord04.atlas.cogentco.com (204.6.150.30)  234.651 ms  234.532 ms  234.636 ms
17  StardockCorporation.demarc.cogentco.com (38.112.15.250)  234.951 ms  234.965 ms  235.292 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Here's my ping times:

Reply from 67.19.42.49: bytes=32 time=42ms TTL=244

Reply from 67.19.42.49: bytes=32 time=42ms TTL=244

Reply from 67.19.42.49: bytes=32 time=42ms TTL=244

Reply from 67.19.42.49: bytes=32 time=42ms TTL=244

Ping statistics for 67.19.42.49:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 42ms, Maximum = 42ms, Average = 42ms

and

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=69ms TTL=114

Reply from 66.28.242.201: bytes=32 time=158ms TTL=114

Reply from 66.28.242.201: bytes=32 time=144ms TTL=114

Reply from 66.28.242.201: bytes=32 time=70ms TTL=114

Ping statistics for 66.28.242.201:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 69ms, Maximum = 158ms, Average = 110ms

That second server's not as fast to respond...

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=115ms TTL=233

Reply from 67.19.42.49: bytes=32 time=129ms TTL=233

Reply from 67.19.42.49: bytes=32 time=127ms TTL=233

Reply from 67.19.42.49: bytes=32 time=116ms TTL=232

Ping statistics for 67.19.42.49:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 115ms, Maximum = 129ms, Average = 121ms

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=123ms TTL=107

Reply from 66.28.242.201: bytes=32 time=123ms TTL=107

Reply from 66.28.242.201: bytes=32 time=124ms TTL=107

Reply from 66.28.242.201: bytes=32 time=123ms TTL=107

Ping statistics for 66.28.242.201:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 123ms, Maximum = 124ms, Average = 123ms

Pretty adverage ping times for me.

Keep up all the good work <3

Whoops, yep, I meant 66.28.242.201. Sorry about that. Just curious, though. No biggie :)

and for that IP still a lot of hops insde that network

traceroute to 66.28.242.201 (66.28.242.201), 30 hops max, 40 byte packets
 1  vlan250.lon-service6.Melbourne.telstra.net (203.50.2.177)  0.339 ms  0.358 ms  0.24 ms
 2  10GigabitEthernet9-0.win-core1.Melbourne.telstra.net (203.50.79.129)  0.341 ms  0.281 ms  0.389 ms
 3  Pos-Channel2.ken-core4.Sydney.telstra.net (203.50.6.21)  13.067 ms  12.866 ms  12.965 ms
 4  10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86)  12.923 ms  13.025 ms  12.967 ms
 5  10GigabitEthernet2-2.syd-core02.Sydney.net.reach.com (203.50.13.42)  13.213 ms  13.205 ms  13.21 ms
 6  i-0-0.wil-core02.net.reach.com (202.84.144.101)  161.414 ms  161.362 ms  161.34 ms
 7  unknown.net.reach.com (202.84.251.166)  246.252 ms  160.911 ms  160.839 ms
 8  unassign.net.reach.com (134.159.63.66)  160.858 ms  160.93 ms  160.977 ms
 9  p15-0.core01.lax01.atlas.cogentco.com (154.54.2.213)  161.429 ms  161.372 ms  161.707 ms
10  p5-0.core01.san01.atlas.cogentco.com (66.28.4.78)  163.94 ms  163.584 ms  163.764 ms
11  p6-0.core01.iah01.atlas.cogentco.com (66.28.4.5)  195.505 ms  196.641 ms  195.494 ms
12  p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106)  223.754 ms  223.725 ms  223.642 ms
13  p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34)  235.219 ms  234.752 ms  234.889 ms
14  p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154)  234.494 ms  234.479 ms  234.522 ms
15  p2-0.core01.ord04.atlas.cogentco.com (154.54.3.42)  235.082 ms  235.106 ms  234.924 ms
16  g3-2.hc01.ord04.atlas.cogentco.com (204.6.150.34)  235.012 ms  235.066 ms  235.036 ms
17  StardockCorporation.demarc.cogentco.com (38.112.15.250)  234.916 ms  234.771 ms  234.756 ms
18  66.28.242.201 (66.28.242.201)  234.784 ms  236.982 ms  234.748 ms

From the UK...

Pinging 66.28.242.201 with 32 bytes of data:

Reply from 66.28.242.201: bytes=32 time=114ms TTL=114
Reply from 66.28.242.201: bytes=32 time=115ms TTL=114
Reply from 66.28.242.201: bytes=32 time=116ms TTL=114
Reply from 66.28.242.201: bytes=32 time=115ms TTL=114

Ping statistics for 66.28.242.201:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 114ms, Maximum = 116ms, Average = 115ms

Pinging 67.19.42.49 with 32 bytes of data:

Reply from 67.19.42.49: bytes=32 time=164ms TTL=245
Reply from 67.19.42.49: bytes=32 time=163ms TTL=245
Reply from 67.19.42.49: bytes=32 time=161ms TTL=245
Reply from 67.19.42.49: bytes=32 time=162ms TTL=245

Ping statistics for 67.19.42.49:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 161ms, Maximum = 164ms, Average = 162ms

Edit: ooooo, quick edit is niiiiice

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You might be right... Look at his name, hiding in plain sight: hAmId.
    • ExplorerPatcher 26100.8457.70.3 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.3 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Update for Windows Insider Users If you're running Windows 11 Beta build 26220.8474 or Experimental build 26300.8493, updating ExplorerPatcher is highly recommended. Microsoft has removed parts of the old Windows 10 Start menu from these builds, which caused ExplorerPatcher's Windows 10-style taskbar and Start menu to crash. This update fixes those issues and ensures Explorer starts correctly after future Windows updates. Because the required components are no longer included in Windows, the Windows 10 Start menu option has been disabled on these builds and future builds that lack the necessary files. A temporary workaround is to replace StartTileData.dll with a version from build 26xxx.8457, but this solution may stop working in future releases. The good news: development on the Windows 10 Start menu isn't over yet. More updates are planned. Highlights Fixed crashes affecting the Windows 10 battery flyout on Windows builds 25951 and newer. As part of that fix, network flyout buttons now behave like they did before Windows 11 version 24H2. Changes to the Primary taskbar location on screen setting now apply instantly without requiring a restart. ExplorerPatcher no longer modifies Windows 11 taskbar auto-hide settings when Explorer starts. The Open Start in All apps by default option is now hidden when the new Windows 11 Start menu is enabled. Fixed Windows 10 Start menu crashes on very early Windows 11 builds (21996–22000.51). Fixed a crash in Registry Editor when switching to thumbnail view during registry import/export operations. Improved compatibility with recent Windows builds, especially ARM64 and upcoming 26H1 releases. Improved overall ARM64 performance. Added Greek language translations. Thanks to @KonVetsos! ep_taskbar Improvements ep_taskbar now supports all 43 Windows 11 display languages. Fixed several issues in the system tray and other taskbar components. For mod developers: DLL naming has been simplified and made easier to understand. For mod developers: internal TrayUI changes provide better stability across Windows builds that use different taskbar implementations. Windows 10 Start Menu Improvements To help preserve compatibility, ExplorerPatcher now includes a newly recreated version of the tile layout engine that Microsoft removed in build 26xxx.8474. Current limitations: Tiles may occasionally overlap when pinned in certain ways. Restarting StartMenuExperienceHost.exe or Explorer usually corrects the layout. Further improvements are planned. Additional Fixes Added a blacklist that prevents ExplorerPatcher's shell extension from loading inside specific applications where it may cause problems. Updated Windows 10 Start menu animation support for newer ARM64 Insider builds. Fixed a rare taskbar initialization deadlock that could occur during startup. Start10 Updates Addressed a new compatibility issue caused by Microsoft's ongoing removal of tablet mode code in Windows 11 25H2 Experimental builds. Pinned tiles are no longer reset after repeated crashes. Various wording and interface text improvements throughout the application. Translation and UI Several interface strings have been cleaned up and clarified. Thanks to @sefinek for wording improvements. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.3 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This author may be AI..... we just...... don't know.... lol AI is taking over.....run for the hills!
    • Here's how to grab your share of Apple's $4 billion lawsuit payout (if you qualify) by David Uzondu Image via DepositPhotos.com A UK tribunal has approved a collective legal action letting a $4 billion (£3 billion) claim against Apple proceed to trial after consumer rights group Which? formally accused the company of violating competition laws. The tribunal recently set a full trial date for October 2028. Which? filed the lawsuit way back in November 2024, accusing Apple of trapping users in iCloud by restricting rivals from fully accessing iOS. Apple gives users only 5GB of free space, and once that limit vanishes, the system drives upgrades by repeatedly nudging users through notifications. The group claims Apple overcharged millions who bought plans ranging from 99p a month for 50GB to £54.99 a month for 12TB. If Which? wins the now-greenlit lawsuit, the court will force Apple to pay out damages to roughly 40 million UK consumers, with each person receiving around £77 for the pricing abuse. Apple has already put out a statement telling Reuters that the allegations are completely false and that consumers do have choices. "We work hard to make iCloud a great experience, but no customer is required to use it, and customers in the UK have plenty of alternatives to choose from," it told the outlet. The good thing is that if Which? wins, claiming your share requires almost no effort due to the automatic structure of the litigation. You are eligible if you used Apple's iCloud services between November 8, 2018, and June 8, 2026, and paid for upgraded storage during that time. The tribunal automatically enrolls everyone living in the UK on June 8, 2026. The system operates on an "opt-out" basis, meaning you do not have to register right now, and you will just verify your details to collect your cash. However, if you want to leave the claim, you must notify Which? by October 8, 2026. But if you lived outside the UK on June 8, 2026, you must manually register on the official Which? website before October 8, 2026, to opt into the action. If you ignore this deadline, you will lose your chance to grab a share of the settlement. On a related note, Google recently had to resolve a massive data privacy fight by agreeing to a payout of over $170 million to Android users. In that lawsuit, plaintiffs argued that Google programmed the Android system to transmit user data without permission, wasting cellular data. To settle, Google agreed to pay a $135 million nationwide settlement alongside an extra $35 million in California. Eligible Android users must submit online claims to secure their cash, with the final approval hearing literally taking place today (June 23, 2026).
    • Microsoft outs Windows 11 KB5095093 with long list of new features by Sayan Sen Microsoft today has released its newest preview update (C-release) for the month of June 2026 under KB5095093, builds 26200.8737 (for Windows 11 25H2) and 26100.8737 (on Windows 11 24H2). The update brings new features across various elements of the OS including the Windows update, the Recovery, Widgets, File Explorer, and more. The full changelog is given below: First up we have the features rolling out gradually: [Point-in-time restore for Windows] New! This flexible recovery feature helps you quickly roll back your PC, including apps, settings, and personal files, to a recent automatic restore point. It helps reduce downtime and simplifies troubleshooting when issues occur. To learn more, see Point-in-time restore for Windows. [Windows Update] New! A calendar experience in Windows Update Settings (Settings > Windows Update) lets you pause updates by choosing an end date, for up to 35 days. You can extend the pause by selecting a different end date and re‑pause updates as needed. For more information, see Pause updates in Windows. [Widgets] New! A quieter, more focused Widgets experience helps reduce interruptions and improves default settings and notification controls: Reduce distractions: Widgets no longer open on hover. Notifications and taskbar badges are minimized by default. Simpler: Open to the Widgets dashboard by default on first use. Customize: Configure Widgets how you want by selecting Settings in the navigation bar, then changing any of the default settings. Stay informed: Dashboard icons show the number of alerts, and badges clear automatically when you leave a dashboard. Adjusted defaults: Some default settings are preserved based on usage, while others adjust to reduce interruptions. Performance improvements: This update provides improved reliability, responsiveness, and visual quality across the Widget experience. [Accessibility] New! This update makes your screen easier to see and customizes your zoom experience: Screen tint: Apply a full-screen color overlay to help reduce eye strain and improve readability. Choose from preset tint options, adjust the intensity, or turn it on automatically. Find this feature in Settings > Accessibility. Magnifier: Enter a zoom percentage directly and change it in increments in the Magnifier window for more precise, flexible control. Magnifier settings menu: You can now also modify zoom increments directly from the magnifier bar instead of navigating to Windows Settings each time. [File Explorer] New! When you hover over a file in File Explorer Home, commands such as Open file location and Ask Copilot appear as quick actions. This experience is now supported for work and school accounts (Entra ID).1 Improves the speed and performance of File Explorer launch.2 Fixes an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run with administrative mode. The address bar now supports paths containing double backslashes and quotation marks (for example, C:\\Users\\user or "C:\Users\user"), improving compatibility with a wider range of inputs. The address bar suggestion dropdown is more reliable and now consistently closes after an item is selected. This update addresses an issue on File Explorer Home where OneDrive files could appear duplicated in the Favorites section. This update includes several refinements to the Rename experience: Addresses an issue where text was repeatedly selected when renaming items in folder views. Addresses an issue where case-only name changes were not immediately reflected in folder views for items stored locally or in the cloud. [Bluetooth] This update improves reliability and performance when connecting to and using Bluetooth devices: New! Windows now keeps the microphone mute state in sync between the audio mixer and the Hands-Free Profile (HFP) for a more consistent experience with Bluetooth headphones with mute buttons or indicators. Accessory compatibility workarounds: Improves compatibility with specific Bluetooth audio devices, helping AirPods appear faster in pairing mode and improving microphone reliability on Beats Studio Pro headphones. Bluetooth audio stability: Improves overall Windows stability with certain PC manufacturer drivers (error code 0x9F). Improves Bluetooth reliability for voice calls when using Classic Audio devices with the Hands-Free Profile (HFP). Reduces time for LE Audio accessories to start playing audio while using the microphone. Device management: Windows will no longer show a “Remove failed” message when attempting to remove Bluetooth devices if the Bluetooth radio is unavailable or has changed since pairing. Settings experience: Improves stability when using the Bluetooth & devices settings page for a smoother, more consistent experience. Connection reliability and responsiveness: Reduces the time it takes for classic Bluetooth audio devices to reconnect after Windows resumes from hibernation. Improves reliability when LE Audio accessories disconnect, such as when another device (for example, a phone) connects. Improves reliability of LE Audio streaming after a connection is lost and restored. [Bluetooth and Phone Link] This update improves audio routing for calls made through a connected phone: When an outgoing call is dialed from a paired phone, audio remains on the phone while ringing and transfers to the PC only when the call is answered from the PC. When Do Not Disturb is enabled on Windows, incoming call audio from a paired phone no longer rings on the PC. [Voice access and voice typing] New! You can now use voice access and voice typing in French, German, and Spanish. As you speak, your PC improves your text in real time. It corrects grammar, punctuation, and recognition errors, and helps improve clarity—even in the presence of background noise. This makes dictation smoother and reduces the need for manual edits.3 [Audio] This update improves the reliability of the inbox HD Audio driver. [Taskbar] This update improves the reliability of opening the Start menu when selecting the left edge of the taskbar when the icons in the taskbar are left-aligned. [Networking] This update includes networking improvements for virtualized environments. Confidential Virtual Machines (CVMs) now use SR-IOV hardware acceleration by default for improved network throughput, and a configuration issue in nested Hyper-V virtualization network setup has been corrected to ensure reliable VM network provisioning. This update improves the reliability of the Windows networking stack. It reduces bug checks (blue screen errors) related to Wi-Fi power and improves cellular (WWAN) connectivity, including support for IPv6 VPNs. Compatibility with third-party VPN software and SR-IOV configurations on server hardware is also improved. Network adapter settings and bindings are now preserved across OS upgrades. [Printing] New! New printer installations use Internet Printing Protocol (IPP) by default when supported, simplifying setup and improving reliability. For details about third-party driver deprecation, see End of Servicing Plan for Third-Party Printer Drivers on Windows. To control this behavior, use the toggle in Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print. For more information, see Introducing Windows Ready Print and modernized driver selection. For more information, see Introducing Windows Ready Print and Modernized Driver Selection. [Windows Subsystem for Linux (WSL)] The update improves usage of WSL in mirrored networking mode with VPNs. [Display and graphics] Improves the reliability of rendering content while scrolling for certain apps spanning across multiple monitors. Improves the reliability and persistence of applying color profiles. [Location services] This update changes how some location settings are displayed in Settings > Privacy & Security > Location to help with clarity. When location services are turned off, settings like Default location and Allow location override don't immediately apply, since location information is not given to apps or services. These settings will now be greyed out when location services are off to reduce confusion over when they take effect. [Search] This update improves the reliability of setting Search related group policies. [Input] New! You can now customize the size of the right-click zone in Settings > Bluetooth & devices > Touchpad. Choose from default, small, medium, or large to control how much of the bottom-right corner responds to a single-finger right-click. This setting is only available on touchpads with a pressable surface. If your device manufacturer provides customization through their own app, a Custom option will appear to reflect those settings. This update improves recognition of English characters when using Japanese handwriting. [General performance] Improves the time to shut down Background Intelligent Transfer Service (BITS) when you turn off your PC. [General Reliability] ​​​​This update improves the reliability of explorer.exe. It addresses issues on the login and lock screens related to third-party credential providers, reduces the probability of taskbar icons appearing as blank gray placeholders, and improves navigation to Home in File Explorer during OneDrive sync. It also improves explorer.exe reliability when switching between desktops, enhances app launch with shell extensions, and using acrylic blur effects in the Start menu, Settings, and the lock screen. [Apps] Resolves an issue where some installers and applications could show unexpected elevation (UAC) prompts after installing KB5089549. [Remote Desktop] This update refreshes the dialog design when you enable Remote Desktop in Settings > System > Remote Desktop. [Graphics Kernel] Improves memory-management policy that allows PCs with more than 32GB of installed memory to run larger local AI models. Up next we have the features under normal rollout: [Secure Boot] With this update, Windows quality updates include additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout. [Authentication] This update improves Netlogon secure channel connections between domain controllers, enabling successful connections from member servers to domain controllers set up before 2025. [Emoji Panel Update] The emoji panel (Windows key + period (.)) now uses GIPHY for GIF content following the deprecation of Google’s Tenor API. Starting June 30, 2026, install the latest Windows update to continue using GIFs in the Emoji panel. If you don’t update, you will see a "GIF service is not available" error in the panel. Installing the latest Windows update will restore access to GIFs. [Networking] This update improves how your device connects to shared network resources. Connections used by apps and system features, such as the NetUseAdd function, now work more reliably, including unauthenticated (null session) connections. [Recycle Bin (known issue)] Fixed: This update addresses an issue where the confirmation dialog might display an internal Recycle Bin file name instead of the original file name when permanently deleting a file. This issue might occur after installing the June 2026 security update (KB5094126). [Taskbar] This update improves notification badge display across your apps. Notification counts and badge visuals now update correctly, helping you stay up to date with new activity. You can choose to manually download the update from Microsoft's update catalog website at this link.
  • Recent Achievements

    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      +Edouard
      165
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Michael Scrip
      87
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!