Windows 10 Insider Preview Build 20236.1005 (rs_prerelease) - Oct. 16 Insider

cereberus · 17 Oct 2020

Went to create an Insider iso, and had option for Windows Team (PPIPro) - anybody know what that is?

Windows 10 Insider Preview Build 20236.1005 (rs_prerelease) - Oct. 16-image.png

f14tomcat · 17 Oct 2020

cereberus said:

Went to create an Insider iso, and had option for Windows Team (PPIPro) - anybody know what that is?

Maybe this? OS Exploration : Windows 10 Team (PPIPro) - the SKU used ONLY for the Surface Hub - YouTube

cereberus · 17 Oct 2020

f14tomcat said:

Maybe this? OS Exploration : Windows 10 Team (PPIPro) - the SKU used ONLY for the Surface Hub - YouTube

Yeah - I worked it out eventually. Just strange as I have never seen it explicitly shown.

uco73 · 17 Oct 2020

I'm roll back to 2004 version. Insider preview is crap. But this version is much better.

larc919 · 17 Oct 2020

cereberus said:

Went to create an Insider iso, and had option for Windows Team (PPIPro) - anybody know what that is?

My usual position if I've never heard of something is that it's not meant for me.

cereberus · 18 Oct 2020

I clean installed the latest Insider version and got the new office app and icon on the task bar which when you click on it enables you to use online versions without having to mess around going to online site to use them (basically it just is just links).

Overall, I think this is a good change as it makes life easier if you do not need or want to install full office version. I shall certainly leave them on taskbar on pcs without full MS Office.

rseiler · 19 Oct 2020

hed0n1st said:

I confirm the DPC_WATCHDOG_VIOLATION bug.
I am stuck on build 20201, every new builds since ran quickly into GSOD.
It seems related with my network card too, but i have an old Qualcomm Atheros AR8151 PCI-E , not sure if it's Intel related.

Intel was just a theory I had come up with based on querying several people with this problem and noticing in the dump file that it's all about networking. Since then, I've seen a couple people mention Realtek and now you with Qualcomm. It's an equal opportunity offender.

One thing has been consistent though: all the NICs have been old (well, the two Realtek people weren't specific enough for me to check, but every single Intel was and yours is).

CallMeSteven · 19 Oct 2020

rseiler said:

Intel was just a theory I had come up with based on querying several people with this problem and noticing in the dump file that it's all about networking. Since then, I've seen a couple people mention Realtek and now you with Qualcomm. It's an equal opportunity offender.

One thing has been consistent though: all the NICs have been old (well, the two Realtek people weren't specific enough for me to check, but every single Intel was and yours is).

Maybe in a build or two it will be resolved.

ZackMuc · 19 Oct 2020

For a software test i had to change the date to october 2021. now after I changed it back I get everytime when loggin in a message saying my build will expire soon

How can i repair this?

MikeMecanic · 19 Oct 2020

ZackMuc said:

For a software test i had to change the date to october 2021. now after I changed it back I get everytime when loggin in a message saying my build will expire soon

How can i repair this?

Welcome to the Ten forums,

See first if BIOS clock is set to current time and date. Go into settings (Date & Time) and turn the first switch off and back on again. The adjust for daylight switch must be ON. You may also try the Sync now switch.

I don't get why you play with time?

Evaluation copy, Expires 1/30/2021 3:27 PM (UTC-05:00}