Tripredacus

Still waiting on 2004 to be released. The information I got was GA is April 2020, so it is supposed to be released today! But probably not.

Dropdown is not a great example to use here, you could do it without javascript before CSS3.

The partition numbers would be correct. I suspect that the OS volume is getting Vol 0 simply because it is mountable, aka it is getting a drive letter. Another observable, although it is not immediately obvious by looking at the output I posted. In the deployment system I manage, a system with a formatted hard disk should get the letter N. This is seen in the SATA SSD M.2 output, where Windows volume is letter N, and the NVME it is letter D. In the expected scenario when booting off USB, an existing volume would get C, USB would get D. Then a script is run to change any C drive to N. This script is an old one and dates back to instances where card readers would be given drive letters even when media wasn't present. So in the NVME example, the USB drive is C, the Windows volume is D, the USB drive is changed to N, but is removed prior to running the diskpart and wmic commands. The expected is that the Windows volume is C, the USB drive is D and the script changes C to N. In any case, it would appear the volume order is not matching partition order. It is something else I can look at when I test on the older WinPE version noted. I also will re-run this test using an onboard RAID configuration using SATA spindle disks to see if there is any way to differentiate an m.2 in "RAID mode" vs an actual RAID array. If anyone knows of any other way to connection type with WMIC, it would be helpful. As I have not tested it yet, but knowing what goes through production, I am quite certain that actual RAID arrays are not being given Disk 1 and instead of Disk 0, as RAID1 are commonplace and I would have heard about those systems not being able to deploy. And I can't go on the presumption that a BusType 11 disk appearing as Disk 1 is an NVME because a RAID array on a controller card may appear the same way, if an onboard SATA, or RAID1/0 or M.2 SSD is detected as Disk 1.

While unknown as to what version this issue started with, the problem is replicated in WinPE v10.0.17763.1 but is not replicated in v10.0.14393.0. After much testing it appears that current WinPE detects an NVMe in an m.2 socket as a different type of disk (as expected) but then gives priority to other interfaces when it comes to disk numbering. The issue has been seen on 5 different boards so far, two different chipset manufacturers and 3 different board manufacturers. Using a fixed driver set, WinPE v10.0.14393.0, booting via USB with a board where the only disk installed is in an M.2 socket, either SATA SSD or NVME, WinPE will give the M.2 device Disk 0 and the USB key Disk 1. Using the same driver set, and WinPE v10.0.17763.1, booting via USB with a board where the M.2 socket has a SATA SSD, the M.2 device is Disk 0 and the USB key is Disk 1. If the device in the M.2 socket is an NVMe, the M.2 Device is Disk 1 and the USB key is Disk 0. That is the problem. I have collected information relating to how the devices are detected on v10.0.17763.1, using a NUC10i3FNK with M.2 SATA and M.2 NVMe. In each scenario the USB key is removed prior to running the diskpart or wmic commands. The NUC10i3FNK is set to AHCI and RAID is not an option. Yet the WinPE will detect the NVMe as BusType 8 aka RAID and have no location path. There is only one M.2 socket in the system and no settings were changed in between testing the SSD vs NVMe except for obviously removing one and installing the other. Normal WinPE is not able to run the WMIC command listed above. It requires WinPE-WMI, WinPE-NetFX, WinPE-Scripting, WinPE-PowerShell and WinPE-StorageWMI WinPE_OCs .cab files, installing the StorageWMI last. WinPE component reference: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference WMI MSFT\_Disk class: https://docs.microsoft.com/en-us/previous-versions/windows/desktop/stormgmt/msft-disk

The bus mouse returns! From inside the Express BIOS tool from Intel for a NUC10i3. For whatever reason there are tons of "things" listed inside, including processors like RISC and "Hobbit Family", socket types including ZIF, battery composition types (Lithium Polymer, Nickel metal hydride, etc). I had thought that perhaps it was for some compatibility checking, but there is no way a 64bit Windows BIOS flashing program is ever going to be updating a BIOS on a Pentium II.

Windows self-optiziming? Never heard of such a thing. I have always struggled at making sense of this tool at times. I always compare boot time to uptime. If I have a long uptime system, boot time is unimportant. If they are not long uptime systems, then I would compare boot time to disk type. I would never put a modern OS (Vista or newer, but also probably anything if possible) on a 5400rpm disk. For a 7200rpm disk I expect boot times to be maximum 1 minute. For SSD on used OS (not new install) it would be 30 seconds.

We know it is possible because it is something that can be done on PXE with Linux and WDS. You'd need a way to replicate that procedure if not using PXE. How it works in general... the client requests to boot to the server, the server asks for capabilities, the (typically) LAN firmware sends capabilities, then the PXE server passes along the appropriate boot option. For a local based solution, you'd need an initial boot platform that is not firmware dependent, can detect the capabilities of the client and then boot the appropriate EFI image. I would imagine the initial boot would have to be on DOS or Linux, or perhaps even an EFI application or EFI-shell script.

