Tripredacus

You didn't. I used an example and you make it sound like that is all this PC is used for. In fact, I have found this PC has been on without a restart for nearly a year prior to stopping to use it to play games.

Well when I am not home, it doesn't need to be doing anything. How are we supposed to compare computers? Do I need to post a list of installed programs? Why would it matter? No it isn't just being used for reminders. What is it that your computer is doing when you are not home?

I see my install as Feb 20, 2010. It is 32bit. It is my main computer as far as productivity goes. I no longer play games on it, made a new computer for that and it is 64bit. It is on 24/7 as long as there is power. I use it as a way to communicate with myself by way of AOL. Using 2 accounts I can IM myself things to look at later, send reminders to do things. Also able to verify the status of things in my home... basically if my other AOL account is signed in, it means I have power and internet. Of course, I realise that every computer is different and everyone uses them differently. I often see people say things like how Windows will corrupt itself, or get slow after too much time and you need to reinstall. This simply isn't true. All it shows is that a person is not using their computer properly, and are in a repeating pattern of this bad behaviour which results in their needing to reinstall often. People also often tend to ignore the little things their OS may do, the warning signs of something coming down the road. And they do this until the thing becomes unusable. If you ever helped a friend or family with their computer, usually you find they wait until the thing is totally broken before they do something about it. In my experience, my most common cause for an issue is hardware related. If I am to install a program and it does not work properly, or causes some problem and I cannot find a way to resolve it, I don't use it. I only keep things installed that have some use. I do not update unless it is required for operation (and no alternative can be found) or for a security related issue that can actually impact me personally. I do not use websites or portions of websites that require me to sacrifice my browser's security (and thus my OS) ever, and I use different browsers for different services and purposes. That is probably the best way I can put it.

I've had no problems. I run a Win7 Pro x86 with no antivirus (MSSE barely counts) daily with no major issues or need for reinstall or system restore. Of course, on all my PCs my browsers run with scripting disabled by default. Windows 8 and 10 are designed to be online. Even the Embedded versions need an internet connection at some point.

Welcome to the MSFN!

Was it ever tested to find out whether or not all installs of Office 365 on Windows 7 does this?

What happens for me, is that the clicking the next page bring the page back to the top, then refreshes the page automatically.

This board uses ECC unbuffered memory. Make sure the RAM you are using is of this type. Google Cache manual (no pictures) If you are ready to throw away a board, there is no harm experimenting on it. LGA771 based server boards and CPUs are still good if you need to replace on the cheap.

Xper's annoucement topic, which was made maybe 20 hours ago, shows 2 different times. It says the topic was posted 6 hours ago, and that it was started 31 minutes ago. It cannot be the case, as my like on the post is retained and I had done that 15 hours ago. Mcinwwl's post here: http://www.msfn.org/board/topic/173752-how-to-avoid-being-upgraded-to-win-10-against-your-will/?page=22#comment-1129300 Still says it was posted September 14th. Now that it is the 14th here, it should say x hours ago, not showing today's date. Anyways, weird date issues aside, everything seems ok so far.

For Windows 7/Server 2012/R2 (presumably 2016 also) sel disk 0 clean convert gpt create part efi size=100 format quick fs=fat32 label="System" assign letter=s create part msr size=128 create part pri format quick fs=ntfs label="Windows" assign letter=w exit For Windows 10 sel disk 0 clean convert gpt create part efi size=260 format quick fs=fat32 label="System" assign letter="s" create part msr size=16 create part pri shrink minimum=500 format quick fs=ntfs label="Windows" assign letter="w" create part pri format quick fs=ntfs label="Recovery" assign letter="r" set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 exit Some things to note. These are designed for diskpart from Windows 10 ADK. Some older versions of diskpart would not auto-select a newly created partition. In case you are using an older diskpart, you would need to add "sel part x" between the "create" and "format" commands. So in the Win10 script, it would be sel part 1, 3, 4.

We apparently had a rollback and lost some posts. If you didn't see the two scripts I posted yesterday, I can post them again.

