Tripredacus

What instructions are you following? PEImg is for Vista times and isn't used anymore. DISM for everything!

Artarga, it is clear that using HOSTS file in Windows 10 is not valid as there are a few documented instances where the file is not even used for resolving domains.

Not knowing which edition you have, but have you looked into AppLocker?

Getting tired of you posting what you did on other forums.

Did you add the registry entry anyways? Also look here: http://www.msfn.org/board/index.php?act=findpost&pid=1097746

I see this often. I just keep doing restarts and check updates until it works.

Its not really news, but I guess no one wrote an article about it yet.

Are you settings correct? See here about the BLASTER var: http://www.rinkworks.com/apogee/s/6.4.2.shtml That is specifically for DOS so you must not be using Doom95 there. For Doom95, a Windows application, it uses DirectSound.

Does 3dmark2000 fit the bill? Look here: http://www.vogons.org/viewtopic.php?t=33579#p406996

You can try running this in a .cmd: wmic useraccount where "name='UserName'" set PasswordRequired=falseThe only way I have made a deployment where an account has no password is to pre-create it in Audit Mode.

I have my PCs also set to notify only, but only because that is the lowest setting you can have that won't disable MSSE. I am considering finding a different lightweight antivirus and then disabling Windows Update completely.

Well good thing MS didn't do a "Show us the great things you did" social campaign for Windows 10. I would just submit a pic of my blocked updates.

I believe the WS folder appears after you do the upgrade.

Have you been looking at any outgoing UDP connections as well?

Ok, there is no official word that I am aware of concerning the re-imaging rights of the ISO from the Media Creation Tool. We do know it initially comes as a converted ESD file and that DISM can't mount it. We also know some people have done deploy/capture or use N(T?)Lite to convert the file so DISM can mount it. OEM/FPP editions of Windows 10 do not have the ESD type install.wim, which leads me to believe that Microsoft does not want the Free Upgrade ISO to be used to make an image. And there are multiple people on Technet reporting that using this ISO with an XML that certain things in Specialize pass are ignored, the primary one being ComputerName. I can do 1 test to see if OEM/SB Windows 10 uses the ComputerName object in the XML. Update It does not work with OEM System Builder. I deployed my image to Audit Mode, then sysprep /reboot /oobe /unattend using this XML: <?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" 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"> <SetupUILanguage> <UILanguage>en-us</UILanguage> </SetupUILanguage> <InputLocale>en-us</InputLocale> <UILanguage>en-us</UILanguage> <SystemLocale>en-us</SystemLocale> <UILanguageFallback>en-us</UILanguageFallback> <UserLocale>en-us</UserLocale> </component> </settings> <settings pass="specialize"> <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"> <ComputerName>NameTest</ComputerName> <TimeZone>Pacific Standard Time</TimeZone> </component> </settings> <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>0409:00000409</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-us</UserLocale> </component> </settings> <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows vista business.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend> It did not rename the computer.

Welcome to the MSFN!

Are you saying you validated Mavericks' XML in WSIM or your own? If you deploy with DISM, it will use the XML in the WIM. If you deploy with Setup, it will use the XML in the root, unless otherwise specified.

Ok. I do not yet have the new WSIM installed and have not done any XML for a deployment like that yet, so I can't test right now. Is the behaviour different from before? Before you had a hang issue, is it still this way or is it that Specialize is ignored? I have read some posts where people complain that ComputerName isn't being applied... but also wonder about your source. Are you trying to use the ISO from the Media Creation Tool?

AMD looks to have won this round of DirectX compliance. Read the article here: http://www.guru3d.com/news-story/nvidia-wanted-oxide-dev-dx12-benchmark-to-disable-certain-settings.html

It is clear from your cmd output. You map to a share called Apps on the 10. ip address. Then you execute a command in J:\Apps. That is where your second Apps folder comes from. Change that line to this: start /wait J:\7-Zip\x86\7z1506.exe /S

You can remove packages with DISM but it won't save you any space. You need to export your image to clear out the files that aren't actually being used.

Did you try having WSIM validate against your install.wim? Maybe a setting has changed.

Disabling the time service (and having the wrong date/time for your selected time zone) should effectively disable Windows Update. If it works the same as previous versions of Windows that is, although it would generate errors because of it in Event Viewer.

Thanks for your feedback. It is one reason why I've been holding off on KB3081444. So, not only removing previous cumulative updates will be required, but probably exporting/cleaning up the image to keep the size down.

Topic split from here: http://www.msfn.org/board/topic/173752-how-to-avoid-being-upgraded-to-win-10-against-your-will/ I am not surprised that MS wouldn't want to upgrade everyone and everything... they are putting themself at a big risk as it is. They are saying they will upgrade your Windows PC for free and support it for the life of the product. Limiting upgrades based on devices is actually a good idea, since you could install Windows on hardware of any age, presuming it technically works. Consider the fact that (not counting those with no driver support for critical devices) Microsoft is taking over direct support of computers that are likely out of warranty or even obsolete. Be aware that the upgrade is going to remove your ability to dual boot and you'll have to redo it.