UK court sides with Volkswagen on security concerns over key pairing


Recommended Posts

porsche-keys.jpg

 

Giovanni Ribisi had better hope he doesn't botch a job anytime soon. Flavio Garcia from the University of Birmingham cracked the security system that pairs an owner's key to their Porsche, Lamborghini or Audi, and Volkswagen's parent company wants that research to remain unpublished. The UK's high court sided with VW's owner and granted an injunction protecting the Megamos Crypto system. Afterward, Garcia was offered to print his findings, but without the all-important decryption codes. He refused, saying that the public has a right to see the holes in the systems it relies on and that this wasn't an attempt to give criminals a hand in boosting cars. While the court's logic is sound -- once revealed, all manner of "if this ever fell into the wrong hands" situations could arise -- it's unsettling to see government bend to corporate request. At least we know Eleanor can sit in the garage for just a little longer now.

 

 

http://www.engadget.com/2013/07/29/uk-court-volkswagen-megamos-crypto/

1) government =/= justice system, in fact, they should be two completely different entities, so saying that the government bends to corporate request because of the decision of a Judge is kind of stupid

2) the decision is completely logical, I really don't see this as censoring just because a company wants to have something censored. Releasing those decryption codes would make it somewhat too easy for the criminals to make their own keys

It's not a "corporate request" so to speak. If it got out, thousands of cars would be much more easily stolen, with potentially no way to patch them.

 

I agree with the court on this. It kinda annoys me how hackers these days call themselves "researchers" and then think that the public has a right to their "research".  No, you're a "hacker", and nobody has any right to see your "crack".

Absolutely the right decision IMO. This "researcher" is clearly an ass who just wanted to make a name for himself.  It's absolutely irresponsible to release this information to the public; all it will do is facilitate car theft as VW have no practical way of updating the software in the cars.

 

He should have just contacted VW and tried to work with them on improving security, not wave his epeen at them.  The public does not need to know this information.

Absolutely the right decision IMO. This "researcher" is clearly an ass who just wanted to make a name for himself.  It's absolutely irresponsible to release this information to the public; all it will do is facilitate car theft as VW have no practical way of updating the software in the cars.

 

He should have just contacted VW and tried to work with them on improving security, not wave his epeen at them.  The public does not need to know this information.

The researcher is in the right. With this court order you WON'T see a recall of the cars with this security system. If the information would actually be released then the car manufacturers would have to issue a recall to reprogram the systems.

 

If they can figure out how to do it then anybody can do it, it's not as if car thieves are all stupid, they have their own research teams.

The researcher is in the right. With this court order you WON'T see a recall of the cars with this security system. If the information would actually be released then the car manufacturers would have to issue a recall to reprogram the systems.

 

If they can figure out how to do it then anybody can do it, it's not as if car thieves are all stupid, they have their own research teams.

 

Actually, no... they wouldn't have had to recall anything.  This "researcher" found a flaw which cannot be exploited remotely, so there would be no need to recall anything.  Also, car manufacturers only recall cars when there are actual design faults which affect safety; this doesn't come under that heading at all.

It's not a "corporate request" so to speak. If it got out, thousands of cars would be much more easily stolen, with potentially no way to patch them.

 

I agree with the court on this. It kinda annoys me how hackers these days call themselves "researchers" and then think that the public has a right to their "research".  No, you're a "hacker", and nobody has any right to see your "crack".

