Tripredacus

No.

I cannot be hacked because I RAM Overlay.

It depends on the drivers and how they are installed. Some drivers that require installation from a program may have OS checks in the program itself. The drivers themselves may have a compatibillity check in them, which would normally cause a setup to work but for Windows to reject the install. That would be found in the .inf file. But even if the INF does allow installation on Windows 8.1, the binaries may require Windows 10 versions of some files to work. The first step would be to post the hardware IDs of the devices you want to find drivers for. You may be able to find some in the MS Update Catalog, but know that they do not always have the correct OS information on that site. Meaning: They may show a driver for Windows 8 but it only works in Windows 10. You won't know until you try it.

Welcome to the MSFN!

Every Lite-On DVD drive I've used has the same issue as in the op. I just either use a paper clip or when I get fed up will replace the drive.

Third name in 30 days? This isn't a username changing simulator.

In my recent uses of Linux, it just works. But that is presuming I am using it as-is. My current install, everything worked without me having to do anything. That includes LAN, WLAN, mullti-mon, etc. What I wasn't aware of was how to install new programs. I had wanted to install Zoom onto it, and there is a Linux download, but it was some file that wasn't associated with any other program and I had no idea what to do with it.

There are the drivers for your processor graphics: https://downloadcenter.intel.com/download/21414/

That is the identifier for NT Authority context, which is stored in C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT. So you would need to mount that hive and add keys to it, then unmount.

Using DISM /online /add-package options https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options

We have an entire sub-forum for this already https://msfn.org/board/forum/24-windows-desktops-screenshots/

For whichever situation is applicable to you, post the make/model of: - motherboard + cpu (if using onboard video) - notebook (or notebook + cpu if using whitebook) - video card

This is not the expected behaviour. There is no functional difference between LTSC and say... Enterprise or even a retail SKU. There is something wrong with your installation if this type of thing is happening to you.

I show for you: 1.8 MB of 1.95 MB allowance for attachments. You can view your attachments here: https://msfn.org/board/attachments/

No.

I've actually seen this myself. When this happens, you can find in event viewer that Steam.exe vetoes the Shutdown request! I just make sure to exit Steam before shutting down.

Windows 10 is not full UEFI, neither was Windows 8. Windows only has an EFI bootloader using the same basic methods as Vista and Windows 7. The OS itself is still "legacy" (hence why it still has stuff from XP in it) and only has the ability to hook into UEFI features. To put it this way, if Windows 10 was actually an EFI application, it would be impossible to image/convert a Windows partition between EFI/GPT and BIOS/MBR disks and be able to get it to boot. You can do that now because when you do this type of conversion, you only need to change the bootloader to get the OS to boot.

This site is almost 20 years old, it is not that surprising. There are many accounts that I have made on other forums and not gone back to. There is not enough time in the day to be posting on forums, especially as you get older. Times change and people do different things.

Why don't you put in the solution that you found?

What the designers at MS want to do, and then what the developers are told to do, as well as what the execs resign themselves to be able to do (market-wise) are totally different things. What I get from what little birdies tell me is that a plan was put into motion to do a thing, then was "rolled back" at least partially and then bandaids are put in along the way. So in this instance, I fully believe that GDI/+ was intended to be removed, a decision that came about from the planning stages of UEFI 2.3.1, and work on the new system almost certainly was started and does exist within the OS. But the decision to fully cut out GDI was rescinded and they left a compatibility layer in place.

This isn't a blog.

I use whatever OS is required for the software I want or have to run. If I have a Win7 computer and the software works on that, then that is what I will use. Of course I have a Windows 10 computer at the office and also on one of my personal notebooks, so if I really did need it for something I can use those. But a software requiring Windows 10 must be really something I care to use before I'd consider replacing the OS on one of my main systems.

GDI was considered a "legacy" product since around when Windows 8 came about. Even in the lead up to Windows 8, it was in their pre-release plan to get rid of GDI entirely and replace it with some other thing which I forgot the name. Their focus is now currently on DirectxD related APIs and it does not surprise me in the least that something like GDI has been mostly left to rot away.

I haven't run into anything but I do not use a lot of the options anyways. The surefire way to know would be to create an CLG on an 1809 image, and XML with everything added. Then mount a current build image and apply the XML to it and see what the validator says. I do know that MS doesn't document everything, such as when they made XML objects case sensitive.