Recommended Posts

Before you jump in with build 9926, be aware of these issues I had:

1) wipes out any tiles you developed and replaces with defaults

2) As you recreate tiles with Oblytile, you'll note that tiles created for wide and large are displayed as tiny!

3) in build 9879 they did a nice job with expanding/resizing the start screen.  In 9926, that has been regressed to either narrow vertically scrolling or full screen, nothing in between.  Clearly, design specs were not important in development and this actually steps back toward windows 8 as a nod to touch screen users

4) Cortana not particularly good yet.

 

I rolled back to 9879

Link to comment
https://www.neowin.net/forum/topic/1244392-windows-10-build-9926-issues/
Share on other sites

Before you jump in with build 9926, be aware of these issues I had:

1) wipes out any tiles you developed and replaces with defaults

2) As you recreate tiles with Oblytile, you'll note that tiles created for wide and large are displayed as tiny!

3) in build 9879 they did a nice job with expanding/resizing the start screen.  In 9926, that has been regressed to either narrow vertically scrolling or full screen, nothing in between.  Clearly, design specs were not important in development and this actually steps back toward windows 8 as a nod to touch screen users

4) Cortana not particularly good yet.

 

I rolled back to 9879

 

Why?  The whole purpose of these tech previews is to give Microsoft feedback.  Tell them about the issues...I've submitted various feedbacks on all the tech previews.  Not sure of the reason to go back to older builds...that isn't going to help Microsoft or the end user much.

 

I'm not running it as a default OS though ... just VMWare so I can test w/o getting burned.

  • Like 3

I looked up Oblytile and the author has posted that it will probably never work with later TP and Windows 10 builds. It was a hack that just doesn't work anymore.

The new Start and Cortana aren't finished yet. This build is the first to include tablet-oriented changes and the start menu/page seems to be in a transition state right now.

 

You have to remember this isn't a demo of the final release. It's literally a build that passed a QA suite for stability so Insider members can see what they're working on. Some projects, like IE12, haven't even been checked in yet.

Sigh... If you read the Windows 10 blog, you'd know that #3 was specifically addressed. The Start menu has only "regressed" because it has been completely rewritten in this build. The old features of resizing, moving things around, etc. will return in a later build.

Nothing major so far but so far I've encountered

 

  • Explorer seems to randomly crash. My background will flicker black for a second, the taskbar will vanish and reappear devoid of icons before being refilled again
  • When right clicking tiles on the start menu in full screen, it creates a graphical glitch where a second duplicate tile would appear randomly on the screen until I selected an option in the right click menu.
  • When clicking the task view button, my screen becomes distorted, breaking the screen in half.

I think I found 2 things not working well with Win10.  Did not have any of those 2 problems with Win 8.1 :

 

1) I have a local folder with TONS (1160) desktop background images.  In the Personalization, Desktop Background, I select that folder and all the files and let Windows change the desktop every 3 minutes.  Each time Windows is about to change the background image, it "freeze" for a couple of seconds, sometime with the open windows flickering and if I was doing something in those open windows, well, it reset everything (ex: if I'm renaming a file while this happen, the cursor will disappear and the file will revert to the original name).  Almost feels like the GFX drivers are crashing and restarting.

 

Solution : Select only 1 desktop background.  I did not test to see just how much files you can select until this thing happens.

 

2) In Personalization, if you use "Automatic" in the Color and Appearance section, you will see ghosting while moving your windows around the screen.  You can see the ghosting in the title bar, where the controls are.

 

Solution : Select anything else than "Automatic".

 

EDIT : So the ghosting problem is still here, when you move around the window of a "modern" app.  It's gone if you move a File Explorer window.

Why?  The whole purpose of these tech previews is to give Microsoft feedback.  Tell them about the issues...I've submitted various feedbacks on all the tech previews.  Not sure of the reason to go back to older builds...that isn't going to help Microsoft or the end user much.

 

I'm not running it as a default OS though ... just VMWare so I can test w/o getting burned.

Absolutely and I have sent them this specific feedback.  Rolled back because 9879 had resizeable start "window".  It was affecting navigation and viewing of live tile data.  Other answers appear with other questions.

You rolled back because... Third party customizations broke? Perhaps you mistook the purpose of a technical preview build?

No.  1) Because this company has been heavily promoting tiles and not providing tools for it.  That's one of two issues.  But it is not about third part software, but lack of Microsoft software to do same;

