Announcing Windows 10 Insider Preview Fast+Skip Build 17046 for PC Insider

I'm reposting this here, because I am very interested in hearing from those who are much more talented with coding than I am, and what they think about this, and why they might believe it is still not implemented? Thanks to anyone who chimes in.

Spectrum said:

Looks like the memory manager was initially mapping a file into memory (NT calls this a section object), it does this by allocating memory from pools of kernel memory. After that, it attempted to deallocate a block of pool memory with some specific tag (ExFreePoolWithTag). The evidence points towards a double free, in other words the memory manager is trying to free something that is no longer there, which leads to undefined behavior and often a crash.We see that the pool header and the first parts of the pool header contents are zeroed out. Combine this with the fact that the function that called ExBugCheck (which is the function that creates the blue screen among other things) was an attempt to free a pool allocation, so I think it was likely an attempt to free something that was already freed.For reference, a pool header is the metadata Windows kernel adds to requests when allocating/deallocating memory from a pool. You can view this data structure in windbg from a live kernel session:

Code:

dt nt!_pool_header   +0x000 PreviousSize     : Pos 0, 8 Bits   +0x000 PoolIndex        : Pos 8, 8 Bits   +0x002 BlockSize        : Pos 0, 8 Bits   +0x002 PoolType         : Pos 8, 8 Bits   +0x000 Ulong1           : Uint4B   +0x004 PoolTag          : Uint4B   +0x008 ProcessBilled    : Ptr64 _EPROCESS   +0x008 AllocatorBackTraceIndex : Uint2B   +0x00a PoolTagHash      : Uint2B

You see, this is what I have never understood about computer os's. If this indeed is the case, knowing all we know about AI today, why does the computer crash when it tries to free something that has already been freed???? Why don't they write code that is smart enough to recognize that it was already freed, and make a note of it, so this isn't a problem anymore, or in the future, INSTEAD OF THE SYS JUST CRASHING???? That seems so antiquated! Why do we get codes that we need to look up when there is a problem in our OS? Given the advances with text to speech as well as AI, why doesn't the computer just tell us in plain language what was wrong and how to fix it, or better yet, go ahead and fix it??? Computer OS's should be self correcting, and have the ability to diagnose their own code, or any other problems within it. This is the 21st century, and you have to wonder why it isn't already happening?

Kari said:

UUP to ISO tool failed, complaining about missing files.

Kari, are you talking about running the UUP to ISO tool failure with the UUP-Dump download or with the Windows Update download?

If you DID use the UUP-Dump download and failed, I can confirm your failure. Apparently the UUP-Dump doesn't contain the "Microsoft-Windows-Hello-Face-Resource-C-Package-amd64.cab" file. The Windows Update package in C:\Windows\SoftwareDistribution DOES contain the file, which I copied over to my UUP-Dump download directory.

Now running UUPtoISO again, with the copied "C" file added to the mix. Will know in as minute if it "works".

The problem with the Miniserver has already been solved, you just have to execute the "update.cmd" file.

I will install this update later. After reading what was added and what was fixed I'm not in a hurry to update. I was hoping the green screen crash on shutting down/restarting would be fixed. Oh well!