Recommended Posts

And they are not killing WP7. If you actually paid attention instead of making nonsensical posts, a lot of the improvements in WP8 are hardware related. How do you put that update on a phone without that hardware? It would be stupid and inefficient. They are instead, being smart about it, and shipping 7.8 for those devices, which contains features that were software only...

true,they're not killing WP7, and it's actually more complicated than that. but come on now. for a couple of years ive heard people saying how microsoft had succeeded at avoiding the fragmentation seen in android, managing updates at the same time on all models and whatever. the result? microsoft stayed too long stuck on the same hardware and with self-imposed limitations like screen resolution. it was always clear to me that once the hardware started upgrading, they wouldnt be able to update the older gens (this is normal obviously). but they took it a step further by coming up with an entire new architecture behind it. which is not bad, considering WP7 was not THAT successful, you can argue that it doesnt affect a vast number of people. on paper WP8 is great. but for nokia it sucks.

Maybe, maybe not. Seems like a lot of Android companies are just doing "ok" while Samsung clearly is the winner. Nokia may be able to pull it off with their look/design...but who knows.

Microsoft really needs to start doing more/different advertising. Their smoked contests don't seem to be doing to much for them. Start showing more of what WP can do besides posting to Facebook and checking weather.

I would have bought a Lumia 800 and dumped my iPhone if it ran Android.

And I think the reason HTC is not doing so great right now is because they aren't delivering the best phone. If you look at what android phone is the most popular at any one moment it's the best one. And I don't mean subjectively the best, I mean the one with the best hardware. The most cores, the most ram, the largest screen. The S3 has the best specs of any Android phone on the market and the ones that HTC are selling while great are below the S3 in specifications but almost the same in price so obviously people are going to keep picking Samsung over and over until HTC (or another Android provider) bests it with what the hardware can do.

Sadly I'd have to agree.. they are looking more and more like RIM.

it has nothing to do with Android and everything to do with companies themselves. Samsung seems to be breaking all kinds of records and outselling Apple 2-to-1 with MONSTER profits thanks to Android. So the point is moot. It just shows it's not Android, it's the company making the hardware.

Nokia is more like Samsung rather than HTC.

Silly talk! MS gave Nokia billions of dollars!! That was the important aspect of this relationship. Google chose Moto as a partner, Apple is Apple and Nokia has who to work with? Nokia needs a marketing campaign to stay afloat. Word of mouth is not good enough anymore. Apple advertises like crazy and so does Samsung. We see their commercials all the time. Nokia had the beta test ads and then stopped after about a month. They need to put more money or effort into the phones they want people to buy. A huge marketing blitz on TV not the "smoked" stuff for at least 6 months and I think we would see the needle move.

  • Like 1

Erm what? That's like saying Apple killed iOS 3. Microsoft isn't killing anything, they are adding support for newer hardware. WP8 add support for hardware, WP7.8 adds software updates.

Wp7 is a platform like IOS but IOS 3 is a version of the platform.

wp7(All version are not getting updated to wp8 platform) underlying kernel and architecture changes

IOS 3 is still in IOS platform and latest IOS 5 is still on IOS platform...

also IOS3 has been updated to IOS 5 unlike just getting wp7.8

Sadly I'd have to agree.. they are looking more and more like RIM.

it has nothing to do with Android and everything to do with companies themselves. Samsung seems to be breaking all kinds of records and outselling Apple 2-to-1 with MONSTER profits thanks to Android. So the point is moot. It just shows it's not Android, it's the company making the hardware.

Nokia is more like Samsung rather than HTC.

No Nokia is not like Samsung they simply do not have the capacity to pump out endless phones like Samsung and I also question their ability to compete with Samsung's Amoled screens.

There is no evidence to support the suggestion that Nokia would be doing any better running Android would the pureview sell any better running Android and would the Lumia 900 really compete with the Samsung Galaxy S3?

