Tripredacus

RunOnce will execute under the current user context at logon. Without using something else to execute the file, you will need to invoke the rights within the .cmd file itself. There is the runas command, which you can specify a different user account to run a command with, but I believe you cannot script in a password. So it would only be useful for an account in the Administrators group (or custom group with appropriate permissions) that did not have a password on it. You should look into use Task Scheduler instead. There is more freedom to setting up the condition that way. You can say, when x user logs on, run this program as this other user.

You open Regedit. Expand HKEY_LOCAL_MACHINE and make sure it is selected on the left. Click File-> Load Hive. Browse to the other hard drive to a location \Windows\System32\Config. Select the file called SYSTEM (not system.log). It will ask for a name, call it "mount_system". Now everything in there from the left is the hive from the other hard drive. You make your changes. When you are done, it is very important that you select the loaded hive on the left "mount_system" and then File->Unload Hive. You can then close regedit. Always make sure to do this or there can be problems. Regarding the registry files, there is no main file. Loading the different hives under the different main groups (HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, etc) will load different things. If you do not know which to load, fine a relative key in your regular registry. If it is HKLM\Software, you load the SOFTWARE hive under HKLM. If it is HKLM\System, then you load the SYSTEM hive. And always make sure you give the loaded hive a name that indicates it what it is, and do not give it a name that matches an existing one. If you are concerned about goofing up, make a backup of the hives on the other drive first.

When they crash, do they create anything in the Application event log?

It is a strange thing, because the Windows store was created with the vision that filesystem access was not to be allowed at all... and now MS makes and OS where the only way to install "normal" desktop programs is through the store.

Another thing you can try is to use DISM to install the drivers into the online image, by copying the driver files onto the drive someplace, and setting it to run a .cmd on first boot. You could say, put it into Startup folder or another way. Then when the PC boots, DISM would install the drivers using /online option instead of /image. Or even you can trigger the silent install of the Intel USB3 setup.exe with the flag to reboot. EDIT: I forgot. There is a situation where you won't be able to use the new drivers if the old drivers exist. This effects certain Intel USB2/3 drivers whereas the INF is written in such a way that it will trigger the HwID check in the Driver Model to apply to the incorrect device. This happens because there is one Intel USB2 and 1 Intel USB3 device that have the same HwID, have different drivers (not interchangeable) and the INFs do not use full HwID to the SUBSYS and CC. If this is the case for you, the old drivers need to be removed. Two situations I've seen with these controllers is either USB does not work or bugcheck on boot.

I think it depends on how Origin goes about determining which OS it is installed/running on. If no one knows how it is done, then you'd need to see what Origin does on both a compatible and non-compatible system with a debugger or Process Monitor. But I think such a thing as simple as that would fall under the "reverse engineer" prohibition on 1.A. of the Origin EULA: http://eacom.s3.amazonaws.com/EULA_Origin_EN-ROW_PC_5.26.16.pdf So the only recourse would be to ask on an official EA or Origin forum.

Does this present a scenario where you had a perfectly working thing, then the software updated and now it says you can't use it?

Same as this: http://www.msfn.org/board/topic/174021-startisback-20/?page=37#comment-1138506

Well the question is how to add drivers to an existing installation, not what you have posted. Unless you know some trick to do a repair install/in-place upgrade to get the drivers to be used.

Well not specifically, just that MS is more inclined to base their decisions on the market sector in which they make the most money from. When it comes to the current market, with more people not buying new computers (except for work or school reasons) and increasingly filling that gap with tablets or phones, the retail desktop market has shrunken incredibly.

It may be possible to use DISM to add the driver, but I have not tried to do it with an offline HDD. It is designed to work with mount points. I think that you can do a test by getting the driver info. I suspect if that works, then you could add a driver. You need a WinPE3 or higher and the USB3 drivers in the PE image or on another USB device. And of course, your WinPE3 needs to have the USB3 support. It may be worthwhile to use a WinPE4-10 instead as they have better USB3 support built-in. If you do not have a WinPE to boot, you can use a Windows 8.1 or 10 Setup disk (no XML in it) and at the first screen use SHIFT+F10 to get the cmd. First you need to find which volume has your OS on it. You can use diskpart or the guess and test. For the example, I will pretend your OS is on drive N: Use this command to see if DISM will service this OS: DISM /IMAGE:N:\ /GET-DRIVERS If DISM gives the driver list, then the chances are better to add the drivers. But DISM may complain it is not an image. This is the command to add the driver (example) DISM /IMAGE:N:\ /ADD-DRIVER /DRIVER:d:\folder\iusb3xhc.inf DISM /IMAGE:N:\ /ADD-DRIVER /DRIVER:d:\folder\iusb3hub.inf When you add the Intel USB3 driver, if the driver for your device has the two files (whatever and hub) then you need to add both. Some Intel USB3 does not have the two files in the download package, so then it is ok to just add the one.

That is exactly what they are doing. Since the Windows 10 free upgrade happened and the sale of the Surface, it was the first time you could get an OS directly from Microsoft. It cut out the OEM and the normal OEM support. In the standard desktop space, OEM was king and retail was a very small number. But now with Windows 10, Microsoft is directly responsible for support. With this as their market aim, they would have no reason to want to support legacy OSes. All of their moves in the past few years are indications that they want to take a bigger chunk out of the OEM market. I also think that the CPU limitation doesn't have anything to do with the OEM or Retail channels, I bet that comes from the Enterprise channel instead.

Windows 8.1 is supposed to be affected also. It accompanies the complaints that Windows 8.1 is not end of support, yet MS will block updates to it if using these CPUs.

Yes, MSFN only hosts a support section for bigmuscle and Aeroglass. Although, some people have accidently donated to the forum to get an Aeroglass license...

Have you seen this section? http://www.msfn.org/board/forum/147-windows-updates-downloader/

It doesn't matter where they are from. You are not allowed to say such things to people here.

This forum is English only.

No one can tell you. Please read the forum rules.

I've gone into the about:config on many versions in the past 9 years and never saw this message.

I went into my about:config in Firefox and now see this message! It is 52.0.2. What is it talking about?

I also just remembered that I had this problem on Shiva for many years, but I had attributed it to having a custom splash screen. In a case where Windows would not boot, I would need to use escape key to cancel the splash screen. You may need a PS/2 keyboard for this. For me, that issue went away after changing the video card.

Well sure you can install Windows 7 onto it. We will have to see what people experience with it. I know there are some games that do need some updates, and I haven't found out if this CPU blocking thing only effects Windows Update, or effects updates themselves. For example, what if there is a game that needs an update that isn't available in the catalog? I think my example of H1Z1 requiring an update is not yet a good example because you can get those from MS with just your browser. I'm just thinking of the future and I think I'll let it play out.

Welcome to the MSFN!

The last thing on this log is [0015CABC] Initing hsflop.pdr Is it possible to disable the floppy drive in the BIOS? Have you also done the step-by-step confirmation boot? This sometimes helps.

It will be a long time for me to consider using that, since it is Windows 10 only. I will try to stay using Windows 7 as long as possible. When I have to make a new PC for Windows 10, I will be looking at Ryzen as a possibility.