Recommended Posts

No more restarting upon driver installation

Adding hard drives with permissions from previous installations to not have to have so many security precautions via password

The network "diagnosis" to actually diagnose rather than restart the network adapter. (You can do this yourself.)

Same as above, though, it'd just do it's job without saying what it's doing and just do it's job.

Disable BSOD's permanently

Have all codecs and drivers manually like linux

Continue previous sessions

I got some more, but can't think of them all now.

Post yours.

No more restarting upon driver installation

Adding hard drives with permissions from previous installations to not have to have so many security precautions via password

The network "diagnosis" to actually diagnose rather than restart the network adapter. (You can do this yourself.)

Same as above, though, it'd just do it's job without saying what it's doing and just do it's job.

Disable BSOD's permanently

Have all codecs and drivers manually like linux

Continue previous sessions

I got some more, but can't think of them all now.

Post yours.

99% of what you want is technically impossible or would be very unsecure. Also, BSODs help you. They end your session before stuff gets all corrupted. If you want "drivers and codecs like linux" then go use Linux. Drivers need to restart the computer. This isn't specific to Windows for a reason. Continue previous sessions would be a nice one, though, although hibernating works to the same effect, basically. Don't assign a password to your user account if you don't want to deal with the files from previous installs. Simple as that. Microsoft isn't going to remove their security just so YOU don't need to right click and choose "take ownership". Some people like security.

99% of what you want is technically impossible or would be very unsecure. Also, BSODs help you. They end your session before stuff gets all corrupted. If you want "drivers and codecs like linux" then go use Linux. Drivers need to restart the computer. This isn't specific to Windows for a reason. Continue previous sessions would be a nice one, though, although hibernating works to the same effect, basically. Don't assign a password to your user account if you don't want to deal with the files from previous installs. Simple as that. Microsoft isn't going to remove their security just so YOU don't need to right click and choose "take ownership". Some people like security.

Almost every other operating system does not need a restart for driver installation, why does Windows still need it after 7 versions?

Saying that all of that was technically impossible is technically incorrect, because this only really occurs on Windows. I'm definitely not a stationary Linux user at all, but I have dabbled with it, and driver installation was on the fly without restarting, I honestly don't see any reason why that's impossible or why it should be.

Hibernating is not 100% efficient, it sometimes puts other hardware to "sleep" and keeps them there temporarily till the next reboot.

I did not assign a password to my account on my previous account (Windows XP,) yet I couldn't access it till I changed the permissions, and if you search on the net, you'll see this is a very big problem in Vista and 7.

I don't see how you can get just your hard drive stolen and not your whole PC, which is what I was trying to say, but had to clarify it.

THOUGH, I think one of my hardwares is messed up, but I did memory test, everything was fine, it COULD be my graphics adapter, but I didn't see anything in my event log, but I tried 7 on my brand new notebook, got a BSOD, and I replaced it for a totally new one, same thing, replaced it, it was driver issues. Maybe I do have bad luck, but I've seen 3 BSOD's so far with 7.

@HeLGeN-X

Almost every other operating system does not need a restart for driver installation, why does Windows still need it after 7 versions?

Probably it depends of the driver. I remind restarting linux, after trying different driver, so what you are saying is not true.

It might not restart automatically, but you still have to restart to make the driver work properly.

I'm thinking especially of driver for graphic card.

Hibernating is not 100% efficient, it sometimes puts other hardware to "sleep" and keeps them there temporarily till the next reboot.

Weird. Wondering if you are not making a confusion with the default "sleep mode".

I did not assign a password to my account on my previous account (Windows XP,) yet I couldn't access it till I changed the permissions, and if you search on the net, you'll see this is a very big problem in Vista and 7.

Not clear.

Maybe I do have bad luck, but I've seen 3 BSOD's so far with 7.

Try with an other OS. If you get BSOD/ system crash, only with win7, that can be buggy drivers.

No more restarting upon driver installation

Those are extremely rare now, but when you have to, you have to. No big deal. Besides, dealing with drivers are incredibly rare anyway. More than likely you're only going to deal with drivers in the first hour you work with windows, then you're set, until you buy a new hardware, which then only takes 15 to half an hour of your time, depending on what it is.

Adding hard drives with permissions from previous installations to not have to have so many security precautions via password

I've yet had an issue with this myself, but then again, I don't deal with encrypted drives. With permissions, I'm pretty sure Windows 7 can try to adjust the permissions of the files from any previous installations. In fact, Windows 7 did a pretty good job fixing any permission issues I've had when I need to. Worst come to worst, you will have to find software that will "take own" of any files if needed, but since I started using windows 7, I've never had a problem with this to begin with.