Except that the researchers are university researchers from the school of information security at the university. They do this professionally with ethical oversight and peer review (they'd already sought and achieved reviewed status).

 

Absolutely the right decision IMO. This "researcher" is clearly an ass who just wanted to make a name for himself.  It's absolutely irresponsible to release this information to the public; all it will do is facilitate car theft as VW have no practical way of updating the software in the cars.

 

He should have just contacted VW and tried to work with them on improving security, not wave his epeen at them.  The public does not need to know this information.

Clearly haven't read into this properly. They contacted VW 9 months previously and gave them full details of the exploit.

 

On top of this, they asked for VW to ok the release of the work once they had a chance to fix it. VW chose not to respond but rather filed for an injunction.

 

This kind of research is important. Arm chair lawyers like you guys need to do more reading before making judgements like this.

 

EDIT::

It's also worth noting that the research they did was from a leaked copy of the software used to determine codes for the cars. That was already out there and remains on the internet.

So? It's still not information which the public "needs to know", so attempting to release it into the wild, especially knowing full well that it's NOT fixed, is completely irresponsible.

 

Would you like it if someone released information on how to hack YOUR car into the public?

Except that the researchers are university researchers from the school of information security at the university. They do this professionally with ethical oversight and peer review (they'd already sought and achieved reviewed status).

 

Clearly haven't read into this properly. They contacted VW 9 months previously and gave them full details of the exploit.

 

On top of this, they asked for VW to ok the release of the work once they had a chance to fix it. VW chose not to respond but rather filed for an injunction.

 

This kind of research is important. Arm chair lawyers like you guys need to do more reading before making judgements like this.

 

EDIT::

It's also worth noting that the research they did was from a leaked copy of the software used to determine codes for the cars. That was already out there and remains on the internet.

 

 

Except that the researchers are university researchers from the school of information security at the university. They do this professionally with ethical oversight and peer review (they'd already sought and achieved reviewed status).

 

Clearly haven't read into this properly. They contacted VW 9 months previously and gave them full details of the exploit.

 

On top of this, they asked for VW to ok the release of the work once they had a chance to fix it. VW chose not to respond but rather filed for an injunction.

 

This kind of research is important. Arm chair lawyers like you guys need to do more reading before making judgements like this.

 

EDIT::

It's also worth noting that the research they did was from a leaked copy of the software used to determine codes for the cars. That was already out there and remains on the internet.

 

So what exactly would VW do if the exploit was made public? Recall EVERY single car? Even if they did - only a small percent of customers would do anything about it.

 

Genuine security researchers aren't in the business of making exploits which could harm members of the public, public. Just because they work for a university, doesn't mean they don't have any malicious ideas.

They offered to remove the segments that would allow the hack to be reproduced.

 

VW choosing not to pursue a fix is irresponsible. Obscurity doesn't provide security. If these gentlemen could generate the exploit, other people with lesser morals can.

 

Keeping the exploit secret doesn't protect people; releasing it would force VW to actually fix the issue (which is doable via a key recode).

 

Would I like it if it was my car? No. Do I think it's necessary despite it being a pain in the arse? Damn straight I do

So what exactly would VW do if the exploit was made public? Recall EVERY single car? Even if they did - only a small percent of customers would do anything about it.

 

Genuine security researchers aren't in the business of making exploits which could harm members of the public, public. Just because they work for a university, doesn't mean they don't have any malicious ideas.

On that basis any security researcher who identifies a bug and publishes the research is malicious.

 

The re-key can be done in about an hour during a regular service. That would cover the vast majority of people.

 

In the meantime, whilst this information is not out in the public, other manufacturers are not aware of how the system was defeated (and thus how to improve their systems or even whether their systems are still secured) and people aren't aware that their cars can be accessed illegally.

 

There's a plethora of good reasons to release information that could be detrimental to the public. The balance that must be struck is whether keeping it private exposes people to greater risk. If VW didn't have a reason to change their key coding system, what do you reckon the chances that they would are?

 

For the record, the software is that was used to derive this attack is still online (as was noted in the court case). People are still vulnerable, only unknowingly so now.

The problem is, no system will be completely un-hackable.

If you stare enough at the same data, you will make patterns out of it.  Just like hacking, the more you try to crack something, the shorter the time of the crack will be.

 

Why these companies don't take on the "hacker" to produce the next "secure" system, I don't know.

The problem is, no system will be completely un-hackable.

If you stare enough at the same data, you will make patterns out of it.  Just like hacking, the more you try to crack something, the shorter the time of the crack will be.

 

Why these companies don't take on the "hacker" to produce the next "secure" system, I don't know.

Indeed.

 

The answer to the latter is that creating secure systems is the exact opposite process of assessing them.

On that basis any security researcher who identifies a bug and publishes the research is malicious.

 

The re-key can be done in about an hour during a regular service. That would cover the vast majority of people.

 

In the meantime, whilst this information is not out in the public, other manufacturers are not aware of how the system was defeated (and thus how to improve their systems or even whether their systems are still secured) and people aren't aware that their cars can be accessed illegally.

 

There's a plethora of good reasons to release information that could be detrimental to the public. The balance that must be struck is whether keeping it private exposes people to greater risk. If VW didn't have a reason to change their key coding system, what do you reckon the chances that they would are?

 

For the record, the software is that was used to derive this attack is still online (as was noted in the court case). People are still vulnerable, only unknowingly so now.

 

That's great - if you have your car serviced at a main dealer. What % of people do that? Considering the prices they charge, not many.

 

So - VW could send a mailshot. Cool. Except - what about people that bought the car used? How to they get contacted. He has contacted VW - they do know how it was defeated. And how do you know car manufacturers don't share security information (which it's in all of their interests to do)?

Everyone, because it's a manufacturer fault. It will be covered by VW.

 

Your position on this plays into my stance. My point is that you must publish the information publicly, otherwise people who have a second hand car have no chance of finding out about the issue. You can publish without details of how to exploit the issue and people can get their cars looked into. This is what VW has chosen to block. If you read into this, you will the researchers offered to publish without including the key codes or details about the exploits execution. VW filed for an injunction regardless.

 

To answer your final point: given VW is approaching this as security through obscurity, I'd suggest that they aren't sharing.. Not very obscure if you share how you do it.

 

The basic principles of cryptography are well known. Something VW is doing isn't in line with best practices, that's how it got cracked.

 

Even if you want to suggest VW isn't doing the wrong thing; your original stance that this is hackers claiming to be researchers is completely untenable.

They should be recalling cars NOW and fitting a new version. We now know its possible to crack so someone somewhere is working on it right now and they WILL release it in to the wild, when they do thousands of cars will be vulnerable. By releasing the exploit now VW would be forced in to fixing it, but they choose to cover it up and leave people vulnerable just so they don't lose money. I'm sure VW will already be planing Excuses and T&C modifications to cover themselves.

One could say the same in regard to publishing nefarious information about lots of hardware just browse you-tube for lock picking or getting into a hotel safe or through their card lock doors and you get the drift.Just because you make a lock system doesn't I think ,make it right that the security behind the device cannot be publicly posted.

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!