Possibly related to an old issue I had The thread is a mess and a resolution was never posted into there. I swear that a resolution was posted on the forum, but I am having trouble locating it. The issue in that thread was that I could boot in IDE using in-box drivers but not boot into RAID using Intel RAID driver unless I would zero out the MBR on the disk before installing. As for the resolution, for some reason I have this memory of the boot image having 2 indexes and having to inject the drivers into both (usually it is only index 2) before it would deploy. However, I also do not know if I had used my regular method of creating images on finicky hardware: creating a base install on another system. I looked on my deployment server and I ended up only using a single image and it was deployed using imagex to 1 partition. So I think that once the initial install was done, redeploying it wasn't an issue.

LTSC is not optimal for modern gaming hardware, specifically due to the fact that it is so far behind in build numbers. This is a problem for video cards and their drivers, as well as some other situations. I do work with LTSC, where 1809 is the latest build. There are other compatibility issues in general between video cards, software and CPUs with retail Windows builds, and the LTSC SKUs share these problems.

Tons of people not being able to go to a physical school building because their government has closed those venues due to the coronavirus.

Topic split from

Welcome to the MSFN!

I might be 1 or 3 or 5 or 7 or 100. What am I counting, what are they counting? Am I just me, or does my IoT notebook count, do my multiple MS accounts count? I have installed it hundreds of times and activated it tens of times.

I do not know what is involved with the Adsense issue and/or why Xper chose that particular mitigation. If I were to guess, this could be a starting point: https://msfn.org/board/topic/178681-whered-the-ads-go/?tab=comments#comment-1165751 That basically, we could see a large amount of "invalid traffic" from specific IP ranges. As the linked google support thread says "if we are unable to verify the quality of your traffic, we may limit or disable your ad serving." which did happen to us a few times as you can see in that thread.

As far as I'm aware, WinPE past v4 is not redistributable. However, you should at least add the drivers into the .wim using DISM.

I had talked to Xper last week about this issue. He says that there are some IP ranges that are blocked due to Google Adsense abuse. It effects a lot of countries including, at least, Poland.

SCP still is using an Xbox 360 controller driver?

I was looking solely at the crash report you posted.

tomasz, how long has this been this been a problem for you?

Nuhi has NTLite: https://www.ntlite.com/

Do the icons exist in the path specified in the stack? Ref: https://bugs.mojang.com/browse/MCL-10659 also: https://github.com/coffeenotfound/ModloaderFix-b1.7.3/issues/2

8.23 GB too big for a Dual Layer? Not sure what the overhead size is on those.

I ran into a situation where there seems to be a minimum Windows 10 build required that can boot on a TRX40 board with a Ryzen 3960X. I can't really find any information on what this version requirement is or if it is caused by a missing hotfix or driver. This is also primarily a WinPE concern, however it may also relate to the main OS equivalents themselves. The behaviour is that the PE will do the pre-load, but the activity indicator (spinning dots) do not appear, and the hardware does a hard lock. There is only USB on these boards, and the caps/num/scroll lock doesn't work. It could be that the hardware is not locked but just the USB portion is. I don't have a PCI-E PS/2 card to verify. These do not boot on the Ryzen board: - WinPE 10 (Kernel32.dll version 10.0.14393.0) - Windows Setup for IoT 1607 LTSB - Windows Setup for Windows 10 RTM or 1511 These do boot on the board: - WinPE 10 (Kernel32.dll version 10.0.17763.1) - Windows Setup for IoT 1809 LTSC - Windows Setup for Windows 10 1709 and 1803 These are all either WinPE on USB (although I do have a report that WinPE 10 (10.0.14393.0) via PXE does not work) or the WinPE that is part of the Windows installation DVDs. I have yet to see if a deployed OS version of say 1511 or 1607 will boot.

OK the first things that need to be resolved are the Content Security Policy errors. These are generated when an add-on or feature of the browser is specifically blocking a portion of a page. This can be a script blocker, any rules to block domains or types of scripts. Anything that would block cookies, (possibly XSS) or mixed/outside content, privacy settings, etc. You can look up each error to get a hint of where the problem is. The first one is specifically due to the site using frames, but is using an outdated method. This could be because the browser is blocking this use of frames, the browser is too new for the intended purpose or (more likely) the site developer is not using the appropriate coding for the target browser. OR that the browser is picking up a kludge for a specific browser when it isn't supposed to (aka, a compatibility fix, which may be sent erroneously if you are using a custom user agent). Ref: https://superuser.com/questions/1456787/what-does-this-mean-content-security-policy-directive-frame-src-has-been-de You can expand out the info on those other red lines to get more info. You'd need to research each to see if there is anything that can be done only on the client. There is also likely a lot of errors that are not the cause of the problem, and that a site may work fine with them being present. And also, without a full understanding of the page structure, it would be impossible to know which is worth focusing on and which isn't. Especially if this is a remote page and not something you have code access to. BUT, that is why the Content Security Policy errors should be the priority.

Is it possible to load this page or url or whatever, with the Inspector open? At least Error Console or Network tab (network tab isn't cached, so it needs to be open when the page load starts), it could give some hints as to what is not working properly with the browser.