Recommended Posts

Righto, I've tested build 6801, 6956 and 7000 and in the two later compatibility mode have NOT worked.

When I try to mark compatibility for any version of Windows, the application instantly crashes, it's like this for ALL exe's.

Have anyone else had these issues? I've tried just about everything and I can't get it to work, I guess I'll send some bug reports to MS so they'll have a look at it the second the official beta starts.

post-273418-1231129251_thumb.png

post-273418-1231129259.png

post-273418-1231129266.png

I know that with build 6956 which leaked, there was a bad image made where the creator didn't specify to leave symbolic links - therefore several things broke. I haven't seen this issue under build 7000 however, perhaps you have a bad installation or a bad installation disc?

I know that with build 6956 which leaked, there was a bad image made where the creator didn't specify to leave symbolic links - therefore several things broke. I haven't seen this issue under build 7000 however, perhaps you have a bad installation or a bad installation disc?

I wouldn't think so as just about everything else have been -perfect-, and the MD5 sums matched up and the DVD was verified as correctly burned.

At the moment it's the odd thing that doesn't work in Win7, everything else have been perfect, I've tried to search on the error code, but no luck there either.

  • 3 weeks later...

I think I have found the solution.

The crash is due to the wrong permission settings of the file "user32.dll" under "c:\windows\system32\" after the patch is applied.

You can still apply the patch to remove the watermark. Then you need to correct the permission of the file.

Go to "user32.dll", right click and select "Properties", under "Security" tab, correct the following permission settings.

System - only "read and execute" and "read"

Administrators - only "read and execute" and "read"

Users - only "read and execute" and "read"

TrustedInstaller - "Full Control"

File Owner - TrustedInstaller

Reminders: to add "TrustedInstaller", you need to type "NT Service\TrustedInstaller" without the quote.

Hope this information can solve the problem :)

  • 4 weeks later...
I think I have found the solution.

The crash is due to the wrong permission settings of the file "user32.dll" under "c:\windows\system32\" after the patch is applied.

You can still apply the patch to remove the watermark. Then you need to correct the permission of the file.

Go to "user32.dll", right click and select "Properties", under "Security" tab, correct the following permission settings.

System - only "read and execute" and "read"

Administrators - only "read and execute" and "read"

Users - only "read and execute" and "read"

TrustedInstaller - "Full Control"

File Owner - TrustedInstaller

Reminders: to add "TrustedInstaller", you need to type "NT Service\TrustedInstaller" without the quote.

Hope this information can solve the problem :)

works perfekt :)

thaks alot

I think I have found the solution.

The crash is due to the wrong permission settings of the file "user32.dll" under "c:\windows\system32\" after the patch is applied.

You can still apply the patch to remove the watermark. Then you need to correct the permission of the file.

Go to "user32.dll", right click and select "Properties", under "Security" tab, correct the following permission settings.

System - only "read and execute" and "read"

Administrators - only "read and execute" and "read"

Users - only "read and execute" and "read"

TrustedInstaller - "Full Control"

File Owner - TrustedInstaller

Reminders: to add "TrustedInstaller", you need to type "NT Service\TrustedInstaller" without the quote.

Hope this information can solve the problem :)

thank you very much

works like a charm now :)

Hey, thank you very much for that! But could you pls. help me? What is this?

TrustedInstaller - "Full Control"

File Owner - TrustedInstaller

Reminders: to add "TrustedInstaller", you need to type "NT Service\TrustedInstaller" without the quote.

I dont get it... pls. help me

pic http://img217.imageshack.us/my.php?image=89400776.jpg

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

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!