features you disabled in Windows 7 and why?


Recommended Posts

Did you know that Windows Media Player runs just fine with just the executable (and no other files present) in the dir? Although the visualizer is part of another dll file - mpvis.dll - you should keep that if you want the cruddy anims when playing music. I also wouldn't remove the wmplayer.exe.mui, mui files are important as long as the file they are referring to exists.

:)

Do you even have the slightest idea how many applications depend on Internet Explorer? Winamp, for example, uses it, as well as countless other applications. Internet Explorer isn't just an application, it's also framework. It might not be such a big deal in Windows 7, but disabling it before sometimes (more times than not) resulted in severe issues with programs that contacted the internet, as well as Windows Explorer.

When I had used XP, I tried to completely remove it. The thing is Source games like CS:S use it for rendering the server page. With a total removal of Internet Explorer, it will ask you what to do with htm/html files - as there is no IE Core to render them. It will annoy you to no extent, it is better to just kill the browser but not the engine. Also Windows Explorer should work fine without IE and as far as I can tell it has nothing to do with networking abilities - internet will work fine, but all applications that use the IE render will suffer.

Did you know that Windows Media Player runs just fine with just the executable (and no other files present) in the dir? Although the visualizer is part of another dll file - mpvis.dll - you should keep that if you want the cruddy anims when playing music. I also wouldn't remove the wmplayer.exe.mui, mui files are important as long as the file they are referring to exists.

:)

No, I don't buy the statement that WMP runs just fine with only the exe present. You may think it does, but something in the functionality will stop working when you get rid of it, you just haven't found it yet. I tried it in my vBox 7 that I use as a sandbox, and I've completely lost the ability to stream music, the language pack is totally effed up (all box characters), and some icons are missing. So no, I wouldn't say "it runs just fine". Thankfully, I restored the files and it now functions perfectly again.

It's quite retarded that you call that "tweaking". What exactly are you trying to tweak? You're removing functionality, and you do realize that the entire WMP12 Program Files folder (also checked the appdata folder) is roughly 6 and a half megabytes. Congrats. You shaved off 6 megabytes from your precious, oh, what's the standard HD sizes nowadays? 250 GB at least? Yeah, awesome.

No offense, but you really do sound like you know what you're doing, but you and the rest of your "tweaking" crowd seem to be suffering from a placebo affect. You can cry "it's my software, I'll do with it what I want", but at the end of the day, Windows 7 has worked on every single computer I've tried it on, both old and new, laptop and desktop, and I have yet to encounter any problem that required "tweaking". I think the issue is that the nostalgia from all the so called "tweaking" and "optimizing" from XP has driven you guys to assume that each Windows OS needs to be totally modified otherwise it will perform poorly.

I'm waiting for the day where people realize that Windows 7 has got to be the most hassle-free OS to use out of all the Windows OSes, and that it doesn't require much disabling except UAC and search indexing, if you don't use those.

No, I don't buy the statement that WMP runs just fine with only the exe present. You may think it does, but something in the functionality will stop working when you get rid of it, you just haven't found it yet. I tried it in my vBox 7 that I use as a sandbox, and I've completely lost the ability to stream music, the language pack is totally effed up (all box characters), and some icons are missing. So no, I wouldn't say "it runs just fine". Thankfully, I restored the files and it now functions perfectly again.

It's quite retarded that you call that "tweaking". What exactly are you trying to tweak? You're removing functionality, and you do realize that the entire WMP12 Program Files folder (also checked the appdata folder) is roughly 6 and a half megabytes. Congrats. You shaved off 6 megabytes from your precious, oh, what's the standard HD sizes nowadays? 250 GB at least? Yeah, awesome.

No offense, but you really do sound like you know what you're doing, but you and the rest of your "tweaking" crowd seem to be suffering from a placebo affect. You can cry "it's my software, I'll do with it what I want", but at the end of the day, Windows 7 has worked on every single computer I've tried it on, both old and new, laptop and desktop, and I have yet to encounter any problem that required "tweaking". I think the issue is that the nostalgia from all the so called "tweaking" and "optimizing" from XP has driven you guys to assume that each Windows OS needs to be totally modified otherwise it will perform poorly.

I'm waiting for the day where people realize that Windows 7 has got to be the most hassle-free OS to use out of all the Windows OSes, and that it doesn't require much disabling except UAC and search indexing, if you don't use those.

Does it still play MP3s? Yes.