The network "diagnosis" to actually diagnose rather than restart the network adapter. (You can do this yourself.)

If memory serves vista and 7 tends to do several issues with the network during the diagnosis. I think it's fine as it is.

Same as above, though, it'd just do it's job without saying what it's doing and just do it's job.

It's useful to me, to tell me what it is doing. It would help me to realize what's wrong, and fix it and prevent the issue in the future. I work with a router with 3rd party OS, Tomato. the way Network diagnosis has been useful to me when I needed to deal with the entire home network.

Disable BSOD's permanently

We hate them, but we could use them. It help us telling wtf is wrong, and what can be fixed. Most of the time they're here to protect the computer and files from any damage and just shut it down and tells us what went wrong. It's MUCH better than back in the 9x days when we'd get constant flashing classic blue screens. So, no thanks. I'd rather keep my BSODs.

Have all codecs and drivers manually like linux

Know what kind of codecs package out there and stick to it. I don't think any copies of windows would ever need it. Would it be nice to have, sure. But I can't ever see that happening anyway. I think that people that needs codecs are just considered as a minority in windows market share. This is not a necessity that any majority would need anyway.

Continue previous sessions

Isn't that what Hibernation does? In any case. I rarely use hibernation myself, with the exception of my laptop.

I have a few points and hope they get implemented at least in the next version (which will be a major release)

1)I wish Windows focused on reducing the number of silly and unnecessary reboots. I know that it has been considerably less compared to XP but may be they can focus on the issue a bit more.

2)A bit less cluttered and more organized Control Panel. The view by Small icons is lame presently

3)Remove all legacy crap since next version will surely be 64bit only and I'm sure XP Mode like feature would be even more improved

P.S: I have yet to see any BSOD since Vista. :huh:

No more restarting upon driver installation

Adding hard drives with permissions from previous installations to not have to have so many security precautions via password

The network "diagnosis" to actually diagnose rather than restart the network adapter. (You can do this yourself.)

Same as above, though, it'd just do it's job without saying what it's doing and just do it's job.

Disable BSOD's permanently

Have all codecs and drivers manually like linux

Continue previous sessions

I got some more, but can't think of them all now.

Post yours.

Get rid of the registry. No other operating system has this file.

I want an image reize option photos like you had with the image re-sizer power tool.

It's not quite the same, but Windows Live Photo Gallery has a resize option, so in a sense it supposed to be in Windows, what with WLPG being part of the, "Essentials" suite.

...Kinda sorta.

i wished i have more control while installing OS by selecting the apps i need during install only.

also if they would have changed a UI a bit more compared to vista

& about BSOD: i have yet to face it.

what i would like to see is:

64 bit only

drop compatability for older apps

include ability for portables apps to work without a rebuild

i know dropping support for older stuff wont be easy but 64 bit is easier

Bring back the sanity of the Control Panel for all its worth!

I totally agree with the Network Diagnostics stuff. If anyone has observed, if you network a Win7 system with WinXP, then using the 'repair' option on WInXP does nothing (in effect) and doing it on Win7 reportedly fixes "issues" on the Win7 desktop & does nothing (in effect). This is in case of an Ad-hoc network. (last time it happened, 'twas a DHCP issue, something way too obvious for Windows? to solve) So much for backward-compatibility!

For once, in a lifetime, to get the damn 'speaker fill' thing to actuallywork>!

Omkar

32 will eventually disappear. i dont see why it has to be done in win 7 right now. it doesnt support 16bits anymore so eventually 32 bit will be gone as well. in the mean time, a lot of people still have older hardware that doesnt have 64 bit drivers for it and the maker of those hardwares are too lazy to support them.

i havent used windows 7 yet. not much into beta or RC releases but what i would like to see is the ability for multiple desktop. i used to used Redhat at University and loved the idea of having 4 desktop and able to switch between them with a click. that's something i truly miss in windows. the ability to have a multiple copy and paste. i know it there in Office but i mean when try to copy files in windows explorer. i should be able to copy different sets all at once from folder and then paste each of those individually in different location. i would find something like this very useful when organizing photos into different folder as an example.

Hmm how about something more useful...

Better dual monitor support pl0x?

I would like to natively be able to have different/spanning wallpapers and a taskbar/Superbar that can extend over multiple displays. While Ultramon and DisplayFusion do this it's cumbersome having to have an extra app to do these menial tasks and currently they are incompatible with Aero Peek or the Superbar's icon docking anyway. Furthermore I would like the system tray/clock/Show Desktop button on the opposite corner as the Start Orb rather than in the same monitor and in the middle of the desktop :(

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

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!