and  2) most importantly, Microsoft made a big advancement in 9879 with resizeable "start window".  Then, because they changed the language they were using for coding, they regressed that advancement.  That changed my navigation entirely.  I stated to Microsoft that I rolled back as well so they would be aware.

3) Someone from ZDNet advised me about the language change and that the plan is to re-introduce the resizeable start screen

 

Regarding the comment "Perhaps you mistook the purpose of a technical preview build" -- a response with zero value.  I have given a ton of feedback and will continue to after this short stay in 9879.  Been a member of the program since September.  If you don't want members to hear feedback, I would ask you why YOU read this forum?

  • Like 1

Why?  The whole purpose of these tech previews is to give Microsoft feedback.  Tell them about the issues...I've submitted various feedbacks on all the tech previews.  Not sure of the reason to go back to older builds...that isn't going to help Microsoft or the end user much.

 

I'm not running it as a default OS though ... just VMWare so I can test w/o getting burned.

I did give them this feedback and also learned from ZDNet that the resizeable menu will return with a new build.  It didn't burn me as this is a secondary computer in my house.  When the next build comes around, I'll install from fast ring as before.  I never rolled back 9841, 9860 or 9879.  And 9926 was the first build I experienced in which there was a feature removed (resizeable verus maximizeable start screen).  That is why I rolled back.

I looked up Oblytile and the author has posted that it will probably never work with later TP and Windows 10 builds. It was a hack that just doesn't work anymore.

The new Start and Cortana aren't finished yet. This build is the first to include tablet-oriented changes and the start menu/page seems to be in a transition state right now.

 

You have to remember this isn't a demo of the final release. It's literally a build that passed a QA suite for stability so Insider members can see what they're working on. Some projects, like IE12, haven't even been checked in yet.

I am aware of this and agree with you.  But for the few weeks until the next build, I opted to roll back.  It is the first build I did that with, and not primarily because of Oblytile, but because resizing went away.  I took the opportunity to ask Microsoft for a Microsoft version of Oblytile during build 9841, 9860, and 9879, as well as 9926.  I'll keep advocating for that until Microsoft says they aren't listening any more

Sigh... If you read the Windows 10 blog, you'd know that #3 was specifically addressed. The Start menu has only "regressed" because it has been completely rewritten in this build. The old features of resizing, moving things around, etc. will return in a later build.

Do you not want your members to hear feedback already submitted to Microsoft?  If so, I will simply withdraw from Neowin.  No skin off my teeth, and not everybody spends their whole day reading blogs.

I looked up Oblytile and the author has posted that it will probably never work with later TP and Windows 10 builds. It was a hack that just doesn't work anymore.

The new Start and Cortana aren't finished yet. This build is the first to include tablet-oriented changes and the start menu/page seems to be in a transition state right now.

 

You have to remember this isn't a demo of the final release. It's literally a build that passed a QA suite for stability so Insider members can see what they're working on. Some projects, like IE12, haven't even been checked in yet.

That's exactly why I have advocated for a Microsoft supported version of a tile builder in 9841, 9860, and 9879.  Until there is listening to this, I will continue to give this feedback.  I don't want to use Oblytile either.  Reason I do large tiles is for my vision.  When it was taken away, it seemed they'd be sensitive to visual issues for start screen.  In fact, as you point out, they are.

I think I found 2 things not working well with Win10.  Did not have any of those 2 problems with Win 8.1 :

 

1) I have a local folder with TONS (1160) desktop background images.  In the Personalization, Desktop Background, I select that folder and all the files and let Windows change the desktop every 3 minutes.  Each time Windows is about to change the background image, it "freeze" for a couple of seconds, sometime with the open windows flickering and if I was doing something in those open windows, well, it reset everything (ex: if I'm renaming a file while this happen, the cursor will disappear and the file will revert to the original name).  Almost feels like the GFX drivers are crashing and restarting.

 

Solution : Select only 1 desktop background.  I did not test to see just how much files you can select until this thing happens.

 

2) In Personalization, if you use "Automatic" in the Color and Appearance section, you will see ghosting while moving your windows around the screen.  You can see the ghosting in the title bar, where the controls are.

 

Solution : Select anything else than "Automatic".

 

EDIT : So the ghosting problem is still here, when you move around the window of a "modern" app.  It's gone if you move a File Explorer window.

Not sure if relevant, but I think your desktop wallpaper folder might be too big

I had a similar experience with 7, but it was because I selected all the pics in my 33 gig folder (used to be bigger) instead of the folder with the 30 or so wallpapers made specifically for my displays

This topic is now closed to further replies.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      459
    2. 2
      +Edouard
      212
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!