Windows 10 Insider Topic

[GoodBytes]

Skip ahead gets a new build: 18855, which brings the new fixes of the Fast Ring to it.

I suspect Skip Ahead will start getting new things that Fast Ring doesn't have after Build.

[Stellar Ray]

Hi!

I got build update of 18352 from 18342.8. The installation didn't complete. At on point of multiple restarts, the system remained on, but didn't boot. The screen was't blank or anything, just off, but the system was still running, and restart or the power button didn't work, neither mouse or keyboard. This happened before during, during 18329 update.

 

Is this a common issue? Anyone else having the same problem?

[Excalibur20]

On 2/22/2019 at 9:01 PM, Excalibur20 said:

When I went to update my computer to the 18342.1 (19h1_release) build this came up. I went and updated all my drivers and it still didn't solve the problem. Not sure what to do.

Well, it appears that the problem was caused by BattleEye anti-cheat service and the Steam anti-cheat service. The solution is uninstalling Steam.

[GoodBytes]

19 hours ago, Excalibur20 said:

Well, it appears that the problem was caused by BattleEye anti-cheat service and the Steam anti-cheat service. The solution is uninstalling Steam.

Yea, BattleEye is a huge problem. I don't think Steam is an issue, as I have it Steam, and it seems work fine on my side.

Apparently, BattleEye is doing undocumented kernel level stuff to check for cheaters. The end results is that BattleEye is not working possibly anymore with the new version of Windows 10, (possibly also causing system stability issues). The company behind this system doesn't give 2 crap in fixing it, despite pressure not only from Microsoft but Epic Games and others. The problem is that big games like Fortnight uses it.  It has been months Microsoft is trying to work with the compant to have a fix ready, but sadly, BattleEye is not interested.

 

So, will Microsoft put a update block on anyone with BattleEye and those playing Fortnight will now never be able to upgrade? And if they re-install they'll have to say good buy to their games that uses it? Will Microsoft goes, "screw it", and remove it, and now millions of gamers are affected?

[GoodBytes]

For those interested in the coming up Edge web browser using Chromium engine:

Looks nice, they managed to add features that Edge didn't have as well.

Still works needs to be done, this is very early release, not officially released by any means. So no, you can't get your hands on.

[Yongtjunkit]

I actually noticed 2 issues with windows 10 1903( fast ring) 

1. Windows sandbox crashes on me every time I launch it  
2. Currently have office 365 installed on my computer, the office link in the start menu only opens office online for me not office 365, office 365 version 1902 

I’ve done a clean install of windows 10 1903 via the iso from the Microsoft website   

[bws2007]

On 3/23/2019 at 12:37 PM, Excalibur20 said:

Well, it appears that the problem was caused by BattleEye anti-cheat service and the Steam anti-cheat service. The solution is uninstalling Steam.

I'm on the build right now on multiple computers and steam is working fine

[Yongtjunkit]

Hi, I would like to know which build settings am I supposed to be in to receive the final version of windows 10 19h1? I’m currently on the fast ring and enabled the setting that automatically opts me out of the insider program once the final version is installed 

 

https://insider.windows.com/en-us/articles/check-your-windows-insider-program-settings/

[GoodBytes]

6 hours ago, Yongtjunkit said:

Hi, I would like to know which build settings am I supposed to be in to receive the final version of windows 10 19h1? I’m currently on the fast ring and enabled the setting that automatically opts me out of the insider program once the final version is installed 

 

https://insider.windows.com/en-us/articles/check-your-windows-insider-program-settings/