Let's not forget that MS has invested heavily in Nokia which has helped to stem the tide somewhat at least until the true test (WP8) comes out. Additionally where does this notion come from that people are always asking for Android phone the experience I and many other people have is that they ask for the latest HTC or the latest Samsung most people couldn't give two craps about Android.

Nokia is far from finished in my opinion. In the US they may look down, but man when I was in the mid-east last month everyone that didn't have a smartphone had a Nokia. The biggest thing right now for them is trying to find their place again. Personally I love the Lumia Series phones, and its easy to say they are not doing well when you look at the dominating force behing the iPhone and Android markets. Nokia is playing it right with Windows Phone because it allows them to differentiate themselves. How well do you all really think they would have done competing with the Galaxy SIII if they had gone Android, I would venture to say worse off than they are now.

How well do you all really think they would have done competing with the Galaxy SIII if they had gone Android, I would venture to say worse off than they are now.

Would be hard now for Nokia to enter the Android market considering how dominate Samsung is. If Nokia started with Android around the same time, then it would be a different story.

Not this tired argument again, how many times do we have to bring it up? It's like someone on here has a hard time letting go or moving on. Nokia made it's choice, deal with it. If they sink or swim what do people really care? Companies come and go. Nokias stock went up 11% today, but yeah, they're oh so dead.

Elop didn't even give MeeGo a chance, that was the problem. The N9 was a much better phone than the Lumia series, and that was almost purely down to the OS. But as Elop said himself - even if the N9 is successful, we'll still drop it. What a CEO!

Not this tired argument again, how many times do we have to bring it up? It's like someone on here has a hard time letting go or moving on. Nokia made it's choice, deal with it. If they sink or swim what do people really care? Companies come and go. Nokias stock went up 11% today, but yeah, they're oh so dead.

why cant you let it go?? people who want to argue about it let them argue... people here made their choice deal with it.

why cant you let it go?? people who want to argue about it let them argue... people here made their choice deal with it.

U mad bro? I'm not the one making threads over this and always bringing it up am I? How about you try to find someone else to attack?

The main problem with Windows Phone is its name. Microsoft singlehandedly destroyed the reputation of both the Windows Mobile/Phone and Internet Explorer brands. People simply aren't quick to forget what happened in the recent past.

While I do agree that the brand names Windows and IE are tarnished and nigh on worthless these days, I don't think the whole failure of WP can be blamed just on the name. Clearly the metro/tile UI isn't resonating with consumers either.

The company could have had a fresh start by calling it Metro Phone with a different logo and a proper international launch. They failed at doing both and screwed up on many levels. Real shame and quite frankly unbelievable for a company the size of Microsoft.

A new name would help, but I still think the metro/tile UI is terrible. It just looks fugly compared to the beautiful ICS/JB UI. I know beauty is subjective, but once you've used an ICS Android device, it's impossible to use WP.

So far I'm absolutely loving my Nokia Lumia 900 and the Windows Phone experience. I have no plans buying a Nokia phone again if they decide to switch to Android.

That sounds like a fanboyish response to me. How can you dismiss all future Nokia devices simply because they run Android? I would never dismiss future Microsoft mobile OS's completely. If they improve enough and get good, of course I'll give them a try. I love Android and FOSS software, but not to the point that I'm xenophobic of other OS's just for the sake of fanboyism.

U mad bro? I'm not the one making threads over this and always bringing it up am I? How about you try to find someone else to attack?

Thats the same question I asked you on your previous comment(not literally)

if you cant let go people discussing this topic you cant say people to let go the discussion..

I am not trying to attack you but just trying to make my point about ur statement.. if people want to discuss let them discuss

A new name would help, but I still think the metro/tile UI is terrible. It just looks fugly compared to the beautiful ICS/JB UI. I know beauty is subjective, but once you've used an ICS Android device, it's impossible to use WP.

Purely opinion of course but strongly disagree here. I have several ICS devices.. and I flat out love my Lumia 900, nothing "impossible" about it. In fact, I'd go and say it actually looks better just for consistency, something which Android has issues with. The underlying OS itself is pretty, I'll give it that, but trying to get all the icons, gadgets, etc to look uniform.. now that's near impossible.