I found some post dates have tomorrow's date. If I reply to the thread, the earlier post gets put after mine. Last seen date is also wrong on user profiles. The posts with tomorrow's date all seem to be from earlier today. Current posts seem to have the correct date on them.

Well cumulative updates are always a problem. Consider a situation where you need to have some update to fix a security issue you know you need, but another update is known to break something else you need.

It is for Windows 8 OS. 1. I have never seen stock Windows 7 recovery work on GPT disk. 2. Windows 10 does not have a recovery image. I can post you my EFI diskpart scripts for Win7 and Win10 on monday if you want.

It sounds like your OS is running in a RAMDISK, RAM Overlay or Write Filter. It is difficult to say anything really, your installation is not common. Perhaps you can tell us how you made this install?

Is this the correct page? http://www.glass8.eu/sign/in

Another change I found in 1607. SmartScreen now takes over the place of the old security dialog when trying to open programs, it will complain that it cannot access the internet (if it cannot access the internet) to verify an application that you try to install. I tried with an MSI file. You can still just run it anyways.

DISM doesn't care regarding to /apply-image option, as long as it is a WIM file. Where the compatibility issues lie is with servicing images, which wouldn't be done in a PE anyways. Those include DISM from Win7 AIK can't service a Vista image and vice-versa. DISM for Win10 is needed for adding most signed drivers to Win10 images. You are correct, when you make a WinPE you don't have to copy in the imaging tools portion. It saves that short step because DISM is built-in. As far as advantages go... idk. MS deprecated imagex.exe in WinPE 3, even if it has been available in the current ADK. The only thing I ever use it for is the /info option but not while in a PE.

Why even use Imagex.exe at all. Use DISM for both.

Regarding icons. There seems one change in 1607 where Windows is using a different icon index to use to display when on the desktop. It is using one of the smaller sized icons. If you ever made a program or used a resource editor, applications have a few different sized icons in there. So now on 1607, my icon is pixelated, but in 1511 and previous it was fine. It doesn't bother me so much because my program is for internal use aka it doesn't have to be pretty. But I have already received reports of the icon looking wrong on the new OS.

You should never use /upk except on an image you make from the ground up or know exactly what you are doing. The install key needs to be in the OS and the Activation key in the BIOS. BUT now you took out the install key from the OS, we can't tell you the key to put back in because it is confidential. If you have 2 computers activated using the same activation key, eventually one will enter notification. If you want to use the key from the BIOS to activate a system, use slmgr -ipk to input it. Then use -ato to activate online. If -ato gives you an error, you can try phoning in the activation. When you are doing this work on your own, or under the name of a company, you want to do it the right way. Most of the limitations that are put into place are policy restrictions. For example the fact where no one has the "right to re-image" or modify or make an image using an OEM pre-installed OS or recovery DVD. MS does have auditors and they do catch companies mis-using Windows and they get fined for it. So if you are not an OEM, then you should not be using custom OEM images in a repair situation.

Do not put all that into startnet.cmd. Make your own .cmd and call it within startnet.cmd. Change your diskpart script to make your destination volume a different letter than C.

It shouldn't do anything with the key in the BIOS. Windows edition matters, but also the source. You would only use the Windows 8 OS provided by the OEM to activate with the key in the BIOS. This OS does not ask for a key to be input. When installed, it will read from the BIOS automatically and then activate if an internet connection is present. The key in the BIOS is only designed to activate in this way. If you run slmgr -ato what does it say?

Use this Diskpart script: sel disk 0 clean convert gpt create part efi size=100 format quick fs=fat32 label="System" assign letter=s create part msr size=128 create part pri format quick fs=ntfs label="Windows" assign letter=c exit Apply your OS image to C. BCDboot command: bcdboot c:\windows /s s: /f uefi As above, drive letter for OS volume is C, you can make it W if you want, it doesn't matter. Just make sure the bcdboot command matches. The PE you use to do this deployment must be booted in UEFI mode. WinPE should be v5, otherwise you may need to add select part to your diskpart script.

Activation is not stored in the BIOS exactly, but similarly this would only be true if you had purchased a computer from an OEM and it came with Windows 10 installed on it.