Does it still play MP4s? Yes.

Therefore, to me there is no functionality that is lost.

This is not tweaking, this is pure removal of unnecessary functionality. :)

Actually it does work. A normal Windows XP install boots in about half a min on a 2004 my emachines, while a nlited install boots in about half that time. I haven't yet tried a lited 7, but the results should be the same. The results of tweaking can actually be seen at boot by just booting the 12 or so (12 if you remove some dependencies, more like 15) services needed for basic functionality and internet VS. booting at all 50 or so.

Does it still play MP3s? Yes.

Does it still play MP4s? Yes.

Therefore, to me there is no functionality that is lost.

This is not tweaking, this is pure removal of unnecessary functionality. :)

No, unneeded function as defined by you. The rest of us who use WMP to manage our libraries and stream them to our Xboxes, we call that needed functionality. And no, it doesn't make a damn bit of difference whether or not you delete them. I've timed the startup times after removing it and it does nothing for speed. You can gladly say "it's my OS, I'll do it the way I want" but the point is that it's not assisting your machine in any way, and any improvement you may think you see from deleting said files is purely placebo.

Actually it does work. A normal Windows XP install boots in about half a min on a 2004 my emachines, while a nlited install boots in about half that time. I haven't yet tried a lited 7, but the results should be the same.

No idea where XP's boot time has anything to do with deleting the majority of a 6 MB folder's contents.

No idea where XP's boot time has anything to do with deleting the majority of a 6 MB folder's contents.

No, that was a comparison between the normal 2GB install of XP and an lite XP that can be installed on a 512MB Partition. :)

No, that was a comparison between the normal 2GB install of XP and an lite XP that can be installed on a 512MB Partition. :)

And why pray tell would you want to install XP on a 512 MB partition? Don't you realize that programs, by default, install to the C:/ (or whatever the install drive is) drive?

If you're still living with ancient hardware, that's not called tweaking and "optimizing", that's called being too cheap to get decent hardware (which is no longer expensive, if all you're trying to run is XP).

And why pray tell would you want to install XP on a 512 MB partition? Don't you realize that programs, by default, install to the C:/ (or whatever the install drive is) drive?

If you're still living with ancient hardware, that's not called tweaking and "optimizing", that's called being too cheap to get decent hardware (which is no longer expensive, if all you're trying to run is XP).

You missed the point.

You missed the point.

If you say so. meanwhile, I'll still have a fully functioning operating system that does everything Microsoft intended it to, and when I have support issues, I won't have to keep a list saying "this is what I disabled, I wonder if this will cause an issue". Oh, and my Windows 7 runs plenty fast. Defragment regularly, don't install crapware, and you won't ever have to reinstall.

Have fun.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

with hard drives being so cheap these days i don't really care about space....

You should. Fast Flash based, server grade and the Raptor harddrives from Western digital are expensive and relatively small. Bigger files also means longer time to load, and more fragmentation issues.

If you say so. meanwhile, I'll still have a fully functioning operating system that does everything Microsoft intended it to, and when I have support issues, I won't have to keep a list saying "this is what I disabled, I wonder if this will cause an issue". Oh, and my Windows 7 runs plenty fast. Defragment regularly, don't install crapware, and you won't ever have to reinstall.

I guess you are not very fast, on a general basis :p I find programs to launch much slower then on XP, and its strange that my Raptor WD1500 HD sounds much less busy in Vista and 7, than XP. Seems like Microsoft decided to insert a few millions NOOP instructions per HD I/O. NVIDIA Control panel takes several seconds to open vs. almost instantly on XP. Perfectdisk analyzing a HD is also much slower XP vs. vista and 7.

The user interface is also much more sluggish then XP. Each folder takes about half a second to open in Vista and 7, vs. instantly on XP.

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

Check out the link for more information on GDI+ and hardware acceleration.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

If you look at the three Quartz implementation diagrams in sequence, you can see how the video card portion of the diagram has slowly expanded over the course of four years to encompass more and more of the display layer. The reason is clear when you look at the bandwidth numbers: 30GB/s between the GPU and VRAM, and that number is climbing rapidly—much more rapidly than the bandwidth between the CPU and RAM.

http://arstechnica.com/apple/reviews/2005/...osx-10-4.ars/14

In programmer circles, Microsoft is the very model of modern bloated software. As a quick example, just check out your Windows Live Contacts database. Each contact gets a default 32MB database file.