hat sounds like a fanboyish response to me. How can you dismiss all future Nokia devices simply because they run Android?

Again, just my own opinion and can't speak for him, but that's the reason I bought the Lumia in the first place. I didn't want the "yet another Android" phone. If Nokia goes that route, it's likely to be the last one I'd buy too as there's a crapton of Androids out there and the odds of me picking theirs specifically just went way down.

I might have stayed Loyal to Nokia if they considered an Andriod OS Phone, I'm not hating on Nokia, it's the only phone make I have ever used consistently in my 20 years of buying phones, I've had the odd Motorola here, the odd Sony there, but always ended up going back, I would like to make it clear I Absolutely LOVED my N8, and asked my Provider (O2 UK) for another N8 as my upgrade, was told no as the device is now obsolete, then asked if I could just extend my warranty if I renewed my contract but kept my old device, was told no again, I know that there are many users that didn't like Symbian, but personally I've never had any problems with it, the only reason I didn't buy a Lumia was because something in the back of my mind kept telling my it's not a great idea, (not that there's anything wrong with Lumia, it just wasn't for me,) then Samsung Smashed me in the face with the S3 and OMG! yes the HTC is a better device but seeing as I convinced O2 to give me the S3 for free (19 years with the same provider, regardless of their countless name changes) I'm not complaining.

But just imagine, with how good Nokia Displays are, and not to mention their build quality, a Nokia Lumia type device running Android...

