Windows 10 Announced - Released 29-Jul-2015

Discussion in 'other software & services' started by ronjor, Sep 30, 2014.

  1. guest

    guest Guest

  2. roger_m

    roger_m Registered Member

    Joined:
    Jan 25, 2009
    Posts:
    8,627
    I ran a slightly longer version of command listed there, in PowerShell, and it made no difference. When I break Windows, I do I properly. But, it's only because I'm installing and uninstalling software all the time.
     
  3. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,592
    Location:
    U.S.A.
  4. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    Microsoft wants you to upgrade your PC.... are they joking?

    Many "old" PC's are perfectly capable of running Windows 10 despite OEM lack of hardware/firmware updates.

    For me... that's OK. I'm on the long-term service branch. I'll upgrade to the next refurbished computer when mine wears out.
     
  5. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    5,285
    I got offered the • Feature update to Windows 10, version 1703. in Windows Settings > Update & Security.

    However, after hanging at 75% for 13.5 hours, I decided to hard power off my Surface Book - "Force a shut down and restart your Surface" - https://www.microsoft.com/surface/e...shutdown-and-restart?os=windows-10&=undefined

    Luckily, my computer seems to have suffered no lingering problems, as a result of not being able to get the Creators Update which is now available on general release. I guess will wait until update bugs are ironed out.
     
  6. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    How old is your PC and does your OEM still support it? Under Microsoft's new policy, if it doesn't, Microsoft isn't required to enhance it with new feature updates.
     
  7. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    5,285
    @NormanF

    It was trying to get the update on a Surface Book that I purchased brand new, 13 months ago. It is a Microsoft product. Should not be that difficult!
     
  8. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    5,285
    This is what I got yesterday, when I started the update process:

    Code:
    2017-07-28 09:34:00: CommandLine: ["C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe" /ClassId 1e6a18f8-cca3-424c-a54d-65bb988ee652 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 /PreDownload /Update /ClientId 275547f8-8e2c-4c96-8f89-887c19b9f142 /CorrelationVector tFY71LmLSkyQZbdL.3.1.2]
    2017-07-28 09:34:00: Using default Box path
    2017-07-28 09:34:00: Deleting box result...
    2017-07-28 09:34:00: Checking cleanup registry value...
    2017-07-28 09:34:00: Checking SetupHost result value...
    2017-07-28 09:34:00: SetupHost result missing! Forcing full cleanup...
    2017-07-28 09:34:00: Performing cleanup level: [0x1]
    2017-07-28 09:34:00: Populating preservation paths...
    2017-07-28 09:34:00: Acquiring privileges...
    2017-07-28 09:34:00: Cleaning install folder...
    2017-07-28 09:34:00: CleanInstallFolder: Error = 0x80070003
    2017-07-28 09:34:00: PerformCleanup: Error = 0x80070003
    2017-07-28 09:34:00: Path cleanup failed! Error = 0x80070003
    2017-07-28 09:34:00: Cleaning working dir...
    2017-07-28 09:34:00: Cleaning alternate storage paths...
    2017-07-28 09:34:00: Cleaning MoSetup Volatile key...
    2017-07-28 09:34:00: Cleaning MoSetup RegBackup key...
    2017-07-28 09:34:00: Cleaning SetupWatson key...
    2017-07-28 09:34:00: Removing CorrelationVector registry value...
    2017-07-28 09:34:00: Removing cleanup registry value...
    2017-07-28 09:34:00: Creating path (with ACL): [C:\$WINDOWS.~BT]...
    2017-07-28 09:34:00: Creating path: [C:\$WINDOWS.~BT\Sources]...
    2017-07-28 09:34:00: Opening Box: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe]
    2017-07-28 09:34:00: Reading Box header...
    2017-07-28 09:34:00: Opening Box container: [0]...
    2017-07-28 09:34:00: Verifying Box container: [0]...
    2017-07-28 09:34:01: Reading Box container header: [0]...
    2017-07-28 09:34:01: Extracting Box container: [0]...
    2017-07-28 09:34:05: CUpdateScenarioCtrl::GenerateBoxHash: Calculating file hash...
    2017-07-28 09:34:05: CUpdateScenarioCtrl::populateWorkingDir: Storing file hash...
    2017-07-28 09:34:05: CUpdateScenarioCtrl::populateWorkingDir: File hash stored!
    2017-07-28 09:34:05: Searching for ESD files...
    2017-07-28 09:34:05: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] with command-line [/PreDownload /Update /Quiet  /progressCLSID 1e6a18f8-cca3-424c-a54d-65bb988ee652 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "tFY71LmLSkyQZbdL.3.1.2" ] in Session: [-1]
    2017-07-28 09:34:05: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] [/PreDownload /Update /Quiet  /progressCLSID 1e6a18f8-cca3-424c-a54d-65bb988ee652 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "tFY71LmLSkyQZbdL.3.1.2" ] from [C:\$WINDOWS.~BT\Sources]!
    2017-07-28 09:34:06: Waiting for process events...
    2017-07-28 09:35:20: Process exit code: [0x0]
    2017-07-28 09:35:20: LaunchProcessInSession returned: [0x0]
    2017-07-28 09:35:20: Checking cleanup registry value...
    2017-07-28 09:35:20: Checking SetupHost result value...
    2017-07-28 09:35:20: Skipping cleanup.
    2017-07-28 16:21:07: CommandLine: ["C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe" /ClassId 2e7838a1-bc6e-40e5-9c98-b07159423438 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 /Install /Update /ClientId 275547f8-8e2c-4c96-8f89-887c19b9f142 /CorrelationVector atvcZiQ0+U66GitP.3.1.2]
    2017-07-28 16:21:07: Using default Box path
    2017-07-28 16:21:07: Deleting box result...
    2017-07-28 16:21:07: Searching for ESD files...
    2017-07-28 16:21:08: Found ESD file: [15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd] [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd]
    2017-07-28 16:21:08: Checking cleanup registry value...
    2017-07-28 16:21:08: Checking SetupHost result value...
    2017-07-28 16:21:08: Skipping cleanup.
    2017-07-28 16:21:08: Opening Box: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe]
    2017-07-28 16:21:08: Reading Box header...
    2017-07-28 16:21:08: Execute file [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] exists: [TRUE]
    2017-07-28 16:21:08: Preserve working path: [Yes]
    2017-07-28 16:21:08: Opening Box: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe]
    2017-07-28 16:21:08: Reading Box header...
    2017-07-28 16:21:08: CUpdateScenarioCtrl::populateWorkingDir: Deleting Box hash if exists
    2017-07-28 16:21:08: Working file [C:\$WINDOWS.~BT\Sources\Install.esd] does not exist.
    2017-07-28 16:21:08: ESD source file: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd]
    2017-07-28 16:21:08: ESD target file: [C:\$WINDOWS.~BT\Sources\Install.esd]
    2017-07-28 16:21:08: Successfully hardlinked: [C:\$WINDOWS.~BT\Sources\Install.esd] -> [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd]
    2017-07-28 16:21:08: Searching for ESD files...
    2017-07-28 16:21:08: Found ESD file: [15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd] [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd]
    2017-07-28 16:21:08: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] with command-line [/Install /Update /Quiet  /InstallFile "C:\$WINDOWS.~BT\Sources\Install.esd" /progressCLSID 2e7838a1-bc6e-40e5-9c98-b07159423438 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "atvcZiQ0+U66GitP.3.1.2" /WUCachedFileName "15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd"] in Session: [-1]
    2017-07-28 16:21:08: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] [/Install /Update /Quiet  /InstallFile "C:\$WINDOWS.~BT\Sources\Install.esd" /progressCLSID 2e7838a1-bc6e-40e5-9c98-b07159423438 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "atvcZiQ0+U66GitP.3.1.2" /WUCachedFileName "15063.0.170710-1358.rs2_release_svc_refresh_CLIENTCombinedSL_RET_x64fre_en-us.esd"] from [C:\$WINDOWS.~BT\Sources]!
    2017-07-28 16:21:08: Waiting for process events...
    2017-07-28 16:49:12: Process exit code: [0x0]
    2017-07-28 16:49:12: LaunchProcessInSession returned: [0x0]
    2017-07-28 16:49:12: Checking cleanup registry value...
    2017-07-28 16:49:12: Checking SetupHost result value...
    2017-07-28 16:49:12: Skipping cleanup.
    2017-07-28 17:01:51: CommandLine: ["C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe" /ClassId 57456129-2022-456b-9a2f-593bfacac2d5 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 /Finalize /Update /ClientId 275547f8-8e2c-4c96-8f89-887c19b9f142 /CorrelationVector bxluIc2KtEePPk2q.7]
    2017-07-28 17:01:51: Using default Box path
    2017-07-28 17:01:51: Deleting box result...
    2017-07-28 17:01:51: Searching for ESD files...
    2017-07-28 17:01:51: Checking cleanup registry value...
    2017-07-28 17:01:51: Checking SetupHost result value...
    2017-07-28 17:01:51: Skipping cleanup.
    2017-07-28 17:01:51: Opening Box: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe]
    2017-07-28 17:01:51: Reading Box header...
    2017-07-28 17:01:51: Execute file [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] exists: [TRUE]
    2017-07-28 17:01:51: Preserve working path: [Yes]
    2017-07-28 17:01:51: Opening Box: [C:\WINDOWS\SoftwareDistribution\Download\82f617126cce53d385dc3a428fb4aa65\WindowsUpdateBox.exe]
    2017-07-28 17:01:51: Reading Box header...
    2017-07-28 17:01:51: CUpdateScenarioCtrl::populateWorkingDir: Deleting Box hash if exists
    2017-07-28 17:01:51: Working file [C:\$WINDOWS.~BT\Sources\Install.esd] does exist.
    2017-07-28 17:01:51: Searching for ESD files...
    2017-07-28 17:01:51: Launching process: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] with command-line [/Finalize /Update  /InstallFile "C:\$WINDOWS.~BT\Sources\Install.esd" /progressCLSID 57456129-2022-456b-9a2f-593bfacac2d5 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "bxluIc2KtEePPk2q.7" ] in Session: [-1]
    2017-07-28 17:01:51: Launching: [C:\$WINDOWS.~BT\Sources\SetupHost.Exe] [/Finalize /Update  /InstallFile "C:\$WINDOWS.~BT\Sources\Install.esd" /progressCLSID 57456129-2022-456b-9a2f-593bfacac2d5 /ReportId {A3BB26B0-CD4B-4C62-A966-B88A2F1DF381}.202 "/ClientId" "275547f8-8e2c-4c96-8f89-887c19b9f142" "/CorrelationVector" "bxluIc2KtEePPk2q.7" ] from [C:\$WINDOWS.~BT\Sources]!
    2017-07-28 17:01:51: Waiting for process events...
    2017-07-28 17:09:50: Process exit code: [0x0]
    2017-07-28 17:09:50: LaunchProcessInSession returned: [0x0]
    2017-07-28 17:09:50: Checking cleanup registry value...
    2017-07-28 17:09:50: Checking SetupHost result value...
    2017-07-28 17:09:50: Skipping cleanup.
     
    Last edited by a moderator: Jul 29, 2017
  9. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    Then it'll be under warranty. Until Microsoft stops supporting the hardware. You should be good to go with future feature updates.
     
  10. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    5,285
  11. roger_m

    roger_m Registered Member

    Joined:
    Jan 25, 2009
    Posts:
    8,627
    What to do about the 'Windows 10 is no longer supported on this PC' error.
     
  12. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    I wouldn't worry it. Lots of hardware has no OEM manufacturer support and it runs perfectly fine. My refurbished PC has all new parts.
    Does that mean Microsoft won't support refurbished hardware that is usually Microsoft-certified?

    Ridiculous!
     
  13. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    Yeah I saw that. Is that for W10 across the board? As in, will this effect LTSB as well?

    Need to make a decision for my job prior to rolling out W10. What a mess.
     
  14. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    It won't impact security updates. All the new Microsoft policy means is you won't be eligible to upgrade to a new Windows feature build if your hardware doesn't support it.

    Not an issue for me on LTSB since I don't receive new feature builds.
     
  15. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    I found an easy way to get rid of windows.old folder, It can be done via Settings/System/Storage, Click on This PC, Click on Temporary files. There you ll see the Previous version. Select it and delete. Amazing. Easy way for deleting the old folder. It took only a couple of minutes, smooth process. Hope this helps someone.

    Bo
     
  16. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    Hi Trooper. One thing I did before upgrading to version 1703 was to search what other people using same model of computer than me were saying after upgrading to Creators. I didnt have to go too far, the first link was from Dell, the manufacturer of my laptop, the link led me to a list of all Dell models hat have been tested with the Creators update and given the Go. Mine was listed, that gave me the confidence I needed to carry on the update manually, which was flawless.

    Bo
     
  17. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    I gotcha there. However if some of the new updates like the Fall Creators Update includes increased security like WD and EMET then that will kinda suck to not get it correct?

    I am currently testing a Lenovo T470P at my job. I am not a huge Lenovo fan but will see how it goes with my testing. Did a fresh install of W10 Ent X64 CU. Had to tweak the hell out of it to get it to run "ok". My older HP desktop at home runs W10 smoother. Crazy. I guess there is something to be said about the hardware not being up to snuff for future updates. To be honest, I don't care for much of the fluff that is included in Windows 10. At home, I only use the Windows Store for one app. UBlock for Edge which I rarely use as it is since i am a Chrome guy.

    We do not buy new hardware all the time so would like to get hopefully five years out of the new laptops that we get. So now its a matter of do I go with regular W10 Ent or say screw it, and go LTSB. In the end not sure what I will do. I can foresee a possible mixed environment of both. Time will tell.
     
  18. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    Thanks for this tip Bo. I have a few folks that I want to try this out on. Cheers!
     
  19. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    Hi Bo that is good to know. I may look into whatever hardware we end up thinking we are going to get and see what people say. Fall Creators Update is not too far off so we shall see. I have not had much time for testing of late due to other projects. Also had a few winners at work today get ransomware on their machines, fun!

    I am starting to think that we may need to get another AV at work, but that is a discussion for another thread.
     
  20. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    You are welcome, Trooper. I thought it was going to take a half an hour or so, or slow reboot applying changes, none of that happened. About 2 minutes, reboot was normal.

    Bo
     
  21. bo elam

    bo elam Registered Member

    Joined:
    Jun 15, 2010
    Posts:
    6,144
    Location:
    Nicaragua
    And the list. Other manufacturers are probably doing the same. That was perfect. And a plus for Dell.

    Bo
     
  22. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    That is awesome. I have a suspect or two I need to try this out on. :eek:
     
  23. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    Yeah I am going to be curious about the current Lenovo I am testing. I am sure it will be fine for the upcoming Fall Creators Update and all. Just do not know how many years of "feature" updates it will get. However if the new update is pretty tight with security and we just got Security related updates for awhile, I suppose I could live with that.

    Cheers!
     
  24. NormanF

    NormanF Registered Member

    Joined:
    Feb 20, 2009
    Posts:
    2,874
    I don't have an issue with my current security software; it already has the protections the upcoming Creators Update would provide.
    And I have no interest in the features Microsoft plans to unveil for it.
     
  25. Trooper

    Trooper Registered Member

    Joined:
    Jan 26, 2005
    Posts:
    5,507
    So wait. LTSB will have the WD improvements as well as the EMET being baked into the OS?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.