Tripredacus

BCDboot, when used, writes two names by default. They are "Windows Boot Manager" and it writes it into the BCD file and into the NVRAM, which is what BootIce calls EFI Boot Entries. The different locations can show data in different places. In BCD, this is usually only visible if you have multiple boot entries and you have it set to show boot menu. The name of the OS "Windows Boot Manager" is the friendly name and you can use BCDEdit to change it to something nicer. The name in NVRAM is visible in a board's one-time boot menu, or in the boot order section in the "BIOS" setup. This is the name I need to change. This name can partially be changed with BootIce, using the manual steps. In this particular boot menu, it would appear as Windows Boot Manager [firmware device name] Whereas I can change the friendly name to anything, the "firmware device name" is basically what the motherboard shows the device it is sitting on as. Usually a hard drive model number, read during enumeration at POST. When Ghost was used, this entry in the boot menu would have just a name and no device. Doing it without Ghost will result in a boot entry similar to what is in the codebox. I will still look at the MBR of a disk after applying the Ghost image, perhaps that will be the way to solve this issue.

DD Release doesn't seem to work properly in WinPE. It just shows the copyright info in the CMD and doesn't return to a prompt or show error info, nor open a GUI of any sort. Bootice seems to work fine, however my requirements have totally changed. I no longer need to capture/write an MBR, instead now something to change EFI boot entries. Bootice can do this in the GUI but not in the cmdline. :\

What about this? http://www.winsetupfromusb.com/add-multiple-windows-nt6-vista-7-8-sources-ubuntu-usb-disk/

I may know of where this has shown up in television, not movies. In Star Trek: Deep Space Nine, there is an episode where Odo is with some people eating or drinking. And he makes a glass appear in his hand, and liquid in it. He can drink the liquid and refill the glass again at will. It is because he is a Founder / shapeshifter, his body is naturally a liquid. In this instance, the glass and the liquid are both part of his liquid body, so it is just for show and an attempt to appear more normal and fit in.

The usual culprit is that Windows only will look in the last dir it looked for a file, thus when installing anything that requires CD files, it constantly prompts for this. Files are in one of three places, so you constantly have to browse to the other folders to complete this operation. Windows 98 is the same way. Also the files it shows you it is looking for are sometimes (often?) either compressed or inside of a cab file. Unless you mean something else.

I'm working on a project to port an old deployment method to a new one and have run into an issue. The old method would put Windows install media in a single partition disk and boot from it. Ghost was used to put an MBR onto that disk. To eliminate Ghost I would need to recreate the situation without having the install media on the disk (I have an idea) or to get the MBR onto the disk using another method. Terabyte Unlimited's MBRWORK is 32bit only and does not work on modern WinPE. I have not tested their MBR.EXE yet but I am hoping that it will work. For that there is a 64bit binary available. What are some 64bit programs that can capture the MBR from a disk? Requirements are that the program be portable such as not require extra stuff like .net framework or whatever. If there is something different than MBR.EXE to apply MBR to a disk, in 64bit, same requirement but would require command line as well.

No links to whatever that ISO is.

Moved this honey pot back into the the Funny Farm.

UI should be second to the OS itself. That being said, MS should never have gotten around to making a new UI in Windows 8 or Windows 10.

I have read a couple people with Auzen card use this thing called X-Fi Mode Changer. It wasn't designed for your specific hardware or software. https://web.archive.org/web/20080721034415/http://www.freewebs.com/spectra9/xfmc.html

OK then you try to answer this weird question OP posted.

You'd have to look at the Effective Permissions tab to see exactly what rights it has.

I usually prefer to have the OS on a disk all by itself, and use separate disks for other things, rather than use partitions. For desktops anyways, for mobile computers I typically use them for specific purposes and generally have no use for large amount of programs and/or data storage.

Grant SYSTEM modify permissions on those keys.

