Recommended Posts

Why? Another one will show up in a few days.... Something like I re-cabled all my network and nothing works.... We'll ask for IP address's and they'll all be 169.*.*.* and explain how DHCP works and how to connect something to a switch and blah blah blah.

Just let this one keep going then at least we won't have more random stuff.

Yeah, but some things are just too (insert your own comment) to let live. Sickens me, actually.

at least 2 people offered you support for nothing to look at it, and you choose to format vs allowing a second set of eyes to figure/fix the problem.

I even pointed you to a site to allow anyone that you feel comfortable with to remote in and look at it. ( http://www.showmypc.com )

wow, just wow.

Danny set up some sort of VPN and let the two people that offered help a look at what the hell is going on in your Enviroment. Some of the other comments arent necessary your right but some of them are, You have to understand peoples frustration.

sawyer no need for vpn with the link i provided, with that software the host connects to a ssh middleman and gets assigned a numeric password of 20 or so digits, the remote has to launch the app on their side connecting to the middleman server, via ssh, and type in the password that has been assigned to the host. once the session is in progress no one else can join the session, also once the session is done all you have to do is close out as there is no software that remains resident on either computer.

Edited by sc302
Actually you can assign file associations through the GUI...

I know that. You can reassign, but you can't unassign, AFAIK. I mean, what would you reassign .lnk files to? They're shortcut filetype...

Microsoft should prevent certain filetypes from easily being associated, or have a 'Remove association' button.

KJ, I don't know which version of windows you are talking about, but 2000 and xp both can. There is a utility called folder options, and within folder options there is a tab called file types. The file types are listed alphabetically (L is somewhere in the middle between A and Z), you click on the file type that you don't want associated to anything, then you click on the delete button (this doesn't work for all files like doc, as it will assume wordpad as the default doc reader)

I know what you're talking about, but I can't find it in Windows 7 :/. Maybe it's nested in another option or under another name, but I couldn't find it in the Folder Options nor File Property menu.

What Windows 7 has is a 'Set Associations' control panel:

noway.png

But imagine if someone accidentally associated .lnk to IE. I think I accidentally did this with a right click or slip of drag and drop with the Start Menu. I know I didn't conscientiously navigate through menu's to set file association type. I believe I was reinstalling apps and customizing things when it happened, so I was moving pretty swiftly.

Anyway, Windows allows you to reassign the association at that point -- meaning, they'll present to you a list of programs or let you choose one yourself (like above).

But what about .lnk files should have no associations? How would one do that through the GUI? Not possible, as far as I know.

I think Microsoft should lock or better prevent .lnk and other system files from being associated, or at have a 'Remove/Reset Association' in the 'Set Associations' CP button for accidents like these.

It's pretty annoying, and I hope this is the last time I'll bump into this problem (such an elementary mistake), but MS can make this easier for others.

It was stated earlier, but I'll repeat it for emphasis. You need to go into Control Panel --> Folder Options --> File Associations and remove the file association for .lnk. I repeat, .lnk should have no file association whatsoever. That will fix your problem and you won't have to worry about fudging the registry or any of that other stuff.

In Windows 7, you can find it under the Programs group in the Control Panel. It will say "Make a file type always open in a specific program", just click on that and find .lnk in the list.

It was stated earlier, but I'll repeat it for emphasis. You need to go into Control Panel --> Folder Options --> File Associations and remove the file association for .lnk. I repeat, .lnk should have no file association whatsoever. That will fix your problem and you won't have to worry about fudging the registry or any of that other stuff.

In Windows 7, you can find it under the Programs group in the Control Panel. It will say "Make a file type always open in a specific program", just click on that and find .lnk in the list.

In Windows 7, there is no button to remove the file association, only a menu to choose another program to associate with.

In Windows 7, there is no button to remove the file association, only a menu to choose another program to associate with.

You are correct, I hadn't actually tried to associate anything.

This program looks like it might help: http://www.vistax64.com/tutorials/91920-un...ntion-type.html

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

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!