Tripredacus

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.

So no Windows Embedded 7 or 8.1 on those platforms either.

That's sad to hear. Do you think you might end up releasing it or the source under GPL or something similar, so that people may continue to use it? Or, have you considered finding another person or party to take the project over from you? Just some ideas.

It is difficult to help someone troubleshoot a network issue if they do not post more information. You are working with the private side of the network, you may be using 10.x.x.x or 192.x.x.x. It would be nice to be able to see a simple network map. What router is it? Are you using an IP address in the same subnet that the router hands out in DHCP but not within the scope?

I can say that the ones that look like donuts (doughnut) are the wait/busy cursor. In previous OS it was an hourglass or "egg timer" as I've heard it called. I'm not sure about the other two you outlined, but the small-to-large circle progression makes me think of touchscreen cursor.

A biometric pattern cannot be changed on YOU (except through injury) but it can be changed in the system. Nearly all articles relating to authentication security take aim at the wrong thing. It isn't the username or password that is the problem, it is the authentication system. It doesn't matter what you use for your password is if someone can get into the system using another method besides standard login. There is always more than 1 door.

Yes you are correct. While it should be so simple as what Dencorso said, in reality the post editor does not behave that way. It should work like the one on the Technet forum, but even it shares other quirks such as trying to make everything you typed into a link. But even so, it seems the text as it appears in the editor box is fine, keeping in single space. Yet the text as it appears is somewhere between single spaced and double spaced (shift+enter vs enter).

I doubt this would happen.

http://www.geek.com/apps/this-must-be-the-biggest-windows-blue-screen-of-death-ever-seen-1667359/

TVs in the garbage. ;_;

Windows 10 does not remove the pre-existing partitions when an upgrade is done, it just removes the BCD entries to be able to boot it. The 30 days thing, is only relating to the uninstall option that appears in the Recovery page on Windows 10. A user who had upgraded to Windows 10 at the last minute, then got the anniversary update, would have seen that option disappear anyways. There was a case with Windows 8.1 update from 8.0, on MBR disk, it would over-write the recovery "boot" partition, but it would leave the recovery image partition alone. In EFI scenario, the update would make a second recovery partition instead, leaving both original recovery partitions alone.