Tripredacus

Due to the nature of the subject, it shouldn't be a surprise that no one has responded to this thread in 11 years. While I have worked for a company that ran this type of software on employee PCs, they were open about it being there. I never understand companies that treat their employees like children and have to hide things from them.

WIMs operate similarly but you can rebuild them with imagex. Is there a similar tool or method to rebuild RAR or 7ZIP files?

If it is in the WinPE phase, then this can happen. The boot image has a RAM requirement. For Vista RTM/WinPE2 x86, it was generally 512MB and x64 was 1GB. There are some situations where the amount of available RAM may be less than what is physically in the system. Some may be allocated to onboard hardware such as mass storage or video controller. Other RAM issues I've seen with Vista's PE is where the RAM is faulty or failing, or in some rare cases the timings are wrong (relabelled memory) or (on certain hardware) the timings are not matched. If this was during the HDD boot phase (2nd stage) then RAM wouldn't be so much of an issue.

There was some registry hack that could be done in the Preview versions that would allow you to change the edition from Ultimate to Pro or Home Premium (RTM i guess). It was basically a way to trick Setup into allowing an in-place upgrade to be permitted. I can definately think of valid reasons for doing this type of thing, but at a risk of potential system instability.

I never really used that site. Maybe once or twice during XP times. Wasn't that one based on user submission? Hopefully it comes back, seems like a waste if they just removed it after all the work done with it.

Oh yes, I have previously used that method before. It would just be a pain to have to do a lot of work just for one program.

Then tell me how a user can, but cannot "go down edition" according to you, downgrade from W7U to W7HP?! There is a difference between what is designed/intended and what is physically/technically possible.

Can you post a link to the thread you found?

I ran into a situation where I need to use a DOS program but it will not run if himem.sys is loaded. Unfortunately, I (likely) have other things that require it. This is my config.sys [COMMON]DOS=HIGHSHELL=C:\COMMAND.COM C:\ /P /E:512DEVICE=himem.sysdevice=ifshlp.sysIs it possible, via .bat, to unload himem.sys so that the program can run if it is selected?

The main page for it just redirects to the generic Windows page. This error page shows it is temporarily unavailable. https://www.microsoft.com/en-us/windows/compatibility/Error

Windows isn't designed to go down edition, but only up edition.

Well the summary of the article states that versions prior to Windows 2000 wouldn't be vulnerable. In fact, the security issue was found with the TrueCrypt driver in VeraCrypt on Windows 10.

What were you installing it from?

It is hard to tell what your exact question is.

Yes we are aware.

Office 2010 uses an XML or MSP file. https://technet.microsoft.com/en-us/library/ee656738(v=office.14).aspx

The link that was originally posted contained files that are not allowed for redistribution. We do not operate in the gray area here.

Windows 8 has "Core" and Pro versions. There was confusion along with this because "Windows 8 Core" was the internal name for Windows 8. There are these two consumer editions: Windows 8/8.1 (Windows 7 Home Premium replacement) Windows 8/8.1 Pro (Windows 7 Pro replacement) For Windows 10, they decided to call the prior "Core" product Home. So you have these editions: Windows 10 Home Windows 10 Pro

Note: OP is likely tandem spammer, however can't always be sure.

Which redistributable download contains memtest.exe? I can't find one and Microsoft might not allow it.

Redistribution of Windows files is not permitted. Its cool that someone figured it out tho. What is allowed is a tutorial of how to do it yourself.

Look for tasks scheduled to run on user logon.

Trusted Installer runs under the security context of System. http://www.msfn.org/board/topic/174336-question-user-accounts/#entry1106603 As an example, Trusted Installer has the ability to take ownership of things because it is a child to System. But System is not a full account as it doesn't have the natural ability to run in the interactive user session. This is why you can't really use it as a true user account. I recall in Vista there was some trick that you could get Windows to log on in Session 1 as System (it had something to do with cmd and screensavers) but the OS was pretty much unusable. If you look at the history of Windows development, you see it is mostly a bunch of add-ons. The system account is very old and Trusted Installer is relatively recent by comparison. It would be easier to give Trusted Installer certain priveledges rather than rewriting everything in Windows to no longer use System.

dragosr on twitter shared this powershell script. Debloat-Windows10.ps1 (Windows 10 Enterprise N LTSB) http://pastebin.com/Uk9BRrRJ

Considering the mitigating factor: You may not even need to apply it at all. https://technet.microsoft.com/library/security/MS15-111