(I admit, it's not for everyone.)

  • Like 3

How do you solve a problem like Nokia?

Keep simplifying?

(They are already doing that! You can't advice someone to do something they are already doing!)

Look to the past

Plenty of people think that while Nokia?s previous strategy was not perfect, it at least had it in control of the full stack: hardware and software.

(Nokia still has full control over both hardware and software. As per the agreement, they can do anything

with the software. In fact, they originally planned a full redesign of WP7, but changed that decision later.

And that also explains how they give features on their phones, which no other OEM can. Plus, they can

also make Apps exclusive to their phones only!)

Go Android

Nokia has already said in the past that it considered working with Google but decided against becoming

just one of dozens of manufacturers building on Android.

Except here?s the problem, Microsoft is not proving to be the partner Nokia expected: the appearance of Microsoft Surface tablet PC shows its apparent willingness to **** off OEMs.

(Whereas, Google hasn't released their own tablet (or bought one of it's hardware maker). Plus, they aren't even selling it at complete loss...)

And the decision to make Windows 8 incompatible with previous versions left Nokia having to rapidly discount Lumia handsets.

(Indeed. All the Android phones will get the latest and greatest Jelly Bean. This is what's Google is

famous for: compatibility. All the Android phones can run any version of Android, and absolutely any App.

Developing for Android is a piece of cake.

And here's the effect WP8 incompatibly is having on current sales.

-1

-2

-3

)

Get rid of Stephen Elop

Like many former Nokia staff, Tomi Ahonen ? now a prominent mobile industry analyst ? is bullish about

the company?s fortunes? if it chooses the right path.

(A prominent mobile industry analyst? Seriously?

It was under his time, that Nokia became a sinking ship, and that Symbian started to lag behind others. It

was under him that Nokia became dirt cheap, not Elop.

Nokia was a sinking ship, long before Elop was hired. And he is now taking major steps in the right

direction.

And as most naval experts would tell you, it's a very hard and times-taking process, to turn around a

sinking ship...)

Not this tired argument again, how many times do we have to bring it up? It's like someone on here has a hard time letting go or moving on. Nokia made it's choice, deal with it. If they sink or swim what do people really care? Companies come and go. Nokias stock went up 11% today, but yeah, they're oh so dead.

It's an argument that comes up for several reasons.

1. A lot of us actually like Nokia and don't want it to end up on a scrapyard while Microsoft shills pluck it away and destroy a great company so they can get their hands on their patents

2. Because Nokia is BLEEDING money and having to take money from Microsoft is just sentencing the company to death over the long haul. It's like taking money from a loan shark.

3. Because not only fans, but a big number of analysts are saying that Nokia HAS to go Android if they want to save the company (if it's not too late already). if they went with Android from the very beginning they would be most likely the dominante smartphone manufacturer on the market now.

While I do agree that the brand names Windows and IE are tarnished and nigh on worthless these days, I don't think the whole failure of WP can be blamed just on the name. Clearly the metro/tile UI isn't resonating with consumers either.

A new name would help, but I still think the metro/tile UI is terrible. It just looks fugly compared to the beautiful ICS/JB UI. I know beauty is subjective, but once you've used an ICS Android device, it's impossible to use WP.

That sounds like a fanboyish response to me. How can you dismiss all future Nokia devices simply because they run Android? I would never dismiss future Microsoft mobile OS's completely. If they improve enough and get good, of course I'll give them a try. I love Android and FOSS software, but not to the point that I'm xenophobic of other OS's just for the sake of fanboyism.

I believe the complete opposite Android is yet another me too UI that is completely boring and unituitive. It is a mess of icons and apps and is nothing new of the old phone interfaces of yesteryear (symbian etc) with its static layout. Yes it can be customised to your hearts content but stock android is a mess in my opinion. While WP may be difficult to grasp the beauty in static screens it really comes into its own when you show someone the interface. They really need to get a WP into the hands of every sales person as it will shine when given a hand on demo. Windows 8 will probably help mind.

It's an argument that comes up for several reasons.

1. A lot of us actually like Nokia and don't want it to end up on a scrapyard while Microsoft shills pluck it away and destroy a great company so they can get their hands on their patents

2. Because Nokia is BLEEDING money and having to take money from Microsoft is just sentencing the company to death over the long haul. It's like taking money from a loan shark.

3. Because not only fans, but a big number of analysts are saying that Nokia HAS to go Android if they want to save the company (if it's not too late already). if they went with Android from the very beginning they would be most likely the dominante smartphone manufacturer on the market now.

What complete nonsense you can't change the fortunes of a company like Nokia overnight it was hemoraging money long before it adopted WP and if anything that has actually slowed. I fail to see how going with Android would help Nokia the only company making profits off Android is Samsung and Nokia would not be able to compete. Why is MS giving Nokia money a bad thing it gives both companies huge benefits: Nokia gets investment it would not have got by going with Android as well as being able to modify WP. MS gets a prominent backer for their fledgling OS, as it is not like the other manufacturers have put much effort in. Nokia will not find success over night but come WP8 with the marketing might of MS's fall push (cross windows 8 compatibility etc) they might just turn it around. If anything had they gone with Android they would likely be dead already, they would be losing even more money (no investment) and have to spend money they don't have developing their own skin of Android only to be obliterated by the S3.

People seem to forget history...

Remember Xbox 1?

"Too late to the game, PS2 rules", "Xbox doesn't have any market share", "No major exclusives, it's doomed to be just a hobby project" etc...

And now Xbox 360 is up there with the PS3.

I believe WP7 is just like the Xbox 1, and Microsoft is applying all the knowledge they gained with it in WP8.

So as an iPhone user since 2008, for the first time ever, WP8 makes me think twice if on December I'll stay in iOS platform or move on to WP8. And believe me I'm huge supporter of the iOS platform, but innovation seems to just getting bigger and bigger on WP8.

And nokia doomed? Sorry but I don't believe that... Microsoft will never let it crash and burn...

This topic is now closed to further replies.
  • Posts

    • it would've been better to just have a screenshot with claude running instead of using a generic thumbnail that doesn't fit the narrative.
    • Helium Browser 0.13.2.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.2.1 changelog: 6b6fbd0f revision: bump to 2 (#1907) cb3f77bd helium/ui/zen: fix cmd+s shortcut sidebar preference in zen mode (#1849) e3980159 deps: bump onboarding (#1905) c99531d5 helium/core: add an option to copy URLs from tab context menu (#1904) c1aba0ea helium/search: add kagi image search params (#1899) eb6711f4 helium/core/hibernate: add an option to hibernate other tabs (#1901) 425306f5 merge: update to chromium 149.0.7827.102 (#1897) ae94c3c8 helium/core/update-pref: improve auto updates strings (#1896) 06897c1d patches & domain_substitution: refresh for chromium 149.0.7827.102 d09826d0 merge: update ungoogled-chromium to 149.0.7827.102 9aeb58da helium/search-engine: reject default engine urls without %s (#1893) 4d7bb965 Update to Chromium 149.0.7827.102 fa67665c i18n: fix "add shortcut" string collision (#1891) 6894bd30 devutils/i18n: parse meaning into source.gen.json dc3fe739 helium/kb-shortcuts: disambiguate "Add shortcut" string cbf38eb4 i18n/apply: pass meaning to fingerprint generator 53ea9920 extra/disable-jit-flag: build drumbrake only if supported Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • ExplorerPatcher 26100.8457.70.2 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.2 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 Fixed Windows 10 taskbar and Start menu crashes on builds 26220.8474 (Beta) and 26300.8493 (Experimental). Update ExplorerPatcher as soon as possible. Without this update, Explorer and the Windows 10 Start menu may stop working on future builds. Microsoft removed Windows 10 Start menu components from StartTileData.dll on these builds, so the Windows 10 Start menu option has been removed where it is no longer supported. Temporary workaround: replace C:\Windows\System32\StartTileData.dll with the version from build 26xxx.8457 (x64/ARM64). This may stop working in future builds. Work is ongoing to restore Windows 10 Start menu support. Highlights Fixed Windows 10 battery flyout crashes on build 25951+. Network flyout buttons reverted to pre-24H2 behavior as a side effect. Taskbar location changes now apply instantly. Windows 11 taskbar auto-hide is no longer modified when Explorer starts. "Open Start in All apps by default" is now hidden when using the new Windows 11 Start menu. Fixed Windows 10 Start menu crashes on builds 21996–22000.51. Fixed Regedit crashes when switching to thumbnail view in registry import/export dialogs. Improved compatibility with recent Windows builds, including 26H1 ARM64. Improved ARM64 performance. Added Greek translations. ep_taskbar Now supports all 43 Windows 11 languages. Fixed issues in the system tray and other components. Updated DLL naming scheme for mod developers. Improved TrayUI compatibility and vtable stability on builds with multiple ITrayUI revisions. Fixed a taskbar initialization deadlock. Windows 10 Start Menu Added a new tile layout engine to restore support removed in build 26xxx.8474. Restoration is currently partial: Tiles may overlap when pinned using "Pin to Start". Restarting StartMenuExperienceHost.exe or explorer.exe fixes the layout. Further improvements are planned. Other Changes Added an executable blacklist to prevent shell extensions from loading in selected applications. Updated Windows 10 Start menu animation support for ARM64 builds 28xxx.2149+. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.2 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft: Windows 11 KB5094126, KB5093998 finally stops trusting a critical system threat by Sayan Sen This week Microsoft released the Patch Tuesday updates for June 2026 with KB5094126 on Windows 11 25H2, 24H2, and KB5093998 on Windows 11 23H2. On Windows 10 22H2 it's under KB5094127. Alongside the announced release notes for the new builds, Microsoft has revealed another change that is coming to Windows with these new releases. It has been confirmed that custom folders are getting a significant change with the June 2026 updates as such folders or folder names defined by desktop.ini will no longer appear after this update is successfully installed. While you may inititally think this is a bug with the new release, Microsoft has stated that this is in fact "expected behaviour" in its new support article regarding this which Neowin spotted today while browsing. Essentially it's a security hardening measure such that custom folder presentations are treated as potentially unsafe whenever Windows is not sure about their origin and whether that desktop.ini folder can be trusted or not. Here is list of such untrusted files and folders: Files downloaded from the internet that carry Mark-of-the-Web (MOTW). Files copied from certain remote locations, such as some WebDAV or HTTP-based locations. Files on network paths that are not classified as intranet or trusted by zone policy. For those who may not be familiar, Desktop.ini is a special configuration file used by Windows to customize the appearance and behavior of individual folders. Basically Windows can read specific instructions stored in Desktop.ini instead of displaying every folder with the same default settings. This can be used to apply custom icons, thumbnail images, localized folder names, and such informational tooltips (infotip). The file can also influence certain folder-specific behaviors and properties. It is typically stored as a hidden system file within a folder that has been designated to support Desktop.ini customization. However, because Windows Shell automatically reads and applies these attributes whenever a customized folder is opened, they have historically (since the Windows XP days) presented an attack surface as a result of an unchecked buffer in the Shell component responsible for extracting custom attributes from Desktop.ini files. As such an attacker could create a specially crafted Desktop.ini containing a malicious or corrupted attributes and place it on a network share. So if a user were to browse that folder, Windows would automatically process the file, potentially triggering a buffer overflow. This could allow arbitrary code to run with the same permissions as the logged-in user. Hence a seemingly harmless folder could become a security risk when their contents are not properly validated. For admins and users alike looking to manage this behaviour, Microsoft has shared a few ways. One of them is to assign a trusted mark on the folder in case you are sure of its source. Secondly a policy can be used to revert back to the previous state. Finally, the MOTW can be removed too to indicate to Windows that this is a safe file. The company explains: Option 1: Add the source to Trusted Sites (Recommended) If the affected content is stored on a known internal or managed source, add that source to the Trusted Sites list. Once the source is treated as trusted, Windows processes desktop.ini from that source normally. This keeps the protection in place for other locations and is the lower-risk option. Option 2: Use policy to restore previous behavior Organizations that need broader compatibility can enable the policy Allow the use of remote paths in file shortcut icons.Enabling this policy restores the pre-June 2026 behavior for affected remote or untrusted scenarios. Option 3: Check for and remove the Mark of the Web (MotW) If the desktop.ini file has a Mark of the Web (MotW), Windows may treat it as coming from an untrusted source and block customization. Verify whether MotW is present and, if appropriate, remove it from the desktop.ini file. This can restore expected behavior, but should only be done for trusted content, as it removes the associated security protection. To remove the MotW tag, open PowerShell and run one of the following commands: For a single desktop.ini file: Unblock-File "C:\Your\Folder\Path\desktop.ini" For all desktop.ini files in a folder: Get-ChildItem "C:\Your\Folder\Path" -Recurse -Filter desktop.ini -Force | Unblock-File Microsoft has warned though against using a broad opt-out using the provided policy as it reduces protection against potentially malicious remote folder-customization content. As such the tech giant recommends trusting only controlled internal sources and keeping trust settings as strict as possible. You can check out the official support article here on Microsoft's website.
    • LAV Filters 0.82.0 by Razvan Serea LAVFSplitter is a multi-format media splitter that uses libavformat (the demuxing library from ffmpeg) to demux all sorts of media files. LAV Splitter is a Souce Filter/Splitter required to demux the files into their separate elementary streams. LAV Audio and Video Decoder are powerful decoders with a focus on quality and performance, without any compromises. Supported Formats: MKV/WebM, AVI, MP4/MOV, MPEG-TS/PS (including basic EVO support), FLV, OGG, and many more that are supported by ffmpeg! LAV Filters are based on ffmpeg and libbluray and is aimed to offer a all-around solution to perfect playback of file-based Media as well as Blu-rays. LAV Filters 0.82.0 changelog: LAV Splitter NEW: Support for demuxing Dolby Vision Enhancement Layer streams NEW: Support for Animated WebP images Changed: When demuxing Blu-ray discs, Dolby Vision metadata is available on the primary video stream LAV Video NEW: Support for Animated WebP images Changed: Hardware decoding support for DVDs has been removed Download: LAV Filters 0.82.0 | 15.5 MB (Open Source) View: LAV Filters Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      PsYcHoKiLLa
      207
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      79
  • Tell a friend

    Love Neowin? Tell a friend!