Tripredacus

Well here is some info about creating items in Control Panel https://msdn.microsoft.com/en-us/library/windows/desktop/hh127450(v=vs.85).aspx And the CLSID list for some objects in Windows 10: https://www.tenforums.com/tutorials/3123-clsid-key-guid-shortcuts-list-windows-10-a.html On Windows 7 Pro, running explorer shell:::{C555438B-3C23-4769-A71F-B6D3D9B6053A} will launch the Display panel, but on Windows 10 Enterprise 1803 it gives an error. So perhaps in 1803 it is different than on that site and you would have to dig abour in the registry to find the correct CLSID.

Remember that spoofing only will cause the site to make available code specific to the browser you are identifying as. It all depends on how the site is written. Identifying as another browser or application does not magically give your browser the ability to do the things the other software is capable of. If they are adding some code that doesn't work in older versions of Firefox, even if they don't put in a version checker, the page may not work properly because your version can't execute the code. As noted, it is impossible to tell what the results will be until that site updates their site, only then would you know if changing your user agent will make the page work or not.

The progression of sizes of spindle disks should have solved this years ago, right when 1TB became "the" standard size for disks. Then things changed. SSDs came out and they were far superior, but their storage sizes were quite small in comparison. How long have they been around for now? You can get yourself a 500GB SATA SSD for under $100 USD, so still not quite good cost wise vs a 7200rpm disk. Then the situation where desktops stopped being the king of computers and was overtaken by notebooks, and to a greater degree, mobile systems. Microsoft seems to be following a model where Windows is generally the same across all of the platforms. And this makes sense if you consider that they didn't invent a new OS to run on low end mobile devices with low amounts of storage. They ported Windows over to fit into that space. So if cheap computers with small storage sizes make up the majority of the Windows platform, we can expect that any changes made to Windows are for those things. And since they don't seem to actually have a separate product for different devices, you are going to see those "features" show up in the desktop space. That is why your desktop computer running Windows 10 has a tablet mode and an airplane mode. And it is quite interesting that they did not bother to segment those features obviously designed for the low end products so that... say.... Windows 10 Pro or Enterprise wouldn't have the same stuff as whatever they put on the Surface Pro. Especially considering the fact that Microsoft has tons of different SKUs for licensing where you have to use specific OS versions on various different devices. It seems that the licensing department knows more about the differences between computers than whoever is making development decisions.

The things Microsoft does always has to deal with the largest common denominator. Rather, they are not saying "you should have a second hard drive to save your files/programs on, never save anything into your user profile and don't save anything into the C drive" and are only being concerned with the typical configuration where a Windows PC has 1 hard drive. Part of me also thinks that they are just moving 7GB from one place to another. It doesn't solve anything and they could possibly accomplish this without having to reserve space at all... if Disk Cleanup actually worked properly. You can see their plan here, saying they will come up with some method to automatically free up space if needed. They could just use this on a regular install and solve the same problem, right? And then they even anticipate that this won't work properly and give you the option to span your OS disk to external drives! If this becomes prime time, can we expect to see some of these issues appear: 1. The Reserved Space cleanup program deleted stuff outside of the reserved area? 2. After spanning C drive to USB key, OS won't boot with key removed? 3. Performance degredation after spanning C drive to USB key (say some poor chap spanned his SSD to a USB 2.0 drive) Then again, if updates weren't 4+ GB, perhaps they wouldn't need to bother with this. I wonder if they looked into expanding the System Reserved partition instead and writing some filter driver to store the files in there. This partition is typically hidden already and rarely ends up having anything inside of it besides boot files, or perhaps a winre.wim, despite usually it being between 250-500 MB in size. Oh but then again, perhaps they are not confident that their automatic cleanup tool wouldn't delete the BCD or boot files...

Destro, that doesn't seem entirely relevant. Ruthan, take a look at this, it is for Windows 7 but perhaps it still works for Windows 10. You may even get to look into the temp folder to see if any logs are already present with the timestamp of your boot time. Otherwise, try setting the registry key and see if it makes any "better" logs appear. https://superuser.com/questions/180281/what-folder-are-installation-logs-in There was nothing really of note in the CBS.log. In the most recent reboot, nothing much but in the one prior Windows Update was doing something.

