Tripredacus

Sergiaws, might I recommend that when you create topics, make a mention of your vision situation. Since you do not have a lot of posts here, many members may not be aware of this and would hopefully save others from suggesting things us "seeing" people take for granted that may not be helpful to you.

My top 3 for best is Windows 7, XP then 98. I had to pick Windows 7 over XP because of the increased stability, in addition to a proper implementation of 64-bit over XP. For uptime considerations, it would be in that order also. My Win7 uptime numbers are already posted here. With XP I had always ran into memory or memory leak issues where you absolutely had to do a restart every now and then because I'd run out of free memory and the computer would get very slow. For Windows 98, my average uptime records were around 3 months before requiring a restart. For the worst, it was a battle between Windows ME and Windows 10. Windows ME was, at launch, a disaster mostly regarding drivers. However, on a properly tuned system, it was no different than Windows 98 SE at the worst. I can't fault Windows ME for being terrible when it was first released. In the same vein, I can't fault Vista for its launch either. Vista at launch wasn't terrible but it was terrible on low-end machines, of which most of the OEMs and retailers were selling Vista systems without enough RAM. They were selling XP systems with Vista, so 512 MB or 1 GB Vista RTM installs. Vista RTM worked decent with 4 GB RAM. It also had driver issues at launch, but everything since SP1 has been fine. Windows 10 gets the loss for the worst. The data collection is one aspect. The changing to UWP, using combination new and legacy UI and UI that (sometimes) did not work in certain scenarios such as in audit mode or with no internet access. The removal of service packs or integratable feature updates. The non-transparency of Windows versions on tools. Processor blocking per OS version. Windows update restarting the computer without input... Windows Update upgrading Windows 7 installations with no input.

If the process plays out every time the same and the bugcheck is generated at the same exact point, there may be a way to catch it without recording a video. At that reboot point, you can attempt to F8 the boot process to see if the boot menu can open. I don't remember if it is available at this point. If it is, then you can select the option to disable automatic restart on system failure, then choose to load Windows normally. Then it won't reset when it crashes and you can see what the error is. If that isn't possible, then the only other way I can think of is to edit the offline registry to enable this. Again, this would have to happen after the first reboot but before it can boot off the hard disk, you'd need to boot into a liveCD, or pull the HD to make it available on another machine to edit its registry. https://docs.microsoft.com/en-us/windows/client-management/system-failure-recovery-options When offline, it CurrentControlSet is not used, I believe it would be the 1 option.

You can try reading the other topics in this section. Many posts refer to this program to make things easier: https://www.bome.com/products/restorator

The INF is just installation instructions. If it shows as installed in Device Manager, then the installation is complete. You have a Code 10 on an installed driver, so there is no reason to think the INF failed. Did you install the update in the readme? KB943545. I'd run depends on the nvme.sys file. And it looks to install a service, does this service exist? And also, since I've never used non-English Windows, and do not know otherwise, are there things such as localised drivers? For example, is it a problem that the vars used in an INF are in English? Such as those in nvme_Service_Inst or the registry keys in msi_addreg or Parameters sections?

No, just speaking for personal experience. In personal life, all the computers I've made have existed for years. In professional life, getting to name computers now are serious business and names have to actually mean something and get reported into inventory system and to IT department. When at the old company, we would just let employees pick names and things were much more colorful back then. And while three of those computers from back then (ie. Uncle Socks) are still operational, nothing new gets to be as fun.

I sort of miss the days of using funny names for computers. Now everything is so serious or boring.

Outside of a software hiccup, there are two things that come to mind. 1. the ISP deleted the items on the server for whatever reason. 2. You had connected to this same email account using another client that was configured as POP3. By client, it can mean something like an email app on your phone, or perhaps even the webmail interface. Since the response you got from your ISP seems generic (although you did not provide an exact quote) I would imagine they did not actually verify the folder contents on the mail server. Having previous experience at ISP, I do know this is possible, but also that ISP did eventually phase this ability out for edge reps. In an IMAP situation, the response would be that what you see on your end is what is on the server. That can be confirmed however, by connecting to your mail account using another client set up as IMAP. Something like Thunderbird or another client that supports IMAP. Then you can verify that the folder is empty on the server, or perhaps it isn't actually empty but there is a problem with Outlook.