I'm all for new features, but I think Windows Vista and 7 could run on much slower hardware if Microsoft wasn't such a bloat machine. It's not very environmentally friendly to produce computers (just check all the chemicals they use to make CPU's) and power efficiency is important in these days of possible human made climate change (the experts does't agree yet). You don't need a super CPU just for the web and there is no excuse not to hardware accelerate video playback.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

Well, let's define "tweaking", shall we? If you mean disabling services or uninstalling system files / folders because you want to reduce the footprint of the OS, then I agree completely. But tweaking can also mean modifying the interface so it better suits your comfort level, enabling or disabling items in the startup menu (ie, run, search, recent docs, etc), removing icon arrow overlays, disabling some visual effects, moving the pagefile to where you want it, and so on. I see absolutely nothing wrong with doing any of these things.That's all part of "making the OS your own".

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

GDI+ is never hardware accelerated on any version of Windows. GDI+ is a software library with various utility functions and classes that make dealing with graphics easier. It does everything in software, and calls GDI when it's time to actually show something on screen (so that part can be accelerated, but nothing else.) Pedantry maybe, but worth knowing. The performance penalty for using GDI+ instead of GDI can be extreme, especially on slower systems.

Check out the link for more information on GDI+ and hardware acceleration.

Firstly I'm going to say that 7 does perform worse than XP. That isn't in dispute. However, the example you're using to "prove" this is extremely flawed. You cannot use Explorer to make some point about a graphics API, and you can't use it to compare different versions of Windows.

Explorer in XP and 7 is not the same program. It has changed massively, even on the graphics side. In XP it uses standard windowing and common controls, whereas in 7 it is based on Microsoft's internal windowless GUI framework. This might introduce additional overhead compared with XP, overhead that is entirely in the software framework itself and not with any Windows API.

In addition, scrolling up and down in Explorer is not necessarily just a benchmark of the graphics side. All the data that is being drawn has to come from somewhere. Changes might have been made in the way Explorer handles the extensions that create thumbnails of your files, for instance. Maybe they now run out-of-process for reliability reasons, something that adds more overhead. Maybe the code that creates the thumbnails has changed as well. Maybe it takes more processing power to read and draw icons and images that have higher quality. Maybe changes have been made to the artificial delays in various parts of the user interface (Windows has lots of these), and so on. The list goes on.

If you just want to make a point about graphics performance, then you have to run synthetic benchmarks that just do graphics, under controlled conditions. There wouldn't be much point though, because everyone recognizes that it is so. It is a necessary step towards the future. Maybe GDI is slightly slower, but at the same time the experience you get while running several Direct3D programs at the same time is much more pleasant than it was with XP and D3D <= 9.

What it feels like in real world use is more important than synthetic benchmarks, and Explorer honestly doesn't feel slow to me, and in some ways it even performs better. I have a folder with close to 7000 images, for instance, and 7 seems to handle this much better. Same with the image viewer.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

Well, they had an easier job with OS X. Its APIs are fairly new, and they have little concern about breaking applications. Windows APIs like GDI and windowing (user), on the other hand, were designed in the 1980s and are very fragile, with thousands of applications relying on internal implementation details. The only real option I see is to create new frameworks that live side-by-side with the old. Microsoft has done that with Direct2D, but sadly there is no UI framework to go with it. The reason, in my opinion, is because Microsoft got so lost in their .NET vision.

there is no excuse not to hardware accelerate video playback.

What are you referring to here? Windows does have hardware acceleration of video. In fact, depending on the hardware you have, virtually the entire process can be handled by your graphics card's video decoder.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

another person who is up microsoft's arse. Microsoft will set the defaults that are most suited to the mainstream user, typically someone who isnt particurly savvy. However it is never ever possible to have a configuration that is optimal for 100% of userbase.

I have enabled superfetch on my machine again now and will concede that superfetch is significantly better than it was under vista, it still runs when the machine isnt idle but not very frequently so is fine. However I would leave it off if I didnt have much ram. Windows search is still turned off tho.

The worst thing a software developer can do is not allow their software to be configurable, eg. microsoft have alienated some people by dumbing down windows 7 gui, its less configurable than previous versions of windows. A developer may have a vision of how a product such work but its a garuantuee not everyone will agree with him, and if he tries to force the issue by not allowing tweaks etc. then he will restrict takeup of software.

I like windows 7 but I feel sick when I read things such as "its perfect" "it does nothing wrong" "no need to change anything" "if it doesnt work then it must be a end user problem".

NVIDIA Control panel takes several seconds to open vs. almost instantly on XP.

I have the same problem, it is a mystery, here is what I have discovered.

1 - The 182.50 wddm 1.0 nvidia driver the panel loads signifcantly faster than newer driver versions, but still way slower than XP, in XP I was using a way older driver, so could be driver related.

2 - The nvidia panel opens alot faster on my amd box than on my intel, the weird thing about this is that on paper my amd spec is weaker.

3 - on XP I know the configuration of IE affected how fast the nvidia panel opened, eg. when I used spybot to fill up the restricted site zone with rogue sites it made nvidia panel open very slowly. So it is possible some part of IE has affected how fast the panel opens in windows 7.

I too don't like the way the GUI functions. What is the logic in not offloading scrolling to the GPU? (Windows Explorer)

For those who completely want to get rid of Internet Explorer in C:\Program Files\Internet Explorer ,

---> Do not remove ieproxy.dll

---> It is responsible for opening folders in the same window.

---> The rest doesn't seem used, so the rest can go

:)

