Tripredacus

It is designed to prompt for a product key unless one of these conditions are met: 1. The ProductKey/Key value is specified in the XML 2. The Edition or explicit path is specified in the XML with "/image/index" in ProductKey/Key value. 3. Specify edition in ei.cfg and have the associated default product key specified in pid.txt. Here is info about ei.cfg and pid.txt. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-edition-configuration-and-product-id-files--eicfg-and-pidtxt So take a look if your ei.cfg and pid.txt are causing the supression of the product key prompt.

That is a redirector, where did it usually end up? Now it goes to https://www.microsoft.com/en-us/ Are you saying that the browsers will show an error and keep the redirector URL in the address bar?

The only government contracts that I have worked on have dealt with either Windows 10 Enterprise or Windows IoT. So far, the only editions of Windows 10 that are decent enough to consider using, despite the amount of hoops required to jump through to get those versions.

The timing of this is weird to the point where it makes me wonder if it is really faulty or if they decided to take a different approach after Linus Torvalds complaints.

Welcome to the MSFN!

I think there are a fair amount of Linux users on this forum, they just don't seem to talk about it very much, outside of the side comment "I also use this."

Removed log and added as an attachment instead.

If you are not using a proxy server, uncheck the box to automatically detect a proxy server in Internet Options. Verify you have a valid IP address. If you have a valid IP address, verify that DNS works. You can do this by running these two commands: ping google.com ping 172.217.11.46

I believe this launch of the 10nm CPU also will coincide with a new chipset, which was reported to be the first from Intel for desktop boards to be UEFI only with no Legacy or CSM support. Whenever I get one of these types of boards or notebook in, I can definately try it. For usability reasons, there has been no real requirement that I have seen to need a "latest and greatest" system in terms of CPU or RAM, and Windows 7 can run just fine on even 3-5 year old hardware. My benchmark for requirements are games, so I do not know the requirements for other types of things such as engineering applications, etc.

I wish I had known about it ahead of time. I "found" this bug while on a production server. Also to note, running multiple DISM like this isn't supported. As even the ADK will not allow you to install it onto a computer that has a previous version installed. Say if you have ADK for 8.1 installed, you have to remove it before you can install ADK10. The only instance where this isn't the case is if you have the WAIK for Windows 7 installed, as the ADK installer does not check for that being installed. It doesn't check for Vista or 7 OPKs, or Embedded Kits either.

What is the name of the virus being reported to you? The name usually starts with W32.

Your signature image is too large. PS: your signature image was removed.

The DISM in the ADK is slightly different than the one that comes with the OS. I have never tried to use the ADK DISM in-place of the OS one, but I know the ADK DISM supports additional switches. DISM has dependencies, When I run multiple DISM versions, I put it into a folder. To save my time to determine what files are needed, I use the entire folder that contains DISM. For example: c:\program files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM and then take that DISM folder and call it something to know what it is, such as DISM10, and then you can put that folder anywhere. BUT be very careful about using DISM this way because you can screw things up! Using a DISM version like this means you need to fully qualify your paths to it and you don't want to run a different DISM by accident. For example, if you mount an image using the Win10 DISM and then unmount with the OS DISM, you will then have yourself a corrupted mount point and a memory leak. The incorrect DISM used will continuously allocate memory until there is none left, which should crash your computer. So I recommend if you are going to use multiple DISMs on one system that you build .cmds to handle them so you don't mistype and run the wrong one.

The forum says you joined 01/15/2018. If you had posted on the forum before, post a link to a post so we can investigate.

This is an OS file and is not redistributable outside of the ADK. If you don't want the whole ADK, you can try JFX's tool: http://www.msfn.org/board/topic/156869-get-waik-tools-wo-downloading-the-huge-isos/

That is the case for a lot of vulnerability checkers, they just see if a patch/update is installed by detecting it directly OR detecting what the patched behaviour should be and doing nothing if it is the wrong response besides throwing an error. In other words, they do not actually perform an action to trigger the vulnerability itself. So there is no real way to check any system to see if it is vulnerable, especially the things everyone seems to want to ignore being 32bit OS and stuff older than Windows 7. Hopefully someone finds a way to do a PoC detection on the issue so people can test these OSes.

So then we will not see fixes for legacy OS and likely even the patches we would see are for OSes in their support period or extended (paid) support period say for XP or Server 2003. If there ends up being a fix in XPe or POSReady2009, then this might be the way to get the update on desktop XP. I wonder about the methods for exploiting this, is it going to be the usual "it won't work on W95 because you need to use some thing that doesn't work on the OS" ... PS: added tags to the topic.

I think that it doesn't matter for the old OSes. As I said, I have just been using the same XML I made in WSIM for Vista on every OS since then, and they all have the lowercase k in key and it was starting this version that it would accept it. It is not a wholesale change as you can still use lowercase for other objects like settings, component, unattend and cpi. It isn't something enforced by the schema either, it would have been a problem if it was like <key></Key> but the case doesn't matter in XML as long as it matches.

General thread in Technology News: http://www.msfn.org/board/topic/177345-cpu-kernel-page-table-isolation-bug-disclosure/

What are these anyways? They are only the CPUs in the i-3/5/7 range according to wikipedia. https://en.wikipedia.org/wiki/Intel_Core Look at the contents/index part to see the breakdown. But I thought articles were saying this issue goes back 20 years? So they are not going to offer 20 years worth of fixes or Intel says that CPUs older than the ones listed do not have the problem? Based on the list from Intel, it would seem that ... say Core 2 Quad Q6600 does not have the problem. What about Pentium 4?

I just ran into a weird situation where the answer files I've been using since Vista time were not working on a Windows 10 Pro 1709 DVD I just got. It made no sense really so I had to do a WSIM validation and it just said the setting did not exist. The one it was complaining about was ProductKey/Key but it was not obvious. I deleted the object in WSIM and re-added it, then compared the old vs new XML that WSIM liked. The difference was an uppercase K. For years this worked and worked fine: <ProductKey> <key>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</key> <WillShowUI>OnError</WillShowUI> </ProductKey> But against the Windows 10 1709 catalog, it doesn't. It only recognizes Key and not key. And of course this isn't documented anywhere online that suddenly this one XML object is case sensitive. What a thing to change!

It could be a million things. Start first by posting what error shows on this screen. Also if there is any difference in the specifics of the error message when using different games.

An interesting note in there that this issue does not effect AMD CPUs (Ryzen comes out on top?) but putting in the patches to computers with AMD CPUs will slow them down just the same. Seems like it could be a nightmare for anyone using Windows 10 on a Ryzen... if (at least) the linux patches are CPU agnostic, you wonder if MS will make it so only PCs with Intel and ARM CPUs will get (or be able to be) updated with these specific fixes. But according to this, it is not: https://lkml.org/lkml/2017/12/27/2 Is it all just a bunch of FUD to lump AMD into this issue or has anyone been able to replicate it on their CPUs? EDIT: topics merged and title changed.

Image caption: "A South Korean government official checks the direct communications hotline to talk with the North Korean side at the border village of Panmunjom, January 3, 2018 / Reuters"

OK well if you had used a disposable email address in the past, it may have been the reason your old account was removed.