It can be difficult to track msiexec.exe by process name due to the way it operates. It usually will create a process, exit and re-open a new process. For trying to figure out what runs it, you may want to look into the CBS.log. Of course there is always the Windows Performance Toolkit, part of the ADK, which has bootlogging tools.

There really shouldn't be any price fluctuation on buying the OS, Partners typically have to just sell it for a set price and that is it. I can say for certain that a company who is reselling the System Builder Kit will not be selling it lower than cost. It is an expensive product still and the online prices are usually at or perhaps 1% above cost. For the version where you just get a product key, the email should be coming from Microsoft so the keys should not be recycled. If they actually were OEM keys instead of retail, you'd be able to tell by doing a licensing check. Since OEM, VL and Retail are generated differently, the licensing tool can tell you which type of key is it. The reason why keys from a legit source would not work would be because someone, somewhere had already used that key to activate a Windows 10 previously, I'm sure we are all aware of how that is accomplished. When I look onto Newegg, it only shows the three options: "OEM" which I presume is the SBK, "Download" and USB Flash drive: https://www.newegg.com/Operating-Systems/SubCategory/ID-368 I also would imagine that a physical Retail kit must exist, but perhaps that is not sold online and only in physical stores.

My first thought is that you booted the USB stick in EFI mode. But that is only a guess. You'll need to view the log file on the ramdisk after this happens to see if there is any more info. When you get the error, you can press Shift+F10 to get the CMD.

Here is a different angle of it, from Instagram: I was not able to find the actual posting, this only shows in Google Images and when you try to view the site it comes from, it is not on that page. If I were to guess, it was a mall in Germany or Austria, judging by the "Doppelte Power" sign you can see in the first pic, which is an advertisement from Hauwei.

Welcome to the MSFN!

Yes we had gotten a bunch of keys from that design from Intel, all 2GB size. They all seemed to be very slow to write data too, and I eventually gave all of mine away to other co-workers and opted to use some much-faster 1GB keys that were from a previous promotional campaign.

I think I had tried it because a vendor gave us a bunch of "large" USB keys as a gift, or free crap when trying to sell a product. Indeed, it was only 2GB size and probably not on the MS supported devices list. And sure, when it ate that key up a few months later, 2GB USB keys were still quite expensive at the time.

Readyboost did actually work. I even used it for awhile. The problem with it was that it wasn't worth the cost of devices to use it. By that I mean that it would kill USB storage quite fast and eventually it was easier to add more RAM than having to buy more USB keys.

The path is C:\users\%userprofile%\downloads They really did screw up the default Explorer view if you ask me, it always shows everything duplicated by default. On my Explorer, it shows Downloads on the left under Quick Access and This PC.

Not sure about it being worthless, I'm sure that the speed increase is technically there. In many circumstances it come down to the user not being able to tell the difference in launching a program with or without Superfetch on an SSD... or even on any sort of disk. Does Superfetch really make Notepad open faster? How can you tell? What about long-to-load programs like Adobe Illustrator or Photoshop?

No I think the myth of it reflecting BIOS boot order stems from "I saw it once, it must always be this way" phenomena. And heck, it might actually work that way for some specific board and/or BIOS version, but it is not designed to work that way and certainly can't be used as a general fact for all computers everywhere. It was proven through observation that Windows Setup will sometimes write the boot entries to other disks. Microsoft never has written up a why or a how to resolve (not even a simple, disconnect your other disks during install KB) and their representatives on forums fall into the trap of "that is how it works sometimes" when it obviously seems like a bug... one that has been present since Vista. The Disk Selection screen does not have anything to do with where the boot files are written, that is the problem. Disk Selection simply is the UI portion for Setup to manually format disks/create partitions and to create the answer file it uses and set the image target. The bits that deal with running BCDBoot (which I don't think it does directly, rather uses some API calls) after installing the image, prior to the reboot into phase two, is done with some other magic. And even this critical phase of installing Windows is not configurable via an XML file create with WSIM. Alas, this issue has existed for such a long time, and has such a small impact on support, even if it were determined why it does this (by testing a butt ton of configurations that no one has time for) I doubt they would even fix it.