I did a compare to the three main WinPEs, the 14393 prod, 14393 local and the 17763 prod to figure out which drivers were in each and which were unique. It brought me back to the AMD drivers again. It would seem logical to do that after the end of the last post, however I had to check all of the drivers specifically because I was seeing the issue on non-AMD boards. The logic would be that Windows would not load an AMD storage driver on a non-AMD storage controller, right? I did a compare on the working and non-working driver set. 9.2.0.87 Working (all NVMe is Disk 0 on any controller) seems to be the newest, also tested 8.1.0.26 (which does not load the AMD driver onto the NVMe) 9.2.0.127 Not working (all NVMe is Disk 1 on any controller) Looking specifically at rcbottom.inf, the meat of the three drivers in my experience... (AMD RAID drivers have 3 infs, rcbottom, rccfg and rcraid) Ok some difference. My first thought it to look at that yellow line that I have clicked on. It has a Hardware ID of CC_010802. I did a recheck of the device properties again using new injections and only with the v17763 of WinPE using the 8.1.0.26 vs 9.2.0.127 drivers.... but that data is similar to what is in the end of the last post. I did a search and NirSoft's DevManView does not have any record of CC_010802. This is a compat? flag. But look at that driver data, you can see rcbottom.inf is loaded on a non-AMD vendor ID. AMD is VEN_1022, what is VEN_144D? It is Samsung. So rcbottom.inf is loaded on the physical hardware device for the NVMe, and then the NVMe (as a disk that can have volumes) is loaded under disk.inf. So here is the proof that Windows will load the AMD RAID driver onto a non-AMD controller because it is loading it for the storage device and not the controller. This is why an NVME can be seen as an AMD RAID device on non-AMD boards. Since we already know that DevManView won't show the whole slew of additional HwID or compat IDs that is actually tied to the device (from WMI), we can boot into the OS and use Device Manager. In this scenario, the PC has Windows 10 Pro but does not have the AMD drivers installed. Hence it appears as "Standard NVM Express Controller" in the Storage Controllers section. And there it is.

Great area, maybe some day I can live there.

Welcome to the MSFN!

What about Windows for Workgroups and Windows NT?

Getting somewhere, maybe.... This could have been a perfect storm, a situation where something else was changed besides the WinPE version and caused this issue to appear... The SK1200KP with a RAID 1 and spindle disks is the same in both WinPE versions. And then these results using 14393 on a PRIME B450M-A, since the NUC would not boot on that PE version. As seen here, it is the same as 17763! But certainly NVMes were definately being detected as disk 0... how could that be? Well I am testing with local PEs not production PEs. They are mostly the same, but obviously there is something different. Production PEs have always detected NVMe as Disk 0 like all other disk types, and it was only the "local" PE that would detect NVMe as Disk 1... UNTIL 17763 came out, and then either build detected an NVMe as Disk 1. Here is the NVMe on the B450M-A using the production PE v14393 where it is detected as Disk 0: I can't put the OCs into the production PE, so I can't run the wmic command. I can do this comparison between B450M-A with NVMe using Production 14393 (detected as disk 0) AMD-RAID Bottom Device Advanced Micro Devices, Inc. rcbottom SCSIAdapter PCI\VEN_144D&DEV_A802&SUBSYS_A801144D&REV_01\4&2074c63f&0&000E @System32\drivers\pci.sys,#65536;PCI bus %1, device %2, function %3;(8,0,0) 0x00000000 0x00000000 No Yes 5/14/2020 3:28:57 AM 5/14/2020 3:28:54 AM AMD-RAID Bottom Device 9.2.0.87 oem17.inf rcbottom_Inst.NT 9/21/2018 5/14/2020 3:28:53 AM AMD-RAID Controller [storport] Advanced Micro Devices, Inc. rcraid SCSIAdapter {54cb850d-a731-8590-0628-1992592bd448}\rcbottom\5&d1e0a6&0&131071 0x00000000 0x00000000 No Yes 5/14/2020 3:28:56 AM 5/14/2020 3:28:54 AM AMD-RAID Controller [storport] 9.2.0.87 oem19.inf rcraid_Inst 9/21/2018 5/14/2020 3:28:54 AM AMD-RAID Samsung SSD 950 SCSI Disk Device (Standard disk drives) disk DiskDrive SCSI\Disk&Ven_AMD-RAID&Prod_Samsung_SSD_950\6&10c8e623&0&080200 Bus Number 8, Target Id 2, LUN 0 0x00000060 0x00000000 No Yes 5/14/2020 3:28:57 AM 5/14/2020 3:28:57 AM N:\ Disk drive 10.0.14393.0 disk.inf disk_install.NT 6/21/2006 5/14/2020 3:28:56 AM and same but with local PE 14393 (detected as disk 1) AMD-RAID Bottom Device Advanced Micro Devices, Inc. rcbottom SCSIAdapter PCI\VEN_144D&DEV_A802&SUBSYS_A801144D&REV_01\4&2074c63f&0&000E @System32\drivers\pci.sys,#65536;PCI bus %1, device %2, function %3;(8,0,0) 0x00000000 0x00000000 No Yes 5/14/2020 3:39:23 AM 5/14/2020 3:39:22 AM AMD-RAID Bottom Device 9.2.0.127 oem11.inf rcbottom_Inst.NT 7/5/2019 5/14/2020 3:39:21 AM AMD-RAID Controller [storport] Advanced Micro Devices, Inc. rcraid SCSIAdapter {54cb850d-a731-8590-0628-1992592bd448}\rcbottom\5&d1e0a6&0&131071 0x00000000 0x00000000 No Yes 5/14/2020 3:39:22 AM 5/14/2020 3:39:22 AM AMD-RAID Controller [storport] 9.2.0.127 oem13.inf rcraid_Inst 7/5/2019 5/14/2020 3:39:22 AM AMD-RAID Samsung SSD 950 SCSI Disk Device (Standard disk drives) disk DiskDrive SCSI\Disk&Ven_AMD-RAID&Prod_Samsung_SSD_950\6&10c8e623&0&080200 Bus Number 8, Target Id 2, LUN 0 0x00000060 0x00000000 No Yes 5/14/2020 3:39:26 AM 5/14/2020 3:39:26 AM D:\ Disk drive 10.0.14393.0 disk.inf disk_install.NT 6/21/2006 5/14/2020 3:39:26 AM Any M.2 shows up as a RAID device on AMD boards, since it does not use the SATA controller, rather to be able to detect the disk you set NVME mode to RAID. A comparison of just the driver info (from Nirsoft's Devmanview) shows that two different RAID driver versions are being used. I could see that as being related to this issue happening on an AMD board, but not the Intel based boards. I will have to do some tests with those AMD drivers removed and see if it makes any difference.

