Recommended Posts

Startup Bug, Desktop.ini Opens in Notepad on Every Boot – FIX

This is an odd bug, mostly due to the fact that some instances of desktop.ini are visible and not set to system and hidden. Fortunately the fix for this is quite easy:

1.

Navigate to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

2.

Delete desktop.ini

3.

Navigate to C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

4.

Delete desktop.ini if present.

Source

Posting this from one of the other threads.

you know thats not grass right? ;)

Well I still reckon it's some kind of flora, and I don't recall seeing any blue or orange plants outside recently :p

In all honesty, it could look good if the orange wasn't as jarring - if it were done with the original image it could go together pretty well.

Anyway, new builds are always exciting. :)

Well I still reckon it's some kind of flora, and I don't recall seeing any blue or orange plants outside recently :p

In all honesty, it could look good if the orange wasn't as jarring - if it were done with the original image it could go together pretty well.

Anyway, new builds are always exciting. :)

yeah true i dont like the green with blue either it makes it look to soft and cool(cold) i want a little spice in my OS.

jesus man, think about it. quit praying for an early release, it will be 2010 and this confirms it in my mind.

Having an expiration date in 2010 means essentially nothing, happens all the time. Considering the public RC wiill be in April It would be shocking if it doesnt RTM this year.

Damn looks niiiice but the orange kind of sticks out i like it that way though!

I think it's good that the orange sticks out, so there's at least a little life in it :cool:

So are you guys convinced this is the same RC that will be released to the public in a couple weeks or is this just one of the pre-RC compilation builds that is just oh-so-close to being finished?

I'd say pre-RC. The actual RC will probably be compiled mid/late March when released April 10.

yeah true i dont like the green with blue either it makes it look to soft and cool(cold) i want a little spice in my OS.

Yes, it's simply too cold. That's why I think the orange would fit in fine there.

doesnt matter. sorry to break it to you and anyone else, thinking next year, but you are all wrong. Yep its true. Why do i think know so? because all RC and beta builds have long expiration dates. The beta expiration date lasts till a little pasts when RC is supposed to be released and the RC always lasts a lot longer than RTM (giving you ample time to purchase it and migrate over).

End of story.

P.S. I hope we get some more experts in here to confirm what im saying, actually scratch that you dont need confirmation, everyone is saying its already very close to RTM just because how good the quality of these builds are. Do we not all see the tech sites raving over how good win7 is right now?

actually the official RC build did. the RC candidate builds that were closer to the official (signed off) RC build probably had this built in as well. This is what your seeing with 7057, seeing as it is really really close to being THE RC build.

Basically, you are contradicting yourself. On one side you are saying that all RC builds have an expiration date after the RTM releases to give testers enough time to upgrade, and then you are saying the final release to the public will be in 2010? That does not make any sense.

There is no way of confirming just because the expiration is set for next March, it will release just weeks before that. Heck, take beta for example. It is set to expire in August, but they are going to release RC next month (4+ months before expiration). So even if you use the same analogy, it means the release will be before the end of the year. But more realistically, any expert will tell you the RTM will get signed off sometime during the summer even if it does not start shipping preinstalled on computers for a couple months later.

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

    • No registered users viewing this page.
  • Posts

    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!