It seems like normal usage to me. Do you have SuperFetch enabled?

WindowsPE uses the same method that Windows OS itself does as far as I'm aware. See here for an explanation from MS: https://support.microsoft.com/en-us/help/937251/disk-drive-numbers-may-not-correspond-to-the-sata-channel-numbers-when

What is the actual memory usage with the hardware mapped memory removed from the total?

Predabot changed to DoomN00b

This is incorrect. If the motherboard fails, you can migrate the array to any other board (same model or different) as long as it has the same storage controller on the board. On the destination board, you would enable the RAID with no disks attached, shut it down. Then connect the disks from the other board to the same ports as the original board, boot the system and enter the RAID manager. Presuming that the disks themselves are sound, at the worst you'd have to do a rebuild. So it may not be a simple solution, but besides being able to read a single disk as jaclaz mentions, it is not a total loss to lose the board. But then again, this brings up the other point, RAID is not a backup solution. You lose the array, its a pain but you would have the backup, right? I will note that I have only done array migrations with a RAID1. I have never found RAID0 to be worth the risk for OS volumes and hasn't been a viable speed option since the advent of SSDs.

Then perhaps it is backwards, and that some RAID software will refer to a single disk outside of an array, while still being managed on the controller, as a JBOD disk, even if singular. Terminology aside, there are still some RAID software on desktop boards that do not allow for a single disk to exist outside of an array and documentation for those boards rarely mention such a thing. Usually only find out if it is possible by attempting it, unfortunately.

Well perhaps, but it is, in effect, what a disk on a RAID controller is when out of the array. With a desktop board, you do not get the luxury of having SATA ports not be on the controller when you change the setting in the BIOS. On modern systems, only M2 sockets get this luxury.

Using generalities, a non-specific desktop motherboard with RAID capability will typically have only one storage controller option for all of the disk connections. As opposed to a workstation or server class board which can have two controllers, assigned to specific or selectable ports. In the general use case of a RAID capable desktop board, it would infer that changing the SATA mode to RAID will change all of the ports to that controller. So the SSD in the first post would need to be added as a JBOD, while a RAID0 or RAID1 is used for the two 3 TB disks.

I'm presuming based on your other topic that you have figured this out already, but here is a relevant reply. When installing Windows on a system with multiple disks/arrays, I would recommend that you only have the OS disk/volume present at the time of installation. The reason for this is twofold: 1. Windows Setup will sometimes write boot data to another disk/volume than the one the OS is installed onto. The issue with this is that if the other volume is removed or has a problem, the OS won't boot. 2. Windows PE will assign disk numbers based on first-come first-served enumeration. Because all hardware is different, even between different systems with identical hardware, the system may make available disks in an uneven order. As such, there are situations where a card reader or RAID volume on a controller gets enumerated before the SATA ports, and this can cause an issue in some installation scenarios because Disk 0 ends up being something other than what you would think. I have never seen an ODD get Disk 0 designation, and have yet to see a NAND/NVMe in M2 slot be anything other than Disk 0... Because you cannot control enumeration of disks to Windows, the best practice is to remove the possibility of the incorrect device being detected as Disk 0. When using motherboard RAID in the scenario outlined above, the controller needs to be capable of creating a array with 2 or more member disks and 1 disk set to JBOD. Unfortunately, specs for RAID on motherboards rarely have a matrix of possible combinations documented, and there are definately instances of desktop motherboards being incapable of this configuration. The only way to know if it is capable is to attempt to do it, or find someone who has tried or has the board. For an Intel chipset board with Rapid Storage controller, you set the SATA mode to RAID. Then you would reboot and enter the RAID software and create 1 array using the two disks, and set the other disk as a JBOD member disk that is separate. If it allows this configuration, then you can either disable the array, or disconnect the disks physically, to install the OS. After the OS is installed, re-connect/enable the array disks and boot into the RAID setup to verify the array is healthy. Then boot into Windows, go into Disk Management and you'll be able to format the virtual disk that is detected.