The license requirements are for System Builders, integrators or OEMs. It related directly to fulfillment scenarios, aka selling the OS and a computer. That edition is designed not for retail sale, but for sale along with a full computer system. The OS has to be installed onto the hard drive, the COA put onto the case and the Pack itself included as an accessory. It is basically a restriction from selling the kit on its own in the Retail Channel. For an end user, you can use it to install to a computer without a problem. You do not need to use the OPK. For Windows 7, only OEMs were able to use the OPK and for System Builders and end users they could use the WAIK. All of that was replaced by the ADK. For those wondering, there is no mistique about the OPK, the only difference between it and the WAIK for Windows 7 (from what I can tell) is one .chm file that has additional license requirements for OEMs and System Builders. With the ADK, MS had made one kit for everyone and now the OEM specific documentation is paywalled and separate from the kit. A situation you may find is that storage or USB drivers are missing from the DVD. You would need to use the WAIK or ADK to add USB drivers into the image and then rebuild the install CD. But this process is not different than with other versions of Windows 7. If you do run into this USB issue, if your computer has PS2 ports you can get around it (instead of rebulding the DVD) by using PS2 Keyboard/mouse for the initial setup, install the USB drivers and then switch to your USB devices.

Welcome to the MSFN!

It is in IoT as well and has some issues. The UWF does not support full disk or volume. For example, it will not work properly if you are using single read-only disk. Look in the requirements for the feature, Pro is not there.

The Rules and Donate links in your signature are broken.

This is answered earlier in the thread. https://msfn.org/board/topic/181489-cpi-error-messages-other/?tab=comments#comment-1181520

You'd have to test if that works. I always run things through cmd.

Done

What I get from here: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825129(v=win.10)?redirectedfrom=MSDN Is that the enable/disable of optional packages inside of the Foundation Package must be done with an /apply-unattend, and that branch should be in Offline Servicing and not just Servicing branch. The image must then be installed using Setup, using your XML that does not have the offlineservicing object in it. Onedrive can be uninstalled, I usually do it with first run commands. Here is the cmd: c:\windows\syswow64\OneDriveSetup.exe /Uninstall

Another test, using RAID1 with 2 SATA disks. So with this, a RAID volume is detected the same as the NVMe, as being BusType 8. However it is Disk 0 and has a location path. So unfortunately, I cannot find a way to programmatically tell the difference NVMe and a RAID volume besides what seems to be checking location path. And I have a feeling that wouldn't be a valid method anyways because that field should have data in it. Other observations: the RAID vdisk doesn't have a valid Disk ID.

Here is an example of an XML that will hide those <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>040c:0000040c</InputLocale> <SystemLocale>fr-FR</SystemLocale> <UILanguage>fr-FR</UILanguage> <UserLocale>fr-FR</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Other</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> </OOBE> </component> </settings> The input locale is for France. Ref: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/default-input-locales-for-windows-language-packs

Corrected title, it is cpi not cip. This line item is only used by WSIM to automatically load a catalog when loading an answer file to be used against the mounted image. It is ignored by Setup and Sysprep. Nearly all of my answer files still retain the Vista Business CLG notation from when I first made an answer file with WSIM way back then. <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> The only reason to remove the offlineImage object is if you need to load your XML into WSIM and the XML was initially built using a different source image or catalog set. If the Catalog path is invalid or correct, WSIM will show an error. See if your XML validates against a stock install.wim without the things you added into it. If you see a fail during Setup, you first have to determine which phase it is. The two phases have existed in Windows Setup for many years, including XP. There is the phase where everything is done from the install media or from the WinPE RAMdisk, and the second phase are things being done from the install disk. Knowing which phase the error occurs is important because you then know where to find the log files. If on the disk phase, the log files will be in c:\windows\panther\ and c:\windows\panther\UnattendGC. Both would have a setupact.log. Note that setuperr.log is typically not helpful. WinPE phase log files: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files Disk phase log files: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs

If the car was from a cab company, the age of the car wouldn't have anything to do with any computers that the company owns.