I would guess, the server closes the connection, but the client doesn't check for the active connection and instead tries to continue issuing requests to it. I would suspect that the client would behave the same way with either the correct or incorrect OS. It might be conflicting information, typically a Socket Error is referring to network communication. A thread exit should give a different error... in the normal world. Since this error is coming from the software, we can't expect it to show exact information we would see from Windows. So the thought would be, what is different in the communication from the "working" and "non-working" installation? You'd have to do a Wireshark (or other network monitoring) capture on your interface during both operations, and compare them to see what might be different. You would think the request from the software would be different in each situation, as the remote server would not be able to make a determination about the client on its own. There is a problem with this approach however. Since it is a product under active support, the developers may not look kindly on this type of information being posted to the public internet.

Has there been any indication that Activation Servers have been disabled for any other products outside of Mac versions?

We can be assured that the laws of the USA (if not the world) are designed to aid current day business operations, and little care is given to "obsolete" products. I'm sure that Microsoft is aware there are sites all over the place with their old files on there and don't really do anything about it because it does not impact their current business. Certainly if we were talking about currently active/supported products it would be a different story. That isn't to say that it is a free pass on those types of things, because you don't get caught or are currrently ignored does not change the legality of it. But if Microsoft decided to go after such file repos, they would be well within their right to do so.

Please read the forum rules, including how to name topics.

I always found it is best to install Windows 10, especially the OOBE phase, with the computer disconnected from the internet.

Ok let's preface this with MAKE A BACKUP FIRST... which hopefully wouldn't be a required thing to say. First of all, when you are dealing with permissions, you can see an account name there, but it isn't a user account. The groups or other things (such as TrustedInstaller or System) are not user accounts nor groups. The groups solely exist elsewhere in the system. These references are Security Contexts. You have duplicates in your list because there are some that have an inheritance, and others that you (or whatever) have added manually. If you want to remove the inherited context rights, you have a few ways of doing it: 1. Remove them using the UI (may not stick) 2. Remove the permission propagation of child objects from the parent object itself. The Inherited From column is telling you which object that is. 3. You can uncheck the "Include Inheritable Permissions" box, which should remove all of the Security Contexts that have inherited permissions. However, before any of this is done, you need to make sure that SYSTEM still has the correct permissions, otherwise it can cause problems. Removing it using #2 or #3 could remove it from the list entirely, which is not advisable. If you know which account is trying to do this action that is being recorded into Event Viewer, verify it on the Effective Permissions tab.

1. No. 2. My process is to first find the hardware id (already done here) then look into the INFs to find exactly which driver to use. If it is "unknown to me hardware" then I would first test the driver with drvload in the PE itself. This would allow me to install the driver, then use Diskpart to immediately see if the disk is detected. This saves a lot of time when mounting and adding drivers to images. Then when I find the driver that allows diskpart to see the disk, then integrate that driver into the image.

I believe that the duplicates are normal, at least we can think that there is a limitation in the UI. As long as each have different inheritances, when a Security Context appears an additional time in the permissions list, with one inheritance and one "not inherited" it means that the "not inherited" permissions are in addition to the inherited. You can try, adding SYSTEM security context additionally to read, so that it too would have a "not inherited" listing. Then uncheck "include inheritable permissions from this object's parent" box. That should invalidate the already present inherited items. Account Unknown is likely an account that no longer exists on the system. Previous user account, or a temporary account created by a program during installation. When the account is removed from the system, it still can exist in permissions for objects, as seen here. Search the registry for that SID to see if you can determine what that account originally was or what created it. It is normal for the checkbox to uncheck after replacing. Another unusual UI design choice, it should have been a button rather than a checkbox I think.

Links would have to be hosted on Microsoft owned servers (not counting personal Onedrive folders) in order to be posted here.

Unpinned topic.

Storage driver seems to be VEN_8086&DEV_1C03, which shows mshdc.inf is loaded. Because it has this name (not oem) it is an inbox driver. These do not always work in all situations, usually needing an actual driver from the manufacturer (Intel in this case) to use disks in certain situations... such as mSATA/NVME or sometimes for some SSDs. Alas, Lunix saves the day... again. :p