Recommended Posts

What a perfect setup for the 5th season. We'll have a far more tech-supported Fringe Division like in the other universe, and they know that the Observers are going to try to take over. Just a shame that we have to wait until the fall to start watching it again! So, does that mean that the opening sequence will go back to the usual blue instead of the amber?

I thought the finale was good but not great. It just felt more like a setup episode for the final season than a big final for this season. Maybe I guess it could've been more epic, I think that future ep we got took something out of it for me. Thanks to that the whole part at the end with Liv and Peter wasn't a surprise at all since we knew it was coming anyways, etc.

I thought the finale was good but not great. It just felt more like a setup episode for the final season than a big final for this season.

I've read a lot people say this on other sites. It makes me wonder if they were more prepared for a series finale and then they got a finale season and had to throw something together last minute?

I know the EPs have said that they didn't film anything else, but that doesn't mean they didn't write something else to wrap it all up. For example, Astrid getting shot was very anti-climatic. Some of the storylines, like that one, felt rushed.

I've read a lot people say this on other sites. It makes me wonder if they were more prepared for a series finale and then they got a finale season and had to throw something together last minute?

I know the EPs have said that they didn't film anything else, but that doesn't mean they didn't write something else to wrap it all up. For example, Astrid getting shot was very anti-climatic. Some of the storylines, like that one, felt rushed.

Yeah, that's kinda how it felt to me like we were getting close to a series final this time but then close to the end they got the green light for season 5 and they had to scale back these last two episodes. At least season 5 will be short so it doesn't get drawn out.

Them jumping onto the ship felt rushed and stupid. The Dialog inside the helicopter was pretty bad.

I agree, that whole helicopter bit was bad, felt like they just come up with it on short notice, too corny.

I think that the finale was written as a series finale. I suspect the flash forward episode was thrown in once they found out they'd get another season. If it had been a final episode it was good, predictable, but good. I hope the entire final season is a spin off of the single future based episode, that was a lot of fun to watch.

With the way Olivia was acting in the end I thought she'd reverted to the 'modified' Olivia that didn't remember Peter. They had been talking that she'd 'returned to normal', so I was fully expecting that to happen. Hell, it still might happen. Who knows.

That said... that ending. ABRAM'D. A season finale reminiscent of LOST, heh. I can't wait for the rest!

The season finale was really good. I was a bit surprised when

Olivia was shot in the head. Also, I wonder where William Bell went. He seemed a little unaffected about what happened. I'm sure he was disappointed but he really took it well. I wonder if he has another plan in case his main plan failed. As for the observers, I can't imagine how they're going to stop them.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • 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
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!