You need to pick: "Release Preview" under (Settings > Update & Security > Windows Insider Program > (wait for it to load, yes it takes ages for some reason) > Then under "Pick your Insider settings", pick your current ring that you are on right now (should be Fast Ring). When you click on it, it will get you to a screen where you can change your ring. Select "Release Preview"

 

[Yongtjunkit]

1 hour ago, GoodBytes said:

You need to pick: "Release Preview" under (Settings > Update & Security > Windows Insider Program > (wait for it to load, yes it takes ages for some reason) > Then under "Pick your Insider settings", pick your current ring that you are on right now (should be Fast Ring). When you click on it, it will get you to a screen where you can change your ring. Select "Release Preview"

 

Is there any refinement Microsoft is going to push to its users ? Or the next version is likely to be the release version(rtm) would definitely not want to miss out on those refinement that Microsoft pushes for 1903(19h1)

[GoodBytes]

1 hour ago, Yongtjunkit said:

Is there any refinement Microsoft is going to push to its users ? Or the next version is likely to be the release version(rtm) would definitely not want to miss out on those refinement that Microsoft pushes for 1903(19h1)

They were, already, more refinement (delivered as Cumulative Updates) that has already been delivered to the Release Preview Ring. Microsoft picked a build as Release Candidate, and start polishing with bug fixes tested by Fast Ring and Slow Ring insiders. The build might match or not the Fast Ring... all depending on which build they selected for final polishing. But they are no difference in features at this point, even if the build numbers don't match, if you wonder.  Even if you are Skip Ahead build, as we speak, there is nothing accessible by the pubic (probably will reveal features after May Update is released), and really open the doors after Build even in May.

[GoodBytes]

A new build arrived today, this one is intresting one. It doesn't something that I read before that Microsoft was apparently planning on doing, but I kinda didn't really understand the logic, and pass it off as improbabe, but yes.. it is true.

 

This new build of Windows 10 merges the fast Ring with the Skip Ahead ring.. in other words, Fast Ring will now have 20H1 updates, and the Slow RIng will be the targetted 19H2.

Initially, it was Slow and Fast Ring with 19H2, and only Skip Ahead that will have 20H1.

 

This is a strange decision to me. No explanation on Microsoft part.

I can only guess that they were very few people on Skip Ahead, and Slow Ring, and this is a way to push people on testing 20H1, and have people switch to the Slow Ring, for 19H2 updates. That is just a complete guess on my part. I have no proof, details, not even basing anything from any leaks... just stuff coming from my ass, I guess you can say.

[Yongtjunkit]

Hi, I have the opt-out setting turn on, on release preview ring, am I supposed to get this message about no longer able to receive insider build and will get anymore refinement and security update for this build till its official release?  The current version is shown in the screenshot below 

 

 

 

[Yongtjunkit]

Windows 10 1903( release preview ring ) just GSOD on my laptop while restarting 

 

the screen looks weird before restarting( looks like as if it has high contrast applied to it ) 

 

 

 

[GoodBytes]

19 minutes ago, Yongtjunkit said:

Windows 10 1903( release preview ring ) just GSOD on my laptop while restarting 

 

the screen looks weird before restarting( looks like as if it has high contrast applied to it ) 

 

This BSOD/GSOD is because a driver doesn't support sleep/hibernate power state. Sadly, you'll need to dig through log and event viewer to try and discover which driver is at fault. Once found, you have to make sure it is updated, hopefully it has the issue resolved. Another issue is a driver conflict has occured, and it is a serious pain to fix, and requires lots of playing arround, hate to say this, but a clean install is best.

 

What you can do, Revert back. Yuo have 10 days since you upgraded to revert back your system to the previous version of Windows that yu had, and everything should be back to normal as it was.

[Yongtjunkit]

5 hours ago, GoodBytes said:

This BSOD/GSOD is because a driver doesn't support sleep/hibernate power state. Sadly, you'll need to dig through log and event viewer to try and discover which driver is at fault. Once found, you have to make sure it is updated, hopefully it has the issue resolved. Another issue is a driver conflict has occured, and it is a serious pain to fix, and requires lots of playing arround, hate to say this, but a clean install is best.

 

What you can do, Revert back. Yuo have 10 days since you upgraded to revert back your system to the previous version of Windows that yu had, and everything should be back to normal as it was.

where can I dig through the logs to find the information that I need, reverting isn't an option since I've been using it for months(unless I do a clean install)

 

current video driver 

intel hd graphics 4000- latest version 

nvidia gt720m - win7(ASUS version) - this version was installed due to issues with win8+ drivers( including the latest version for windows 10) - this laptop comes preloaded with windows 8 

 

If you do mean dmp file, you may refer to it below

15-4-2019.html

041519-9343-01.dmp

[Yongtjunkit]

8 hours ago, GoodBytes said:

This BSOD/GSOD is because a driver doesn't support sleep/hibernate power state. Sadly, you'll need to dig through log and event viewer to try and discover which driver is at fault. Once found, you have to make sure it is updated, hopefully it has the issue resolved. Another issue is a driver conflict has occured, and it is a serious pain to fix, and requires lots of playing arround, hate to say this, but a clean install is best.

 

What you can do, Revert back. Yuo have 10 days since you upgraded to revert back your system to the previous version of Windows that yu had, and everything should be back to normal as it was.

I've just did a clean install via the windows insider advance iso, this time using windows update for all my GPU driver instead

 

when I try to update to the release preview build, I got an error

[GoodBytes]

1 minute ago, Yongtjunkit said:

I've just did a clean install via the windows insider advance iso, this time using windows update for all my GPU driver instead

 

when I try to update to the release preview build, I got an error

 

That indicates that an upgrade block has been put in place. This probabnly because of the issue you faced before and probably you were not alone on it.

You'll sadly have to wait.

 

My Surface Pro 3 cannot upgrade either to the latest build, WIndows Update shows an error even before it does anything. However, my old desktop ha sno issue. So this may be an upgrade block in place as well. Feedback Hub suggest I am not alone.

 

 

[Yongtjunkit]

36 minutes ago, GoodBytes said:

That indicates that an upgrade block has been put in place. This probabnly because of the issue you faced before and probably you were not alone on it.

You'll sadly have to wait.

 

My Surface Pro 3 cannot upgrade either to the latest build, WIndows Update shows an error even before it does anything. However, my old desktop ha sno issue. So this may be an upgrade block in place as well. Feedback Hub suggest I am not alone.

 

 

I think Microsoft used to tell you what driver/hardware/software that is causing the upgraded block ( something like the picture below ) Both GPU used to work in windows 10 properly

[Yongtjunkit]

11 hours ago, GoodBytes said:

That indicates that an upgrade block has been put in place. This probabnly because of the issue you faced before and probably you were not alone on it.

You'll sadly have to wait.

 

My Surface Pro 3 cannot upgrade either to the latest build, WIndows Update shows an error even before it does anything. However, my old desktop ha sno issue. So this may be an upgrade block in place as well. Feedback Hub suggest I am not alone.

 

 

the only issue is the time bomb is ticking

[Yongtjunkit]

On 4/15/2019 at 8:08 PM, GoodBytes said:

That indicates that an upgrade block has been put in place. This probabnly because of the issue you faced before and probably you were not alone on it.

You'll sadly have to wait.

 

My Surface Pro 3 cannot upgrade either to the latest build, WIndows Update shows an error even before it does anything. However, my old desktop ha sno issue. So this may be an upgrade block in place as well. Feedback Hub suggest I am not alone.

 

 

the problem happened again(screen in high contrast, this also happened in windows 10 1809), not sure if you can see the issue though. This time it was able to reboot without GSOD

 

Phone upload 

 

[GoodBytes]

24 minutes ago, Yongtjunkit said:

the problem happened again(screen in high contrast, this also happened in windows 10 1809), not sure if you can see the issue though. This time it was able to reboot without GSOD

 

Phone upload 

 

 

Heumm.. hmm....Something is totally screwed up. why mmc.exe is blocked?

Why cmd.exe needs admin (unless you asked for it)?

As for the contrast, I don't know... could be GPU driver issue..

 

Does your laptop support Nvidia Optimus by any chance?

I see that your GeForce 720 is a rebranded Fermi chip, and that one has been discountinued by Nvidia.

https://nvidia.custhelp.com/app/answers/detail/a_id/4656

I can't even find the drivers on Nvidia website for any version of Windows.

 

So you are stuck with the OEM drivers. If you have Nvidia Optimus, then even if you had support from Nvidia, you wouldstill be locked down to the OEM drivers for proper operation, as Nvidia Optimus is very finisky thing with custom Intel integrated drivers.

 

[Yongtjunkit]

59 minutes ago, GoodBytes said:

Heumm.. hmm....Something is totally screwed up. why mmc.exe is blocked?

Why cmd.exe needs admin (unless you asked for it)?

As for the contrast, I don't know... could be GPU driver issue..

 

Does your laptop support Nvidia Optimus by any chance?

I see that your GeForce 720 is a rebranded Fermi chip, and that one has been discountinued by Nvidia.

https://nvidia.custhelp.com/app/answers/detail/a_id/4656

I can't even find the drivers on Nvidia website for any version of Windows.

 

So you are stuck with the OEM drivers. If you have Nvidia Optimus, then even if you had support from Nvidia, you wouldstill be locked down to the OEM drivers for proper operation, as Nvidia Optimus is very finisky thing with custom Intel integrated drivers.

 

• the cmd.exe part, I asked for admin, if you looked closely, it says unknown publisher
• The Nvidia Part, I'm currently using is from windows updates( both Nvidia and Intel), the Nvidia driver won't work because " unsupported GPU error", don't remember it supporting Nvidia Optimus
• No idea why mmc.exe is blocked even though I'm logged into as admin user and on windows 10 home  

 

by the way windows was clean installed 2 days ago

[GoodBytes]

39 minutes ago, Yongtjunkit said:

by the way windows was clean installed 2 days ago

Hm ok, but I see so many things on your desktop, BitDenfer and a bunch of other stuff.

[Yongtjunkit]

28 minutes ago, GoodBytes said:

Hm ok, but I see so many things on your desktop, BitDenfer and a bunch of other stuff.

I've actually reinstalled almost all my software, Files on the desktop already exist since the files are stored on the D : drive, some icon on the desktop doesn't show any logo since I didn't reinstall them

 

 

edit: regarding about the Nvidia Optimus technology, apparently the GPU supports it but as far as I recalled, it's not enabled due to "not supported" message