I too don't like the way the GUI functions. What is the logic in not offloading scrolling to the GPU? (Windows Explorer)

For those who completely want to get rid of Internet Explorer in C:\Program Files\Internet Explorer ,

---> Do not remove ieproxy.dll

---> It is responsible for opening folders in the same window.

---> The rest doesn't seem used, so the rest can go

:)

WHY in the world would you even do something like this?

I guess you are not very fast, on a general basis :p I find programs to launch much slower then on XP, and its strange that my Raptor WD1500 HD sounds much less busy in Vista and 7, than XP. Seems like Microsoft decided to insert a few millions NOOP instructions per HD I/O. NVIDIA Control panel takes several seconds to open vs. almost instantly on XP. Perfectdisk analyzing a HD is also much slower XP vs. vista and 7.

The user interface is also much more sluggish then XP. Each folder takes about half a second to open in Vista and 7, vs. instantly on XP.

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

Check out the link for more information on GDI+ and hardware acceleration.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

If you look at the three Quartz implementation diagrams in sequence, you can see how the video card portion of the diagram has slowly expanded over the course of four years to encompass more and more of the display layer. The reason is clear when you look at the bandwidth numbers: 30GB/s between the GPU and VRAM, and that number is climbing rapidly?much more rapidly than the bandwidth between the CPU and RAM.

http://arstechnica.com/apple/reviews/2005/...osx-10-4.ars/14

In programmer circles, Microsoft is the very model of modern bloated software. As a quick example, just check out your Windows Live Contacts database. Each contact gets a default 32MB database file.

