Content Type
Profiles
Forums
Events
Everything posted by Tripredacus
-
Just created a classic Windows discord Server
Tripredacus replied to Pingunix's topic in Websites and Boards
This is already the right place. You need to contribute to this site before posting a link to your own. -
Installed what? If I were to guess, StartAll/IsBack related, but if you can confirm we can move this thread to that section or for a different one if this is the wrong place.
-
I would like to something about BCDBOOT
Tripredacus replied to Rbcc56's topic in Unattended Windows 10/11 Installation
If using Diskpart, you just make the FAT32 efi partition on a GPT disk. You don't set anything, so I'm guessing Windows (or bcdboot) just works with it as is. I think Diskpart will actually show an error message if you try to make a partition active on a GPT disk -
AMD has something that mimmicks a TPM. When I was building out configuration requirements for Windows 11, I initially left AMD out because those boards didn't have a TPM. But they have something else that Win11 recognizes as a TPM. It just has a different name on the spec sheets and probably does the same thing. I actually have no experience with either those or IME and I never had to field any questions about them, even from USG/Mil clients. The only motherboard feature like that I've had to deal with was Secure Boot. So to my knowledge, I never have known anyone who ever used a TPM for anything.
-
I would like to something about BCDBOOT
Tripredacus replied to Rbcc56's topic in Unattended Windows 10/11 Installation
You only use the /s or /f option on GPT disk partition layout. You cannot make a partition active on a GPT disk. -
Refresh still exists but it only works in specific circumstances. In my previous testing, refresh only can work if the WinRE components are the same exact build as the installed OS, but the installed OS build changes with updates. So Refresh can work in a system that doesn't update but that is not typical in a modern system. I also prefer that option as well, as it reminds me of the repair install you could do with XP. I don't understand the TPM requirement either, especially in regards to the retail market. Probably it was just easier to include an Enterprise feature in all editions and be done with it.
-
Captcha provider certificate error
Tripredacus replied to Tripredacus's topic in Site & Forum Issues
Working where? I don't know where that registration question comes from, whether it is a default in IPS or if Xper wrote it. -
I'm not necessarily sure about the error code that you had received, but there have been some instances where I have encountered a seemingly unsolveable boot error on Windows 10/11 like this without being able to fix it. My last resort solution is to image the OS partition and redeploy the entire system. It is time consuming but so far that ends up working.
-
Captcha provider certificate error
Tripredacus replied to Tripredacus's topic in Site & Forum Issues
Color is spelled correctly, at least in US English it is that way. The sentence has a grammar error but that's probably even better to deter bots, idk. Something is supposed to appear next to Security Check and it doesn't, not even for me. I suppose it could appear if you modify your browser settings to allow such content to appear but that shouldn't be a requirement, the forum's registration should work on stock (and "secure") browser settings. -
The captcha provider on the site/forum's registration form is showing a certificate error for some users. The result is that the captcha does not appear on the form so the registration process cannot complete. Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID for cap.js (remotely hosted by keycaptcha.com) Reported to me by a user but they did not provide system configuration. I verified using SRWare Iron 135.0.6850.0 on Windows 10 21H2.
-
Strange result when runnig batch script from Windows 10 schedule
Tripredacus replied to Sfor's topic in Windows 10
First the main difference is that you are actually executing the script in two different ways. Your manual methods are being run as an interactive user, likely in Session 1. Scheduler is likely running the script via a security context and also could be running in Session 0. If the presumption is that scheduler is running the script under a security context, I am not able to find out definitively why this type of behaviour may occur other than the obvious reason that a security context has different privileges than an interactive user. Wget may operate differently. There is a debug option you can try adding to your script like so: wget -t1 --debug http://localhost Also you can see about setting the scheduler to run it as a specific user. You can also try using a different tool to see if it behaves differently such as curl: curl --max-time 10 --retry 0 http://localhost -
Can what be done there? You want to run something in specialize pass?
-
winpeshl.ini order questions
Tripredacus replied to Rbcc56's topic in Unattended Windows 10/11 Installation
I would not recommending mounting a wim from inside of the WinPE, rather do these mount operations outside and build a custom boot.wim to use in your installation. -
You can change the letters like that, but you do it in the PE. Those letter assignments are temporary to that PE instance only and get reset everytime you boot. In my implementation I would run a diskpart script that would change the VOL C to VOL N every time WinPE booted. Then when I deployed a desktop OS, I would use a diskpart script to prepare Disk 1 and make the OS volume destination letter W. After imaging, when Windows booted, those drive letter assignments would be forgotten and the volumes re-enumerated. The result was that the OS volume would become C. Differences being, I used startnet.cmd for the initial WinPE set. Winpeshl is only used if you absolutely need to hide the cmd window when WinPE boots. I had only used winpeshl when building fully automated solutions like a burn-in program or hard disk recovery (if WinRE is not available). Also I did not use Setup because Setup does what it wants, instead I deployed using DISM so I can have full control of volume letters.
-
Topics merged
-
Name changed
-
Which version of Windows, or WinPE? The only real difference I know is that in the WinPE based on Win11, it won't assign a drive letter to an OS volume. This effects both ADK built WinPE as well as the PE that Setup uses from the install media. For which WinPE to use in general, I had typically stuck with whatever the most recent one that was needed for whatever purpose and typically that would work with previous versions of Windows but I would keep old builds around for legacy purposes. If you are referring to OS option on my profile card, that is just reflective of the computer I tend to post on the forum from. My regular internet usage computer is Win7 x64 but my gaming/streaming computer and my dev notebook run a Windows 10 equivalent, my security notebook runs Linux and I believe my imaging server runs Server 2019 Standard. I manage a Windows 11 computer also but you can only put 1 thing into the profile card. Not currently possible to circumvent enumeration. I don't even want to think about what would be required to change it. I don't think that it is impossible to do but it probably wouldn't be worth the effort unless you were really bored. Usually you just have to make the best with what you have and apply workarounds if you need to use them. Some of those workarounds that I have had to do in the past include: - always changing C volume to another letter on first boot into WinPE because it will assign USB drives and some unpopulated card readers to letter C which can interfere with some deployment scenarios. - having to make alternate deploy profiles for situations where WinPE enumerated Disk 0 as something other than the disk the OS is supposed to be deployed to. Methods of controlling drive letters include: - Using PXE to boot WinPE instead of from USB. - Using mapped network drives to be the places where OS images and applications would be stored.
-
WinPE reassigns all volume letters based on the order in which the volumes are enumerated. Typically it goes in ascending order from Volume 0, but there are some instances (on real hardware) where a volume (or disk) is not made available at the same time every time and those letters can change. Because of this, I usually recommend that only the disk that is meant to be imaged (or worked) is connected when booting to WinPE.
-
It seems to differ from Android version to version. I remember having a previous phone that I could set custom sound alerts for SMS for specific contacts, but then a later phone didn't have this option. There are apps that can do it but trying to find a simple clean app (especially these days) can be a real task. I had used apps to manage this before and they do work but not reliably. For example one phone I used an app for that, it would play the custom sound half the time and others it wouldn't before eventually it just stopped working. My current phone just has a default "Notification Sound" that is system wide, and the app I use for SMS doesn't have an option to use anything other than the system notification sound. I had a previous app that did but I never bothered to change it before it stopped letting me open it.
-
First of all, people typically don't respond well to demands to give answers or do all of the work for you. Second, it would be good for you to explain how exactly you are designing your deployment workflow. Since you mention using both XML types (one for install, one for sysprep) it leads me to believe that you are making a deployment image. I have never personally found it useful to add any scripting into Autounattend.xml to begin with because that is only for creating the base installation. It is different if you also intend to use it for a recovery scenario, but in that case you wouldn't end up using two XML files anyways. I've only operated in a structured deployment environment where the need for determining drive letters or scanning for volumes wasn't needed. Nevertheless, for post deployment customizations I would use FirstLogonCommands in the oobeSystem phase to specify a single .cmd file. Then within that .cmd file that would be where I would include the scripts. But as I said, I never would need to have to scan for volumes and if I did have to do something like that, I would likely end up writing a program to handle that type of task so that I can leverage WMI and Win32 API calls.
-
Windows Replacing the 'Blue Screen of Death'
Tripredacus replied to Monroe's topic in Technology News
Bring back the Azure Screen of Indifference! Wasn't there a red screen of death in a Vista beta? -
I don't really care about it personally. I have to deal with it here and the other thing I mentioned but MSFN is based in Europe so we have to follow those rules. If MSFN wasn't an official fallback location that line wouldn't be there. It is only because MSFN has many EU members that I mention it. It seems standard practice that US sites don't care about those things, even if the forum software supports it.