Recommended Posts

Windows 10 for Phones is so broken it's not even funny. I think it's ridiculous they're already releasing builds for phones, considering the state that they're in.

 

tech

ni

cal 

 

preview. 

 

what's so hard to understand about it, it's not for regular users or use. it's for developers

tech

ni

cal 

 

preview. 

 

what's so hard to understand about it, it's not for regular users or use. it's for developers

I

am

a

developer

 

:-)

The platform is just too rough/unfinished in my opinion to be released to the public already.

 

I

am

a

developer

 

:-)

The platform is just too rough/unfinished in my opinion to be released to the public already.

 

So you'd rather them not show anything and keep Insiders in the dark?

So you'd rather them not show anything and keep Insiders in the dark?

I feel this is turning into an endless discussion. I just think they should have waited until the platform is more robust/cohesive.

I

am

a

developer

 

:-)

The platform is just too rough/unfinished in my opinion to be released to the public already.

 

 

But you're installing it on your daily use phone and expecting it to work as a daily OS. 

10052 should have a good number of bug fixes compared to 10051, give it a try and see how it compares.  I expect lots more of these updated builds that have bug fixes and nothing new in them from now on.

  • 2 weeks later...

So does this compile it into a native windows application or does WP just use the "Jabba the Hutt" Runtime Enviornment ?

If it is the former, I hope this will be available for PC too. Sick of putting up with mediocre emulators like BlueStacks. 

 

Android apps are just Java and C++ iirc, Windows can run Java, it has for years, so really this is just an extension of what you could always do with Windows. This means that VS will take your Java code, and tell you what needs tweaking/changing, then at build time it'll spit out a native windows app without you needing to do something over.

It's not hard to think about really, the same with iOS apps, they allow VS to read and understand Objective-C, then spit out a native Windows 10 app.

anyone else having issues with Start not showing after the upgrade?

this is my first preview build and after I unlock it just sits on a black screen saying loading

 

this is a lumia 925 btw

anyone else having issues with Start not showing after the upgrade?

this is my first preview build and after I unlock it just sits on a black screen saying loading

 

this is a lumia 925 btw

Same thing is happening to my 930

For me the Start screen doesn't show up when closing all the apps through the task switcher. All you have to do is press the Start button.

The weirdest thing for me is the following:

My pinned apps were not sowing up after upgrading, but they were recognized as being pinned, because in the all apps lit it wouldn't let me pin them. Uninstalling and reinstalling fixed this, but I figured I'd just reset the phone to fix it. Now all my settings that would be under "Extras" are appearing in the All Apps list. Very weird stuff.

I did a hard reset most of the issues on the 1520 are fixed but I cant get to the start screen ? Even powering off and on the phone again just returns me to the all apps list.

Other than that its much improved.

How can I force installation through mobile connection? I don't have access to WiFi at the moment, and I rather not go and sit in some public place for hours to download the new build.

 

Never mind. I'll stick to 8.1 now. I didn't know it was THAT much buggy on a real device, thought it was only Hyper-V acting up. Surface Pro 2 was basically unusable. I guess I'll do my thesis on 8.1 and mention the 10 stuff and how it relates to it.

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!