I'm all for new features, but I think Windows Vista and 7 could run on much slower hardware if Microsoft wasn't such a bloat machine. It's not very environmentally friendly to produce computers (just check all the chemicals they use to make CPU's) and power efficiency is important in these days of possible human made climate change (the experts does't agree yet). You don't need a super CPU just for the web and there is no excuse not to hardware accelerate video playback.

You really don't know the original meaning of software bloat, do you?

Well offloading as much as possible from the CPU seems logical. Especially when it comes to drawing 2D stuff.

It may seem logical, but it is extremely difficult to completely rewrite the implementation of an API designed in the 1980s (and designed around old hardware) to work on a completely different architecture. Even if you managed to do it and emulate the publicly defined API perfectly, you would most likely still end up with thousands of programs that would cease to function because they dependend on some internal implementation detail or quirk that you have now changed.

Chances are it is never going to be done, and that we will instead see a new UI framework that exists side-by-side with the legacy APIs (GDI/User) that new applications will be written to use.

It may seem logical, but it is extremely difficult to completely rewrite the implementation of an API designed in the 1980s (and designed around old hardware) to work on a completely different architecture. Even if you managed to do it and emulate the publicly defined API perfectly, you would most likely still end up with thousands of programs that would cease to function because they dependend on some internal implementation detail or quirk that you have now changed.

Chances are it is never going to be done, and that we will instead see a new UI framework that exists side-by-side with the legacy APIs (GDI/User) that new applications will be written to use.

:(

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

    • No registered users viewing this page.
  • Posts

    • The Light of Life? We actually do glow till our Death, study finds by Sayan Sen Image by Rafael Rendon via Pexels A study by researchers at the University of Calgary has found that living organisms produce an extremely faint light known as ultraweak photon emission, and that this glow appears to drop significantly after death. The research was published in the Journal of Physical Chemistry in April 2025 and quickly drew widespread attention, leading to more than 200 news stories about the findings. Ultraweak photon emission (or UPE), sometimes called biophoton emission, refers to tiny amounts of light released by living cells as a result of normal biological activity. A photon is the basic particle of light, and researchers say every living system examined so far, including plants and animals, has been found to emit these photons. The glow is far too faint to be seen by the human eye. “I suppose it has a little to do with people being reminded of auras,” says Dr. Christoph Simon, PhD, one of the authors of the study and a professor in the Department of Physics and Astronomy in the Faculty of Science. “It is a fact that living beings glow. It’s a very weak glow, but it’s there and visible with very sensitive cameras.” According to the study, the light involved is extremely weak, ranging from 10 to 1,000 photons per square centimetre per second across a spectral range of 200 to 1,000 nanometres. For comparison, a nanometre is one-billionth of a metre and is commonly used to measure wavelengths of light. Detecting emissions at such low levels requires highly specialized equipment. To study the phenomenon, researchers used electron-multiplying charge-coupled device (EMCCD) and charge-coupled device (CCD) cameras. These imaging systems are designed to detect extremely small amounts of light, including individual photons, while minimizing background noise. The technology allowed researchers to capture signals that would otherwise be impossible to observe. The team worked with the Human Health Therapeutics Research Centre at the National Research Council of Canada (NRC) in Ottawa to examine photon emissions in mice. Researchers took two-hour exposure images of the animals before and after death and compared the results. “We saw that the level of light that they emit – this biophoton glow – is distinctly different between living and dead animals,” says Dr. Daniel Oblak, PhD, an associate professor in Physics and Astronomy and the corresponding author of the study. The images showed a clear decrease in photon emissions after death across the entire body of each mouse. According to the researchers, this provided direct evidence that living and dead tissue produce different levels of ultraweak photon emission. “It’s a very small amount and it’s, of course, very tricky to detect,” Oblak says. The study grew out of discussions between Simon, whose research interests include quantum biology, and Oblak, whose work focuses on detecting light for quantum communication experiments. Quantum biology is a field that explores whether processes described by quantum physics, which studies matter and energy at very small scales, may also play a role in living systems. “Since I work as a quantum physicist on light detection for quantum communication, I thought that experimentally we have a lot of the tools to be able to detect the light,” Oblak explains. The researchers also investigated UPE in plants and found that the light changed in response to stress. When plants were exposed to higher temperatures or physically injured, their photon emissions increased. Chemical treatments also affected the glow. Among the substances tested, the local anesthetic benzocaine produced the strongest emission response when applied to injured plant tissue. These findings suggest that ultraweak photon emission is closely linked to biochemical and metabolic activity inside living organisms. Metabolism refers to the chemical reactions that allow cells and organisms to stay alive and function. Because these reactions change when an organism experiences stress, injury or disease, researchers believe UPE may provide a way to monitor those changes. The researchers stress that the glow is a physical and biological phenomenon, not a metaphysical one. Oblak says more research is needed to understand exactly how the light is produced and what information it may reveal about the condition of living tissue. “We must understand what that is to figure out what’s happening,” he says. “If we can understand how that relates to certain influences on the body – stress, diseases – then that could be used as a diagnostic tool.” The researchers believe the technique could eventually help scientists study health and disease without invasive procedures. Because UPE can be measured without adding dyes, markers or labels, it may offer a way to monitor whether tissue is healthy, damaged or alive. In plants, it could help researchers better understand how organisms respond to injury, heat and other forms of stress. While the work is still in its early stages, the study demonstrates that ultraweak photon emission imaging can provide a non-invasive and label-free way to observe biological activity. Researchers say the approach could become a useful tool for studying vitality, stress responses and other important processes in both animals and plants. Source: University of Calgary, ACS publication This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Damn, I loved this show back in the day.  
    • Rufus 4.15.2393 Beta 2 by Razvan Serea Rufus is a small utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc. Despite its small size, Rufus provides everything you need! Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO (with honorable mention to WiNToBootic for managing to keep up). It is also marginally faster on the creation of Linux bootable USBs from ISOs. A non-exhaustive list of Rufus supported ISOs is available here. It can be especially useful for cases where: you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.) you need to work on a system that doesn't have an OS installed you need to flash a BIOS or other firmware from DOS you want to run a low-level utility Rufus 4.15.2393 Beta 2 changelog: Add RISC-V 64 support to UEFI:NTFS Improve the guards for using the "silent" option Improve the ability to cancel during write retries Improve progress reporting for compressed image extraction Fix unrestricted XML entity expansion and integer overflow in ezxml parser (courtesy of @esadowski4) [GHSA-55r2-34wg-8mv9] Fix "silent" Windows installation failing at 75% in most cases [#2960] Fix a crash during boot when using UEFI:NTFS on Snapdragon X based ARM64 platforms [#2934] Fix the first WUE option always being checked by default [#2965] Fix an infinite loop when using Windows ISOs that contain multiple WIMs Fix "Enable runtime UEFI media validation" checkbox not always being properly enabled Other WUE improvements/fixes for OneDrive removal and username validation (with thanks to @christian8641) [#2984, #2991] Download: Rufus 4.15 Beta 2 | 1.9 MB (Open Source) Links: Rufus Home Page | Project Page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Tixati 3.43 by Razvan Serea Tixati is a free and easy to use BitTorrent client featuring detailed views of all seed, peer, and file transfer properties. Also included are powerful bandwidth charting and throttling capabilities, and a full DHT implementation. Tixati is one of the most advanced and flexible BitTorrent clients available. And unlike many other clients, Tixati contains NO SPYWARE, NO ADS, and NO GIMMICKS. Tixati portable version is meant to run on a USB flash drive or other portable media. It stores all its configuration files in the same folder as the executable binary files, and all file paths are stored in a format relative to the program executable folder. It is important you do not delete the "tixati_portable_mode.txt" file within the executables folder. This file is what triggers Tixati to run in portable mode. (The executable binaries are actually the same as the standard edition binaries.) When running the portable edition from a USB flash drive, especially one that is formatted in FAT16/FAT32, you may experience some lag when initially loading a new transfer. This is because initializing and allocating large files on flash-based media consumes a greater amount of time and resources compared to a conventional hard-drive. Tixati has the following features: detailed views of all aspects of the swarm, including peers, pieces, files, and trackers support for magnet links, so no need to download .torrent files if a simple magnet-link is available super-efficient peer choking/unchoking algorithms ensure the fastest downloads peer connection encryption for added security full DHT (Distributed Hash Table) implementation for trackerless torrents, including detailed message traffic graphs and customizable event logging advanced bandwidth charting of overall traffic and per-transfer traffic, with separate classification of protocol and file bytes, and with separate classification of outbound traffic for trading and seeding highly flexible bandwidth throttling, including trading/seeding proportion adjustment and adjustable priority for individual transfers and peers bitfield graphs that show the completeness of all downloaded files, what pieces other peers have available, and the health of the overall swarm customizable event logging for each download, and individual event logs for all peers within the swarm expert local file management functions which allow you to move files to a different partition even while downloading is still in progress 100% compatible with the BitTorrent protocol Windows and Linux-GTK native versions available Tixati 3.43 changelog: Several major DHT improvements Added several screening heuristics to filter malicious DHT nodes, prevent Sybil floods Rewrote DHT search algorithms to add support for multi-path lookups Improved DHT logging, more details in several error messages Extended timeout lengths for outgoing queries over I2P Added incoming query / response per second to DHT table status display Updated Regex engine to PCRE2 Faster Search function, scans channel user profiles in much less time Fixed problems with file name parsing and date handling in RSS Faster and more accurate RSS filtering and episode number detection Several optimizations to global text processing functions, such as UTF-8 cleaning, line splitting, and token parsing Complete update of port-mapping UPNP/NAT-PMP engine, added PCP support, mapping over VPN support, and more Several refinements to default gateway detection on Windows / Android, which is used for port-mapping Support for IPv6 interface-scoped addresses, which is sometimes needed for IPv6 gateway detection and port mapping Full support for PCP port remapping, added backup zero-port query in case requested port is rejected New UPNP/NAT-PMP Monitor in Help > Diagnostics New reflected local port/location tracker that analyzes DHT replies to detect true port/location and NAT mapping type New TCP/UDP Ports monitor in Help > Diagnostics, with several statistic and information tabs, and a detailed event log Calculated/reflected local port is now used for port parameter in tracker queries and peer handshake Fixed several problems with Linux Wayland compatibility Completely replaced tray icon functions in Linux, new SNI implementation is now the default with GSI backup Implemented full DBus-Menu server to be used by new SNI tray icon implementation Replaced Linux tray balloon notification DBus client Rewrote auto-shutdown DBus interface for Linux Rewrote sleep inhibit DBus interface for Linux Dropped deprecated Linux dbus-glib dependencies Completely new Windows asynchronous file handling, now using IOCP model with several block-alignment optimizations Better handling of system network resets and interface down/up cycles Added option to fully clear configuration in Settings > Import/Export Remember last option checkboxes when using Import/Export Fixed minor I2P incoming connection routing problems Much faster I2P vanity host name finder Much faster channel user vanity key finder Raised length limit for torrent tracker remote failure messages to 120 from 64 Fixed problems setting download location on a torrent before the meta info is resolved Added location/MOC paths to category pane tooltips Several minor Web Interface fixes Refinements to static and scrolling ellipsizing layout routines Several fixes and improvements to single and multi-line text edit controls Many other minor fixes throughout the user interface A major overhaul of the Android framework has also been done: API target raised to 35, page alignment set to 16K Rewrote all inset processing routines Full rewrite of foreground service, application, and main activity objects New permission request routines Added multi-cast lock request before UPNP/LPDP discovery operations Fixed file permission and locking problems when loading .torrent from web browsers Fixed problems with Z-ordering of modal / non-modal and popup windows Fixed handling of back gesture on newer OS Added status bar icon adjustment based on status bar background color Added option in Settings > UI > Behavior to continue running in tray when task removed from recents App can be closed by swiping away notification Rewrote IME interface, fixed several problems with auto-correct, on-screen keyboard visibility, and cursor positioning Added full support for Android hardware mouse and keyboard function Added full tooltip implementation for Android hovering via mouse or other cursor device Full rewrite of popup menu widgets to better support hardware pointers and keyboard Added mouse cursor updating framework for Android hovering Added Settings > Import/Export to Android builds Added language file support to Android builds Download: Tixati 64-bit | Tixati 32-bit ~20.0 MB (Freeware) Download: Portable Tixati 3.43 | 114.0 MB Download: Tixati 3.43 for Linux | Android View: Tixati Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Firefox 152.0.1 by Razvan Serea Firefox is a fast, full-featured Web browser. It offers great security, privacy, and protection against viruses, spyware, malware, and it can also easily block pop-up windows. The key features that have made Firefox so popular are the simple and effective UI, browser speed and strong security capabilities. Firefox has complete features for browsing the Internet. It is very reliable and flexible due to its implemented security features, along with customization options. Firefox includes pop-up blocking, tab-browsing, integrated Google search, simplified privacy controls, a streamlined browser window that shows you more of the page than any other browser and a number of additional features that work with you to help you get the most out of your time online. Firefox key features Enhanced Tracking Protection (ETP) – Blocks trackers, cookies, cryptominers, and fingerprinters by default. Private Browsing Mode – Deletes history, cookies, and temporary files when closed. Lightweight & Fast Performance – Optimized memory usage with efficient page loading. Cross-Platform Sync – Sync bookmarks, passwords, history, and open tabs across devices. Customizable Interface – Toolbars, themes, and extensions can be tailored to user needs. Strong Privacy Controls – Options to manage cookies, permissions, and site data easily. Reader Mode – Strips away clutter for distraction-free reading. Pocket Integration – Save and read articles offline with Pocket built into Firefox. Picture-in-Picture (PiP) – Watch videos in a floating window while multitasking. Extensions & Add-ons – Vast library for productivity, security, and personalization. Built-in PDF Viewer – No need for external software to view PDFs. Firefox Monitor – Alerts users if their email is part of a known data breach. Multi-Account Containers – Isolate browsing sessions (e.g., work, personal, shopping). Performance & Resource Efficiency – Uses fewer system resources than some competitors. Open Source & Community-Driven – Transparent development with global contributions. Firefox 152.0.1 fixes: Fixed frequent crashes affecting users with Intel Raptor Lake processors. (Bug 2039575) Fixed an issue on macOS where choosing a PDF option, such as "Save as PDF", from the system print dialog would send the job to your printer instead of saving a file. (Bug 2047850) Download: Firefox 64-bit | Firefox 32-bit | ARM64 | ~70.0 MB (Freeware) Download: Firefox for MacOS | 146.0 MB View: Firefox Home Page | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      81
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      72
  • Tell a friend

    Love Neowin? Tell a friend!