From fee9d7fb66e1036c2295142d8a45e17e6404f568 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 12:09:45 -0700 Subject: [PATCH 01/13] minor release --- windows/deployment/images/download.png | Bin 0 -> 4561 bytes windows/deployment/upgrade/setupdiag.md | 15 ++++++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) create mode 100644 windows/deployment/images/download.png diff --git a/windows/deployment/images/download.png b/windows/deployment/images/download.png new file mode 100644 index 0000000000000000000000000000000000000000..df12d22f7ad2540eb9cfc16370cef346d7891cf5 GIT binary patch literal 4561 zcmV;?5iahDP)Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf5oSq5K~#8N?OO?W z6-5%R+zGi85+H=!37{wjMLZBh!BrQZd5MAnJl5h~TOS z2p)K>h+J}q1VRYmOhWGa*#GaDc?^%2kZ3UZ-1$F;m)FzNU0qdwRdvtP$?NIlnv#kt z5ho|HV8O!ghqL}^!GeWGf<-C|78)51CskFAc3H4s!66z(Dv&8A#9g9sS;Vqn!7&;} zs*)=C{O)l1=Kctg;wrt-f&~j^G>lY8PNkJK>at+Lf@3s%PX#{J@E;2nEI35NNoB!; zg*su8sv$5=K5NcnrmoiK;OCzm)Z_WoWfP(Kkc!GJtvd56uNJAm)f^NLNB8q~5r16H z&Q9k?CJ@Qf-C51S&svGacIt+QMZ8LIQBTbQl*??xGTnyuYoY!qdpSOvi|mbrhW$*b zpi;Jsj}tF`1HY&QiD+HUXhJwe^yFFY}kB+w(z01gyq#X81?S)C7qOcGnwDqYAQ*`t-QW z`8rDr6d+j5tWN6Q&?QG?(Z<}S4VsOJ=CcYDr)PYZEsw7}AuD#lae1Crct;Mw!MEgWvfK!FF>W<8Qt$P~&1uemBN6!5C73QJ?+T zpXH3XT;-=xrWNY<4fzcivhsP%Yut7)t-3$;=1?1ljX8wbhJF)JqTQa`FWq9oRq`R4?&$Oo#<`+TYcyFXft$VT2q1k{PzcoWyJDh zGUw-9$;UV@D4A#9)>;N!8K{+fAeQs^y%IG&RTiO-%9x}#6w=by|t_w6(zF}3#R>0|cM72KxUrYPs{`cafo(Uj%v*Cp9$a)-{3j%%46IP? zO9o>;k^nlGep9GCdR36bw((Rlw+nKYq?=pGrw>NSvJsJTHwkDEix>3T2X{ToqbRl-6;S1U{AGf zTb}g4B2Yet)7oS5x|8w@qV%P3fK4DvIU;*GoZZJmi(xJk_ewR1#bv+LQ9QW$&`}5{ zV!tIQ%?8c4EC1k(&wzkQ*R@n%nGHsMa!hs~K$c<_=kVy0I;p+H2D?cPoG?h=ll4L= z`5o3)^?V2Q-3+IDw#od5qvgJ?{_+#{Hdnp8UpZ*b%nKzDL>+^w;gw}arRJT^s{iK9 zQn?g+Ap=~S$K$&dv9?T%mqh6K&7V%ms1J{5r5*^{yOW=+1sMoel&Mu&Wl}TuV)gx| zcQR!4hEtL`qoaiRxk(nXR7-u`Gr!M~v6!0}-6up|?Hj88Cd@A9Jt@6K zWLq&bT=n^ujt2CKL6kvO~lWFEX2P6SNt9U{IcS$TkP9h})?%x>|0Y?u515)fm%2P@*g(yz55 zR2g&^hK$_q#Z>V$$#NDzwn=dCZAUeIT!XB&YjljPe=J6v=u99{Qr}jJP^*&*CHRq@ z685~7>6aoaS0gBeJd0qcV;G#3`V(YlLpQ~ywUXcjgMt}>UM}K0d7pH7BTapG$J~RN zRqXU+1G31b!w8Z(I<-PDG`UJ8lQZl*d0jRLw^u^O?2*n0ti+gW^vnsp7=+^XzzzN0 z0uc=~lO(0!m{cHC?~cB*{fQW5D6_;~SR8%I2Hu17{DL~Y@5O!^8Gj2{wm1UXV}rG* zbp)A`1Q~#hJn`H&Ig*CRT98vNxXl*?ce54yo zB4FWGw3$xKCalIdnCG=0P8&?%MCL_TK&A_$Q4;BR@`Fq%MKu2Kt1Lxy;+76Rk_KYC z!r_(;kB|e?+Dq4PZO#agngQsqlogovO|~3G^goR3%+j}3Frs0+L}cIoD63Mk%T+Vi zc<8A(mDLA#_E&8*%Z$6iWn{Mi^*zKJYe107Vg;b%Ku(3E9RWc}NFDY0waf#{k4hm3 zx^+i^%36fVT(#K{x{C@teXz0@`?|9{4ojzcz=Xk28W3Wg5pdBtT*@w zN=gIDHuOzB^9}EcCy?8&~w z9;Q#6w=CG4Co7RXY=EN~W1Qe221{LxaYn$h2X9h2SpJGld6Ix^@q(UFnPH`khppVZ z66+pzS%5r(eJ9IiMRwjZiLI8UuiaRpG9NE=H`?rR)FiLbr^ZfjH4gt_mV=#=uGjax zKpCnETipim_?_iz>9g%+3bK59Zl#R*LbH_uZio4q1g8!-KR%ix9FqzTJ`cuv0t>tK z0w0+>1SJ)Tg+(Zbr#`4eWT@A$xgCfMm9#cXUSEqS-w4N|z9@6tyqu+7h`ancA>O9{ zajT$cWR1<4W$OEoL}V-y51a5Ii5hWKX#`Rf9xqe1er&M2+||Vo&y+|p-{Sx`B2#s0 z@i+JX#q ztZW0uNM^(aZpVI6xF5iO13PP3*db5`y>Lq_iN-ui&-ickK5b132rR$qrQrgQF8HAx z68PvYi5kCGJbB#CC7GN#G7v=6OT1J10m%g@TU8rupor=KgD4{d8t(Hw6S0v2&lH?k z64F-w2pltqww3-DYFT;YieuV=ib=gC2t@Z>u4UA9sYTKcrSxKCEgR5%$8k+pMB7*d z#8VYANYBE}4UQQ=#kX*lmsg)q8^sY2elqHR5{q0?K?#mLj;A+Q2dUb2+GkJ}BcaJ? z4T8zv)}vf1o7O>HkZrb4N{|f`J6k5cL@l z4m=Sn=@a5)I|9!75fSQ^A}Abv;+I+(%)Q7e+@FIgV$U-P@gNAJ`b+!QBy*u0(HS^?$>jxsbsI=sOLz&tu>L(w~f#_2c7YF#@`Q z-|BYf1CC6mfl?yUj78o09!eKR-P^7YRwrzykfCns5iBo(RLgee%flbQkr|&i@z z9Y<-Ai>S%#N9>p0`stJeOihtRJW$|?5G;@hr{D=;2FjX?T6-wc9D_r3d+VU2a6?R@ zz-hUM;{K-^QGjxi^dEpohO@6=8_P#H0)NTDOv3C&dH9U2q@knO_rd1==DCN|DHp$A z4`*=3`WO6?D?Mi&M2+e$eUP14+Fab)Q@kP5lyzBZT$L5zSSz>WNfJoFJ|y~Asm1c@ z4>?NaY*q%kgW3RD-`+Nt7`wkIUuI zIZr9murF)<9Om{w2M|`-4|AU^s#LzR7r|#Sbbjr;Lo#qK^um&teqz!mfA;kyeC*o; z8nK5a`pcljM{IV|j$n-b^#MFkekx8Lg#iMbES zqOpONa8RD;bme;_IM`VZ&`{8U^=PHQ;V2W!2u3zjX`w)cmsE=@HvQ~Y0cERx=JJz$ zba^#Gq9YxeV1K$HE#&78kTtaeO|X(xjrV_otYed?=6qrZ9vm!omdr5i(LHXHNSB`d0eGv3qfG3`fdTUSF- z*Zd&s*P~-(Gxly9QNkx8vyZ=4D=Wuh??03Kd6K^wKo2kH0F{nt(s5dZ;~ zer*v=MJR%b=lr}H%do!%oSRw5kqm~6b;)P+sV|KFwarNweQKMVZG7H5uklQ6W9o1< ze77Eb8-%*%2ibg)y~iRuE&WGZ8=<)8pNYM{{XVTJ(Xb!XBCY!%)qA_U$njH1!$vt_ z;m;40jJ?|XD4*YySt@ys_I&3PsFs{CA72#&csk2rl#aWxx31(VB+JLfB=_$`?W8i7 z4`!$`7dIR!lugZOaTXdG+=~(R8Sak)w;|l)(JwiDQ^|1-I8HSNp?Gm2=F4E3eLI`g z#eXdPDWMJH-CtZF_t>^zJXTids z6pl%S%oBh*^}#Cw)%%S4fWKUyzcEj;cnsZ4BZvhHe*|jZQ?aD0C!uU$TDAyf;r|@9 v*J&gNkIWl#S%k7+p`P!lELgBmPl)^vVh#pts|Zio00000NkvXXu0mjfU?ZM9 literal 0 HcmV?d00001 diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 70e120e841..1d903718ab 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -18,13 +18,19 @@ ms.localizationpriority: high >[!NOTE] >This is a 300 level topic (moderate advanced).
->See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article. +>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
-[SetupDiag.exe](https://go.microsoft.com/fwlink/?linkid=870142) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. +[![Download SetupDiag](../images/download.png)](https://go.microsoft.com/fwlink/?linkid=870142) + +## About SetupDiag + +Current version of SetupDiag: 1.3.1.0 + +SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. SetupDiag works by examining Windows Setup log files. It attempts to parse these log files to determine the root cause of a failure to update or upgrade the computer to Windows 10. SetupDiag can be run on the computer that failed to update, or you can export logs from the computer to another location and run SetupDiag in offline mode. -See the [Release notes](#release-notes) section at the bottom of this topic for information about updates to this tool. +See the [Release notes](#release-notes) section at the bottom of this topic for information about the latest updates to this tool. ## Requirements @@ -356,6 +362,9 @@ Each rule name and its associated unique rule identifier are listed with a descr ## Release notes +07/16/2018 - SetupDiag v1.3.1 is released with 44 rules, as a standalone tool available from the Download Center. + - This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed. + 07/10/2018 - SetupDiag v1.30 is released with 44 rules, as a standalone tool available from the Download Center. - Bug fix for an over-matched plug-in rule. The rule will now correctly match only critical (setup failure) plug-in issues. - New feature: Ability to output logs in JSON and XML format. From 120449d99eb48b25d368ab7e55d46563b4e01325 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 13:35:49 -0700 Subject: [PATCH 02/13] minor release --- windows/deployment/images/download.png | Bin 4561 -> 5398 bytes windows/deployment/upgrade/setupdiag.md | 12 +++++++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/windows/deployment/images/download.png b/windows/deployment/images/download.png index df12d22f7ad2540eb9cfc16370cef346d7891cf5..266a2a196beb87cd5126018bfd3dea1bcd998439 100644 GIT binary patch delta 5396 zcmV+v73=EJBbF*5iBL{Q4GJ0x0000DNk~Le0002F0000g2nGNE0PkP=v5_G(e-x`p zL_t(|UhP^3d{kBT{@!FV=^=ptp+o3M??UJ*9YhciL}fumghgBn?7{*Hh=Rnzf}sc^ z5a~(@l2D`uf;2;iKoTGcg!DEuY5Sc!nf#)ETm$PL-TdAs*O~Y3efOSw&Ueav6D`?V zPyih|N-?y17MGQF0qn~%eC6R|B=wBAhDx-+EFAQ?O4F1&Oy&HV}5s{JCNWp7cOGfK!5mDu7-bX{(<}U`aeW>@dT3NGjQqH zL8RP?BjJtktyKrLTegGIXe<%Y4Mv-zh-3V2Iu&Abu7m4W@}q#4e+KpGK=~^A)kVX{ z+k;t+_{F0~vFNoCsNJG1-d(%F77QP;eYIT)4@q(#V3Lr0@F)x-$x9N+-MxYL z`}adq+)cI79IJ(7H_#9cG=vr1UKoc#Z%sxviTs8TTj1*H@iUS;y91#sRw8)uhbkE4t4@spAO&x%+K#$y zTHA>GA0PoG@a47n8QVVgicf9}`!Yt7Nc6^K>b-7@x6^2Z?Hzuc)8*iuxJJ ze%8+>_oPo`f6Et-Dulh?K33$4i%!7qr3*=ZFH~>b0=>siL66ZBP_s!Zj?FI`Z{L$c zp>9MDx$j6Pi8yo=fA7)|TNlov4jiEs>Q44Aa@h4)K)LKXQ`Z#DK1O7*&oBFzb*1Ig z;hb252yt8X8if9nXP{N@XBfeaaPjcKrnysadQTXve-x4!8;fsauIX>3_1)OgM2>V%KA9|dMwU{ z?!x7;f1^y_cTur!T~()MBxm68H>+{wSQsk!HH4G96XLI3$I(qexEmdf%JmyDx`1QW z;M{@zsL{MV&TyWH{d-}}w$j-=5WaN-Zv6Czfy&On_u{;1lxu}y9o z{Le?}QqJ9~|1hR?C*@Q!mjm~9p6gr=+s}QP@bcmfX#P}N)MUE%A2|Y^ z<*O)NQv_NcIJIjhE*w07w8Rwn*7H-P!sW0Nh}av9jKl;uxwyfcW#*o&@bs;UJ?t#cl4h{PF=ud7beJb!dlwsLOoTN(4R@k%p~_=bv1!gc zgnjcR(;-tLHDF{0*fQ4zuPpx#HCy^op=*$II~v~A{LpS_Z-nvsBuVN(ay02Re+1_A zRD>-37*5Wvcyi(-l57*AP91|+r7B2_zRo%Gs8A0aTDuf)Za&25W>6)kK%z-Loh0Q> zI#!M!f_ogF%koO&e+EXZ`u;ue{KBP5_JC*lBkD}JGOoxd=rQgcJn`DADmCx?>@yr# zwTKhuv+mD=XNAge_9&yqiB3d!e`0(=J`Gr{We3{@*IGPwAo{#96OEtfgj|+R6hS$8 zT+~ghcx5m$Q<7K~uge{$NZcbKLjxDUy=-|L4qAqLQIV9De+LBWro-?t z7%=s11{mdE3TBH18MGmnfm?Z3v}a~Mw0a58H8G$maUO82hb<xMZT%TFNe)I#NwdPJsrxTue9#`&zn;h@QLdgi%Jd|Me<+&)3+Ta;O1FPF z1*wce^*VIN+_N#5aXcE8>OY2S#}DH0y02B~QmH{ROx|_^fl;?GVdDXK_*B5j?}Cte z&y2fKcMuk|0xoo>VIMBXr_r%!*rg|OEo22Dk(r#x{guJT zk$3SNYvat!4DR1uwE_o&Dm}zGoOvx|6MIN1a8|E=3ec!WKP!}IT zXcrfJ|M^_FFmoRb`UZ(Hk#O@ai|L0W@xl4q%zR~FVxSUR+sdT}YX*B1{;ejp+qLj; zEFLjLML4OegbuPv2l7VJ+meybB9q}ck1V<094eBtPe>%jwMQ`_za`s3f$|yo@?d0L zcW%#4b?BvwBEM1X>JwK^Y*CULJQN1@*f1A-N4KQ!e4=)ih)z+<|X{CdzO( z&z-@Y>sMHsWTQrFe=vZks49+Gy+wPt_&C6~acwHoM@8o3_}i*ZEdu9FjLSznokcd; z<<)mojVXJ5tmiX4$eD2Ea40A?dQF{;+ZTVrinpgDfB2(+s6L527D>woLpfPK%bWVB z+r2AN7zI0ynXL9%KqdTAN7Bee_>Ucf@tcmouYFgghdkB^L2r#_*>no2NvTNS-rT&( z(TDS}ZE29o5GIx;ccZQ%i*jc2kgD{|b&~Jps;DXik?hM4WcjP3^X z`0I51xMeLqd2JHT@7X=F-?VPaVZqV~4^>$>lU{q+(+t?qJRMe`iUkEN)t}dE0%OU7-SAs&PVk=d!?w zO8_7L`B4uhqJj$__HgSAhIK%QJ1#O0p zqp@8W)qX0@woaz>4|T~(TwH3hjOx?~SAmP8zl`?5ziJMy`>*=(j=X)GGoL_#sa ze;|iV2%yHW+_`)G9zN~U7CUB7#?>QxSRPo_I?B+T(~^}=BWrMGG?L69kvflxkkUrY z!NI@Omt;jN$GQ9ZV90_67_)A_dR|ienH?LMEtx&J2O;qO#d8rn_iY?o8whJ=8sex2 z2|zNB9Yt%{^-s}6ooc_7QA8D??Q#e-e>zqHn`BIJZgrdEWoU$~XyoJEVWpIbh&V;4T}-v%L{%s@iqWi_Wj-p+_jQlf~y%diAxC8YGFUP%?= zm%1uRD{&;3TB??RJB(PqT@iiN>u)L#OpLjX)qm*?kBXHsI%p?7)m16wesf6Ue?J8W zrXQaDxRG4!p1%Z__HI+JqZ;)btRjLJHz|=W_S`9zIUHFECEScu9xZ9hn~~Ag*AYH` z^^txj77;twqioGOsM@w6Tv<;hv6hTEa~u`wH-=*w4<(ZwqW7Q4BgQMdF1%DkbSdYm zUcJd%gX`f3VPY_I;GyUi562SSe|;M@$Ho1@tPwNN?CDXMb~Fsn1qRs&&VDQBa4qM{ zuLVeny{UfqkvSylt8#_oB%9eYnv#bEkKkc)_ks^tZt>7U;uxIWcy^FlFkh8(8lBA9 z%@YN5vI(IVF^_5g{cBNp|8gWI?mfgv&pC@n6epvaH;2#5GeROc;Toy`e~e@X6OvgV z>nk-;t~{1PX-qqgEFn@85|GVF4Lr#^iL)2er6bEBC+;bY*=6&TsU+@2+nv<_wXM#mHOj8MGx$EX2y`;1a5>MU|`|=lu>jqj>928 z(^W~EL4+u2%c7C0w{L~PfB)Kyiy>RMunCceLs*NK!AtA**gQ`nZW>|&PszfPlds^VGDXaP^Ec$q~5s&Gi%ant^8Glk%&aDf7w7GM3&+_u*+wM zL?DfkxB1YQX>bb;F=B?y3&6I&&%)IM!78IP9WquqtCSwM&xT`XzzTddsvjNEtg@Vy z&(-Mol&WXb@7%`Lw_nD-fF%g|;BU&%Y8|y!F+EWRX(!ixfn|f*U=DQ@IItyBZbd1_ zsMBKrOr8eryA#Z*f5}+=d=CUK2t;VWax5A+2-glrsO;!kp%Qg!g(V{mp&w00E9foNLU(IG0fYi~kgfe>uH!R+<0g`epc*!EO7r zS5!8ZACy?GqhX(+%t-0vRVe%B;@hb+aAnUn*7nXy&qDGdU6rsI#Csm3Ni?d}xgGk> zTZN3fvFe@o$e{hoVSZY|Qd{*>I0bW&WqT{4l7`k$;`Z-En4}bF;W*#skHeChh|IfjsMw^n$~fgo_O#e& zq{YRcQVaIe@nmg@Mp^gbSqi1t$}hQRmnS<@IYL%a0x~(q!ssFars?oucw*WoEEl|S z{L7CKvGprdYTOD#mj}bGvN!7Y9fI0j`Xb@#IfSnYe?Xn?1JxlogC&%On{lb&hW-oJ z!PUzLkq5rV`Rzey`TXlhC26y{RxTr}T^4Clrj(_#S8vx%)!3|wSWy^w7_EbT^H-yW ze_N0PcyiW!G#N6QwZ9pMKA(l7OXo2-J8``#YQNrfYpZpv>8Us!^aalC{02@e3%gHU zsDe|>fAJp>bMgpU4u2JCw{OrcwwhQROrn92*`hLacWBXj?2ksZww*B`;7fI0$e}l6 zC*DOS^(GD@8ODJbraa~D^}z}}_1-M7a#V!0GRuiRGwW8`_+gZvUG^U3&Z zjwuk97lYKUvTu<~f~u@3^T^(0eu1p($N(&B$#*3e$5`k9YCb+Eb2w6V`7U~sJ{d2v z$TRl87m_jZDSM7PeH!0Sd4Xff;F)E+e^9Qrhgw@?wotz!vpg$$Q|sDMxW25TI8X?Y zQRI;4vJ!2365Gh9nwK(&F64W*yqctrq~C6H9;vW<#z(lcZH>x`PtIOYWV@0=`!uR# zB$vf4>FKzQvW|Pf)_&0Ad*qU;RLe2luL4Ecvxt&Y9n=$>nPpO z=ID`JM=3|~mq0pnluGF3ijGnbZJu7P=qTkV@q2O|I{sIoEsD`euA_8A3%se5Tu14K yw(_=4avh}`+S*v1w2kpP$#s-w0RINcd;qU9Rnav70000pA``G{QnRyJ4myl>M`P}(GhnLsW(_LLve^qtQ z)5+`UcW`P5|-q4|)C$}O!rfAcD@7OBA1 z925^n_w#lUe_YPaPUlA^5XsZsSV}6!yh?CUPt5_8%WT6k-G=sSq5dd) zIX;_`1HY&QiDiYmyqzIycY{=oP4c2jSvovI{(h04e6%B92FyDo zV2yqgV6+FJ(w~l(hyXXeQ9~w3A3ibp+%^HBI<@tZdoS~srQ7pCLfX>LM`Y2)+@=khjfm#63KOSie3vbcuRI|u zcENFhj-ej1;h{*4P>j?BiOABT2mt}ks7ei^#Na1OB3?$B#u9_y`3%8!b06bxzAjMX zVoZKF#x%hgQh`yQ{n(%7jJaIpr%|RA>h}%#4H&ZWdCY6ve|9jfxiP#d9cT96@8 zFQv+mC7H4&h2+qc$cM`u$i()O<+5XRv^?HD2wZ~sd7q%1l*7;uL7gg{=xzL4edqXS zGjwEHQ-S{c_Xmq*#PVY@=jU9>$2cx1nP=bDS_WJhsFi#mmh>XDHjyex}#6w=bf4#M=8Wkn82DOpy@!p!jl`}X= zzs`O#Z%A8N`)D-ohe?PZG6@}npi{uvp1rk|e1Yc&UK^|&uvWn7dPKEQe=7)VKNO|r?i}F-nX1JV8EN{kcItWJ(W?XG<$-NQ z@++j@ezdf2P4(m-B@xO#MALh zMybqOb3z_mbXfc+B%=(hQ0+?wV?L4qI+%V_s62XAki@p}R5G^}HgIEgY49 z_I(=yK5Huf5?@b~ZHHK6W4!!I`3TN&M<-uNM+p`+VXxXZBqzm7Ld!GDjABG&?{ToqbRl-6;S1U{AGfTb}g4B2Yet)7oS5x|8w@qV%P3fK4DvIU;*GoZZJm zi(xJk_ewR1#bv+LQ9QW$&`}5{V!tIQ%?8c4EC1k(&wzkQ*R@n%nGHsMa!hs~K$c<_ z=kVy0I;p+H2D?cPoG?h=ll4L=`5o3)fAxF^_1z4od$!5^hoj}buKw~9_BL0&yk9wJ z&dduX5JVk=s^OJoN2TVS&Z__B%u=}&dm#f{o5$n36|uHVjF&{{`OTkB$*2#HXr&$q z+PjmVtOXeeSCpw$S!Gf)_hR+^rgt)A^@dZDIisV5`MF6JvQ$fb-7~+>k+GPYe;C~- zL|*M1s{SU-F6TWdS&B=cQ_@O2j0hkcC*+*qK-P-iph5s@r= z;51XueBmn8FUwhjNITz1gRHe{ zbd0QjEJmE@OdwHG-&TrHtCI^Q_>r9w_Pmzqmm(`yBPfMDi(sf@7@U>*e-mV9LpQ~y zwUXcjgMt}>UM}K0d7pH7BTapG$J~RNRqXU+1G31b!w8Z(I<-PDG`UJ8lQZl*d0jRL zw^u^O?2*n0ti+gW^vnsp7=+^XzzzN00uc=~lO(0!m{cHC?~cB*{fQW5D6_;~SR8%I z2Hu17{DL~Y@5O!^8Gj2{f3`RR+GB&YsC5LHk^~umjXd$(H#w4q$Xbw7F5}mnRBe4p z0{GX5zvip&JwTqY7>z&+w`grW6MUo_OCn(5RAe~_91=&zI&nD$M! z97Xg$jO@(Pw^lHsVZ20S-~K48QnJfcGuL?NsW_F@2Y2>YZ8Xb_yTWB;w*d7$#2afs zkji2OpyNPJg`^z;K}kp*_4&2T1Iv#}Aqcv4M}f*(gvwmC*$}#m3Os$VvKRZhvpf$X zEZmwWPxlIzZIk0=fAu}5%TyBXGQI32#=U<;Dv^~&eWYcu<_5>4f?q^K2^Y2UMBN;9 z2C+&Jjcg`h8}5C0e}r5HhlvS-;!FgrH~0ujN(0I^^i4hU4eyF52y8hF1481K-kR9Q zNis%ul!?XMI{~hAJbZtDn?|6kBfaD{lwri^&rhh&J}CX@e~83Eo_?8}isc|l=5DIG z%!eohml*1!l~oE=kdtGesYs93Wmv>y?8&~w9;Q#6w=CG4Co7RXY=EN~W1Qe221{Lx zaYn$h2X9h2SpJGld6Ix^@q(UFnPH`khppVZ66+pzS%5r(eJ9IiMRwjZiLI8UuiaRp zG9NE=H`?rRf7B$e(Wk~va5WD9VU~lPlCIbHyg(VM3R~R<@c5nOYw5G?WeT!92b!z1y%Xb!N#yM?Y_=)!Aw7Z-QHxPG& zDdNX>z}#>IZ;TnltOk6UQUnLl_CBH0Qe@hK40Wt*1I9>Z#0GB1eo?p|z<&cfYgyPK zPzJqle@iQg#ym>T_;2+-ZA}UYEWhfd;R28@_@NyV_~g= zNxdZqME6{-Wz==4MbZzY^kQT!8_<2naZOi5f7@6D#8VYANYBE}4UQQ=#kX*lmsg)q z8^sY2elqHR5{q0?K?#mLj;A+Q2dUb2+GkJ}BcaJ?4T8zv)}vf1o7O>HkZrb4N{|f`5r+76EyEo|EICmotM+M`XW!TuS%)ioQoQ=k1AzjRekFP-ym3^dteldd z-aiqFxFE%|C>Mzv;=N^4QoI~}v4aHbna0JDWf1il5Dq*ME9n#BWIF=R`VkT8mLez| zed3o|8O*)ND%_ugDq_zw3Gzfw?BkfNf8gx95O9cp{jH7cq|6}E8l9XZ(&niNatv9+ z08ie{c)C|h`5yBZOg-J_qo1^6aaAb*55Q+ipYI^KlN01|?jeDt+Y4ka*Q_7d7~sL( z5tOb(Z)EjFCCEH8mn%Xa3=!ymwr8KHmc%1n68Ra zO_4=BP~eFWERYGO;0a*{%9@K>dnnQzgF|(D>!74?LrkK;X}O2u{-+vIfO3-bAAm@P zv#($q%SSi@f62j2!t6$Q_>8Tjf1#t;_rd1==DCN|DHp$A4`*=3`WO6?D?Mi&M2+e$ zeUP14+Fab)Q@kP5lyzBZT$L5zSSz>WNfJoFJ|y~Asm1c@4>?NaY*q%kgW3RD-`j)37gV{T$}@KnD<3 z*$;D{EUHw#vKPT;F?4?IyhAc@F7(2ZmwsZ>Cx7K)kuQT}0t6PMpbfunkf0U4LCK;O&=l(?n7R|Tc>k)~$56PmjftGMkp6GPtdn7p6 zSq{)p(1G=6rNH4R6UzujHdAS#K!ul7iz_z$>{bC~tA6J4lYMk~HA12z9h&70!B+x? z+?<;-FjJ6}Bo6lu1m7)j68k>X4ULIE{rue|KM(i0zhZ#lxGYWaf8mMmr6^a_8YmOx z!Wu{x7qnGzd_KoMTnERo2jz!s?vRNkRv~}-!~Vvc98-Tc=LwQg>=Mew;9+EC z_Qx0jxSv~q=h=+g>Rpzvi&RoS+zU|$yeKP(V!Tr5K0950+)*GtA#PHbg>|8-QR#-@ zOI!14A!Xt%&P^H2e|~1xCvAiMtWPk;q`ZV-C+eS|DRYpKL*22lE0Y^~1j(9VTBddy zxkCk&=79SBOo`5e1@D<0FC9X(a_m5Mxx`N0ciNau0UE@xA4RBZ4d)Y-gZ5X>X(xjr zV_otYed?=6qrZ9vm!omdr5i(LHXHNSB`d0eGv3qfG3`fde_K~WQP=z+>(`@WWHa_| z8&Se1BD0UbRx2yVV(&kb`+1VT89)y&=Kz(CXwq?7s(PVVfG8OI!hUTLO+_ezis$^i z8q2W11)Q5%$dL?&jCILp^r3>6$E%X%VCs`yRo;f(L+~d(NIek;faSk|6H3p%0e{mt^%V3&)JDb(Te=Phdp$;2x zHI*ZCUe3=$oTilH9B`beDy!v^2rt?C&uG1&e&{|YU4Bfh=l>{Y!NQ*uj!A{g6M#DP z!7BpQ`;7X4zg(ZcF;B914Bbp4hy@FO1Zv+?v81afp=@AUwg_e6{~Wc~X(R`a%o}o9 ngtB0vAD-{2ELgBmPl)^vVh#pts|Zio00000NkvXXu0mjfi>aoe diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 1d903718ab..a9b454c671 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -20,7 +20,7 @@ ms.localizationpriority: high >This is a 300 level topic (moderate advanced).
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
-[![Download SetupDiag](../images/download.png)](https://go.microsoft.com/fwlink/?linkid=870142) + [![Download SetupDiag](../images/download.png)](https://go.microsoft.com/fwlink/?linkid=870142) ## About SetupDiag @@ -30,6 +30,16 @@ SetupDiag is a standalone diagnostic tool that can be used to obtain details abo SetupDiag works by examining Windows Setup log files. It attempts to parse these log files to determine the root cause of a failure to update or upgrade the computer to Windows 10. SetupDiag can be run on the computer that failed to update, or you can export logs from the computer to another location and run SetupDiag in offline mode. +To quickly use SetupDiag on your current computer: +1. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). +2. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. +3. When SetupDiag has finished downloading, open the **Downloads** folder. If you downloaded the file somewhere else, open that folder instead. +4. Double-click the SetupDiag file. Click **Yes** if you are asked to approve running the program. +5. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. +6. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. +7. Use Notepad or another text file viewer application to open the log file displaying the current date in the name (ex: SetupDiag_17-Jul-2018.log). +8. Review the information to discover if any rules were matched that can tell you why the computer failed to upgrade. For an example, see the [Text log sample](#text-log-sample) below. + See the [Release notes](#release-notes) section at the bottom of this topic for information about the latest updates to this tool. ## Requirements From 516a40ebb1f114654af4bceebee38a04b8da45c3 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 16:26:09 -0700 Subject: [PATCH 03/13] update --- windows/deployment/upgrade/setupdiag.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index a9b454c671..11c041aa61 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -32,13 +32,13 @@ SetupDiag works by examining Windows Setup log files. It attempts to parse these To quickly use SetupDiag on your current computer: 1. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). -2. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. -3. When SetupDiag has finished downloading, open the **Downloads** folder. If you downloaded the file somewhere else, open that folder instead. -4. Double-click the SetupDiag file. Click **Yes** if you are asked to approve running the program. +2. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. You can also save it to a different location if desired by using **Save As**. +3. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left pane. +4. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. 5. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. 6. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. -7. Use Notepad or another text file viewer application to open the log file displaying the current date in the name (ex: SetupDiag_17-Jul-2018.log). -8. Review the information to discover if any rules were matched that can tell you why the computer failed to upgrade. For an example, see the [Text log sample](#text-log-sample) below. +7. Use Notepad or another text file viewer application to open the log file (SetupDiagResults.log). +8. Review the information to discover if any rules were matched that can tell you why the computer failed to upgrade. See the [Text log sample](#text-log-sample) below. See the [Release notes](#release-notes) section at the bottom of this topic for information about the latest updates to this tool. From 8a6c0851ddeead8174c5ad4c0068dc45e958909d Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 16:28:10 -0700 Subject: [PATCH 04/13] update --- windows/deployment/upgrade/setupdiag.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 11c041aa61..0aae00a355 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -7,7 +7,7 @@ ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy author: greg-lindsay -ms.date: 07/10/2018 +ms.date: 07/17/2018 ms.localizationpriority: high --- From eebf26a9081cde52a73de22e141561f71c1d40b2 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 16:35:24 -0700 Subject: [PATCH 05/13] update --- windows/deployment/upgrade/setupdiag.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 0aae00a355..f1cadc868c 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -31,16 +31,19 @@ SetupDiag is a standalone diagnostic tool that can be used to obtain details abo SetupDiag works by examining Windows Setup log files. It attempts to parse these log files to determine the root cause of a failure to update or upgrade the computer to Windows 10. SetupDiag can be run on the computer that failed to update, or you can export logs from the computer to another location and run SetupDiag in offline mode. To quickly use SetupDiag on your current computer: -1. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). -2. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. You can also save it to a different location if desired by using **Save As**. -3. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left pane. -4. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. -5. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. -6. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. -7. Use Notepad or another text file viewer application to open the log file (SetupDiagResults.log). -8. Review the information to discover if any rules were matched that can tell you why the computer failed to upgrade. See the [Text log sample](#text-log-sample) below. +1. Verify that your system meets the [requirements](#requirements) described below. If needed, install the [.NET framework 4.6](https://www.microsoft.com/download/details.aspx?id=48137). +2. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). +3. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. You can also save it to a different location if desired by using **Save As**. +4. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left pane. +5. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. +6. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. +7. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. +8. Use Notepad to open the log file: **SetupDiagResults.log**. +9. Review the information that is displayed. If a rule was matched this can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the [Text log sample](#text-log-sample) below. -See the [Release notes](#release-notes) section at the bottom of this topic for information about the latest updates to this tool. +For instructions on how to run the tool in offline more and with more advanced options, see the [Parameters](#parameters) section below. + +See the [Release notes](#release-notes) section at the bottom of this topic for information about recent updates to this tool. ## Requirements From 8d931f475c887f3519580b9474ac1c2fb899cade Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 17 Jul 2018 16:43:48 -0700 Subject: [PATCH 06/13] update --- windows/deployment/upgrade/setupdiag.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index f1cadc868c..640c908099 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -35,11 +35,12 @@ To quickly use SetupDiag on your current computer: 2. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). 3. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. You can also save it to a different location if desired by using **Save As**. 4. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left pane. -5. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. -6. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. -7. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. -8. Use Notepad to open the log file: **SetupDiagResults.log**. -9. Review the information that is displayed. If a rule was matched this can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the [Text log sample](#text-log-sample) below. +5. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. + >Double-clicking the file to run it will automatically close the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing SetupDiag at the command prompt instead of double-clicking it. You will need to change directories to the location of SetupDiag to run it this way. +1. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. +2. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. +3. Use Notepad to open the log file: **SetupDiagResults.log**. +4. Review the information that is displayed. If a rule was matched this can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the [Text log sample](#text-log-sample) below. For instructions on how to run the tool in offline more and with more advanced options, see the [Parameters](#parameters) section below. From fe4e7c76c681576bf8226083fc829015369d09d1 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 18 Jul 2018 11:16:06 -0700 Subject: [PATCH 07/13] update --- windows/deployment/upgrade/setupdiag.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 640c908099..6e2f61c6a9 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -32,19 +32,19 @@ SetupDiag works by examining Windows Setup log files. It attempts to parse these To quickly use SetupDiag on your current computer: 1. Verify that your system meets the [requirements](#requirements) described below. If needed, install the [.NET framework 4.6](https://www.microsoft.com/download/details.aspx?id=48137). -2. Click [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). +2. [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). 3. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. You can also save it to a different location if desired by using **Save As**. -4. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left pane. -5. Double-click the SetupDiag file to run it. Click **Yes** if you are asked to approve running the program. - >Double-clicking the file to run it will automatically close the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing SetupDiag at the command prompt instead of double-clicking it. You will need to change directories to the location of SetupDiag to run it this way. -1. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. -2. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. -3. Use Notepad to open the log file: **SetupDiagResults.log**. -4. Review the information that is displayed. If a rule was matched this can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the [Text log sample](#text-log-sample) below. +4. When SetupDiag has finished downloading, open the folder where you downloaded the file. As mentioned above, by default this is your **Downloads** folder which is displayed in File Explorer under **Quick access** in the left navigation pane. +5. Double-click the **SetupDiag** file to run it. Click **Yes** if you are asked to approve running the program. + - Double-clicking the file to run it will automatically close the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing **SetupDiag** at the command prompt instead of double-clicking it. You will need to change directories to the location of SetupDiag to run it this way. +6. A command window will open while SetupDiag diagnoses your computer. Wait for this to finish. +7. When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file. +8. Use Notepad to open the log file: **SetupDiagResults.log**. +9. Review the information that is displayed. If a rule was matched this can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the [Text log sample](#text-log-sample) below. -For instructions on how to run the tool in offline more and with more advanced options, see the [Parameters](#parameters) section below. +For instructions on how to run the tool in offline more and with more advanced options, see the [Parameters](#parameters) and [Examples](#examples) sections below. -See the [Release notes](#release-notes) section at the bottom of this topic for information about recent updates to this tool. +The [Release notes](#release-notes) section at the bottom of this topic has information about recent updates to this tool. ## Requirements @@ -63,7 +63,7 @@ See the [Release notes](#release-notes) section at the bottom of this topic for | /Output:\ |
  • This optional parameter enables you to specify the output file for results. This is where you will find what SetupDiag was able to determine. Only text format output is supported. UNC paths will work, provided the context under which SetupDiag runs has access to the UNC path. If the path has a space in it, you must enclose the entire path in double quotes (see the example section below).
  • Default: If not specified, SetupDiag will create the file **SetupDiagResults.log** in the same directory where SetupDiag.exe is run.
| | /Mode:\ |
  • This optional parameter allows you to specify the mode in which SetupDiag will operate: Offline or Online.
  • Offline: tells SetupDiag to run against a set of log files already captured from a failed system. In this mode you can run anywhere you have access to the log files. This mode does not require SetupDiag to be run on the computer that failed to update. When you specify offline mode, you must also specify the /LogsPath: parameter.
  • Online: tells SetupDiag that it is being run on the computer that failed to update. SetupDiag will attempt find log files and resources in standard Windows locations, such as the **%SystemDrive%\$Windows.~bt** directory for setup log files.
  • Log file search paths are configurable in the SetupDiag.exe.config file, under the SearchPath key. Search paths are comma separated. Note: A large number of search paths will extend the time required for SetupDiag to return results.
  • Default: If not specified, SetupDiag will run in Online mode.
| | /LogsPath:\ |
  • This optional parameter is required only when **/Mode:Offline** is specified. This tells SetupDiag.exe where to find the log files. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories. This parameter should be omitted when the **/Mode:Online** is specified.
| -| /ZipLogs:\ |
  • This optional parameter tells SetupDiag.exe to create a zip file continuing its results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.
  • Default: If not specified, a value of 'true' is used.
| +| /ZipLogs:\ |
  • This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.
  • Default: If not specified, a value of 'true' is used.
| | /Verbose |
  • This optional parameter will output much more data to the log file produced by SetupDiag.exe. By default SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce a log file with debugging details, which can be useful when reporting a problem with SetupDiag.
| | /Format:\ |
  • This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.
| From 503947c89d6170b4b889d4c0f85aeb027c0b409b Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 18 Jul 2018 14:21:42 -0700 Subject: [PATCH 08/13] update --- windows/deployment/upgrade/setupdiag.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 90965a2bd0..3f9716261b 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -64,7 +64,7 @@ The [Release notes](#release-notes) section at the bottom of this topic has info | /Mode:\ |
  • This optional parameter allows you to specify the mode in which SetupDiag will operate: Offline or Online.
  • Offline: tells SetupDiag to run against a set of log files already captured from a failed system. In this mode you can run anywhere you have access to the log files. This mode does not require SetupDiag to be run on the computer that failed to update. When you specify offline mode, you must also specify the /LogsPath: parameter.
  • Online: tells SetupDiag that it is being run on the computer that failed to update. SetupDiag will attempt find log files and resources in standard Windows locations, such as the **%SystemDrive%\$Windows.~bt** directory for setup log files.
  • Log file search paths are configurable in the SetupDiag.exe.config file, under the SearchPath key. Search paths are comma separated. Note: A large number of search paths will extend the time required for SetupDiag to return results.
  • Default: If not specified, SetupDiag will run in Online mode.
| | /LogsPath:\ |
  • This optional parameter is required only when **/Mode:Offline** is specified. This tells SetupDiag.exe where to find the log files. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories. This parameter should be omitted when the **/Mode:Online** is specified.
| | /ZipLogs:\ |
  • This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.
  • Default: If not specified, a value of 'true' is used.
| -| /Verbose |
  • This optional parameter will output much more data to the log file produced by SetupDiag.exe. By default SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce a log file with debugging details, which can be useful when reporting a problem with SetupDiag.
| +| /Verbose |
  • This optional parameter will output much more data to a log file. By default SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.
| | /Format:\ |
  • This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.
| ### Examples: From f354a053804c92d22f20a38eeb1f15db23f94760 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Fri, 14 Dec 2018 15:03:18 -0800 Subject: [PATCH 09/13] 1.4.0.0 --- windows/deployment/upgrade/setupdiag.md | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 893d357f79..794be7b222 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -7,7 +7,7 @@ ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy author: greg-lindsay -ms.date: 08/16/2018 +ms.date: 12/14/2018 ms.localizationpriority: medium --- @@ -24,7 +24,7 @@ ms.localizationpriority: medium ## About SetupDiag -Current version of SetupDiag: 1.3.1.0 +Current version of SetupDiag: 1.4.0.0 SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. @@ -61,11 +61,14 @@ The [Release notes](#release-notes) section at the bottom of this topic has info | --- | --- | | /? |
  • Displays interactive help
| | /Output:\ |
  • This optional parameter enables you to specify the output file for results. This is where you will find what SetupDiag was able to determine. Only text format output is supported. UNC paths will work, provided the context under which SetupDiag runs has access to the UNC path. If the path has a space in it, you must enclose the entire path in double quotes (see the example section below).
  • Default: If not specified, SetupDiag will create the file **SetupDiagResults.log** in the same directory where SetupDiag.exe is run.
| -| /Mode:\ |
  • This optional parameter allows you to specify the mode in which SetupDiag will operate: Offline or Online.
  • Offline: tells SetupDiag to run against a set of log files already captured from a failed system. In this mode you can run anywhere you have access to the log files. This mode does not require SetupDiag to be run on the computer that failed to update. When you specify offline mode, you must also specify the /LogsPath: parameter.
  • Online: tells SetupDiag that it is being run on the computer that failed to update. SetupDiag will attempt find log files and resources in standard Windows locations, such as the **%SystemDrive%\$Windows.~bt** directory for setup log files.
  • Log file search paths are configurable in the SetupDiag.exe.config file, under the SearchPath key. Search paths are comma separated. Note: A large number of search paths will extend the time required for SetupDiag to return results.
  • Default: If not specified, SetupDiag will run in Online mode.
| | /LogsPath:\ |
  • This optional parameter is required only when **/Mode:Offline** is specified. This tells SetupDiag.exe where to find the log files. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories. This parameter should be omitted when the **/Mode:Online** is specified.
| | /ZipLogs:\ |
  • This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.
  • Default: If not specified, a value of 'true' is used.
| | /Verbose |
  • This optional parameter will output much more data to a log file. By default, SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.
| | /Format:\ |
  • This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.
| +| /NoTel |
  • This optional parameter tells SetupDiag.exe not to send diagnostic telemetry to Microsoft.
| + +Note: The **/Mode** parameter is deprecated in version 1.4.0.0 of SetupDiag. +- In previous versions, this command was used with the LogsPath parameter to specify that SetupDiag should run in an offline manner to analyze a set of log files that were captured from a different computer. In version 1.4.0.0 when you specify /LogsPath then SetupDiag will automatically run in offline mode, therefore the /Mode parameter is not needed. ### Examples: @@ -75,10 +78,10 @@ In the following example, SetupDiag is run with default parameters (online mode, SetupDiag.exe ``` -In the following example, SetupDiag is specified to run in Online mode (this is the default). It will know where to look for logs on the current (failing) system, so there is no need to gather logs ahead of time. A custom location for results is specified. +In the following example, SetupDiag is run in online mode (this is the default). It will know where to look for logs on the current (failing) system, so there is no need to gather logs ahead of time. A custom location for results is specified. ``` -SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Online +SetupDiag.exe /Output:C:\SetupDiag\Results.log ``` The following example uses the /Output parameter to save results to a path name that contains a space: @@ -90,7 +93,7 @@ SetupDiag /Output:"C:\Tools\SetupDiag\SetupDiag Results\Results.log" The following example specifies that SetupDiag is to run in offline mode, and to process the log files found in **D:\Temp\Logs\LogSet1**. ``` -SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Offline /LogsPath:D:\Temp\Logs\LogSet1 +SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:D:\Temp\Logs\LogSet1 ``` ## Log files @@ -375,6 +378,14 @@ Each rule name and its associated unique rule identifier are listed with a descr ## Release notes +12/16/2018 - SetupDiag v1.4.0.0 is released with 44 rules, as a standalone tool available from the Download Center. + - This release includes major improvements in rule processing performance: about 3x faster in processing rules! + - The FindDownlevelFailure rule is up to 10x faster. + - New rules have been added to analyze failures upgrading to Windows 10 version 1809. + - A new help link is available for resolving servicing stack failures on the down-level OS when the rule match indicates this type of failure. + - Removed the need to specify /Mode parameter. Now if you specify /LogsPath, it automatically assumes offline mode. + - A few other minor improvements were made in specific rules. + 07/16/2018 - SetupDiag v1.3.1 is released with 44 rules, as a standalone tool available from the Download Center. - This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed. From 34d4a6bdc7c5826fc472899cce7a1698fb0c2ba8 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 18 Dec 2018 12:01:44 -0800 Subject: [PATCH 10/13] setupdiag 1.4 --- windows/deployment/upgrade/setupdiag.md | 30 ++++++++++++++++++++----- 1 file changed, 24 insertions(+), 6 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 794be7b222..b3f10c8d57 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -7,7 +7,7 @@ ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy author: greg-lindsay -ms.date: 12/14/2018 +ms.date: 12/18/2018 ms.localizationpriority: medium --- @@ -368,23 +368,41 @@ Each rule name and its associated unique rule identifier are listed with a descr 40. UpdateAgentExpanderFailure – 66E496B3-7D19-47FA-B19B-4040B9FD17E2 - Matches DPX expander failures in the down-level phase of update from WU. Will output the package name, function, expression and error code. 41. FindFatalPluginFailure – E48E3F1C-26F6-4AFB-859B-BF637DA49636 - - Matches any plug in failure that setupplatform decides is fatal to setup. Will output the plugin name, operation and error code. + - Matches any plug-in failure that setupplatform decides is fatal to setup. Will output the plugin name, operation and error code. 42. AdvancedInstallerFailed - 77D36C96-32BE-42A2-BB9C-AAFFE64FCADC - Indicates critical failure in the AdvancedInstaller while running an installer package, includes the .exe being called, the phase, mode, component and error codes. 43. MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9 - - Indicates a critical failure in a migration plugin that causes setup to abort the migration. Will provide the setup operation, plug in name, plug in action and error code. + - Indicates a critical failure in a migration plugin that causes setup to abort the migration. Will provide the setup operation, plug-in name, plug-in action and error code. 44. DISMAddPackageFailed - 6196FF5B-E69E-4117-9EC6-9C1EAB20A3B9 - Indicates a critical failure during a DISM add package operation. Will specify the Package Name, DISM error and add package error code. +45. PlugInComplianceBlock - D912150B-1302-4860-91B5-527907D08960 + - Detects all compat blocks from Server compliance plug-ins. Outputs the block information and remediation. +46. AdvancedInstallerGenericFailure - 4019550D-4CAA-45B0-A222-349C48E86F71 + - Triggers on advanced installer failures in a generic sense, outputting the application called, phase, mode, component and error code. +47. FindMigGatherApplyFailure - A9964E6C-A2A8-45FF-B6B5-25E0BD71428E + - Shows errors when the migration Engine fails out on a gather or apply operation. Indicates the Migration Object (file or registry path), the Migration +48. OptionalComponentFailedToGetOCsFromPackage - D012E2A2-99D8-4A8C-BBB2-088B92083D78 + - Indicates the optional component (OC) migration operation failed to enumerate optional components from an OC Package. Outputs the package name and error code. +49. OptionalComponentOpenPackageFailed - 22952520-EC89-4FBD-94E0-B67DF88347F6 + - Indicates the optional component migration operation failed to open an optional component Package. Outputs the package name and error code. +50. OptionalComponentInitCBSSessionFailed - 63340812-9252-45F3-A0F2-B2A4CA5E9317 + - Indicates corruption in the servicing stack on the down-level system. Outputs the error code encountered while trying to initialize the servicing component on the existing OS. +51. DISMproviderFailure - D76EF86F-B3F8-433F-9EBF-B4411F8141F4 + - Triggers when a DISM provider (plug-in) fails in a critical operation. Outputs the file (plug-in name), function called + error code, and error message from the provider. +52. SysPrepLaunchModuleFailure - 7905655C-F295-45F7-8873-81D6F9149BFD + - Indicates a sysPrep plug-in has failed in a critical operation. Indicates the plug-in name, operation name and error code. +53. UserProvidedDriverInjectionFailure - 2247C48A-7EE3-4037-AFAB-95B92DE1D980 + - A driver provided to setup (via command line input) has failed in some way. Outputs the driver install function and error code. ## Release notes -12/16/2018 - SetupDiag v1.4.0.0 is released with 44 rules, as a standalone tool available from the Download Center. - - This release includes major improvements in rule processing performance: about 3x faster in processing rules! +12/18/2018 - SetupDiag v1.4.0.0 is released with 53 rules, as a standalone tool available from the Download Center. + - This release includes major improvements in rule processing performance: ~3x faster rule processing performance! - The FindDownlevelFailure rule is up to 10x faster. - New rules have been added to analyze failures upgrading to Windows 10 version 1809. - A new help link is available for resolving servicing stack failures on the down-level OS when the rule match indicates this type of failure. - Removed the need to specify /Mode parameter. Now if you specify /LogsPath, it automatically assumes offline mode. - - A few other minor improvements were made in specific rules. + - Some functional and output improvements were made for several rules. 07/16/2018 - SetupDiag v1.3.1 is released with 44 rules, as a standalone tool available from the Download Center. - This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed. From c84b6501db90326c7903f884d29561b69115a21d Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 18 Dec 2018 12:11:04 -0800 Subject: [PATCH 11/13] setupdiag 1.4 --- windows/deployment/deploy-whats-new.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 4e9ee7e411..a0d7f4cfa8 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -7,7 +7,7 @@ ms.localizationpriority: medium ms.prod: w10 ms.sitesec: library ms.pagetype: deploy -ms.date: 12/07/2018 +ms.date: 12/18/2018 author: greg-lindsay --- @@ -23,6 +23,10 @@ This topic provides an overview of new solutions and online content related to d - For an all-up overview of new features in Windows 10, see [What's new in Windows 10](https://technet.microsoft.com/itpro/windows/whats-new/index). - For a detailed list of changes to Windows 10 ITPro TechNet library content, see [Online content change history](#online-content-change-history). +## Recent additions to this page + +[SetupDiag](#setupdiag) 1.4 is released. + ## The Modern Desktop Deployment Center The [Modern Desktop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home) has launched with tons of content to help you with large-scale deployment of Windows 10 and Office 365 ProPlus. @@ -56,6 +60,12 @@ Windows Autopilot streamlines and automates the process of setting up and config Windows Autopilot joins devices to Azure Active Directory (Azure AD), optionally enrolls into MDM services, configures security policies, and sets a custom out-of-box-experience (OOBE) for the end user. For more information, see [Overview of Windows Autopilot](windows-autopilot/windows-autopilot.md). +### SetupDiag + +[SetupDiag](upgrade/setupdiag.md) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. + +SetupDiag version 1.4 was released on 12/18/2018. + ### Upgrade Readiness The Upgrade Readiness tool moved from public preview to general availability on March 2, 2017. From fd152689337b3356a230b029a538d61deb6f1989 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 18 Dec 2018 12:35:22 -0800 Subject: [PATCH 12/13] removed references to /mode --- windows/deployment/upgrade/setupdiag.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index b3f10c8d57..2382a0a80a 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -61,7 +61,7 @@ The [Release notes](#release-notes) section at the bottom of this topic has info | --- | --- | | /? |
  • Displays interactive help
| | /Output:\ |
  • This optional parameter enables you to specify the output file for results. This is where you will find what SetupDiag was able to determine. Only text format output is supported. UNC paths will work, provided the context under which SetupDiag runs has access to the UNC path. If the path has a space in it, you must enclose the entire path in double quotes (see the example section below).
  • Default: If not specified, SetupDiag will create the file **SetupDiagResults.log** in the same directory where SetupDiag.exe is run.
| -| /LogsPath:\ |
  • This optional parameter is required only when **/Mode:Offline** is specified. This tells SetupDiag.exe where to find the log files. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories. This parameter should be omitted when the **/Mode:Online** is specified.
| +| /LogsPath:\ |
  • This optional parameter tells SetupDiag.exe where to find the log files for an offline analysis. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories.
| | /ZipLogs:\ |
  • This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.
  • Default: If not specified, a value of 'true' is used.
| | /Verbose |
  • This optional parameter will output much more data to a log file. By default, SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.
| | /Format:\ |
  • This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.
| @@ -114,7 +114,7 @@ When Microsoft Windows encounters a condition that compromises safe system opera If crash dumps [are enabled](https://docs.microsoft.com/windows-hardware/drivers/debugger/enabling-a-kernel-mode-dump-file) on the system, a crash dump file is created. If the bug check occurs during an upgrade, Windows Setup will extract a minidump (setupmem.dmp) file. SetupDiag can also debug these setup related minidumps. To debug a setup related bug check, you must: -- Specify the **/Mode:Offline** and **/LogsPath** parameters. You cannot debug memory dumps in online mode. +- Specify the **/LogsPath** parameter. You cannot debug memory dumps in online mode. - Gather the setup memory dump file (setupmem.dmp) from the failing system. - Setupmem.dmp will be created in either **%SystemDrive%\$Windows.~bt\Sources\Rollback**, or in **%WinDir%\Panther\NewOS\Rollback** depending on when the bug check occurs. - Install the [Windows Debugging Tools](https://docs.microsoft.com/windows-hardware/drivers/debugger/debugger-download-tools) on the computer that runs SetupDiag. @@ -122,7 +122,7 @@ To debug a setup related bug check, you must: In the following example, the **setupmem.dmp** file is copied to the **D:\Dump** directory and the Windows Debugging Tools are installed prior to running SetupDiag: ``` -SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /Mode:Offline /LogsPath:D:\Dump +SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /LogsPath:D:\Dump ``` ## Known issues @@ -138,7 +138,7 @@ The following is an example where SetupDiag is run in offline mode. In this exam The output also provides an error code 0xC1900208 - 0x4000C which corresponds to a compatibility issue as documented in the [Upgrade error codes](upgrade-error-codes.md#result-codes) and [Resolution procedures](resolution-procedures.md#modern-setup-errors) topics in this article. ``` -C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Offline /LogsPath:C:\Temp\BobMacNeill +C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:C:\Temp\BobMacNeill SetupDiag v1.01 Copyright (c) Microsoft Corporation. All rights reserved From f9df450acf6cad167da362ea4cbd1354918f4123 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 18 Dec 2018 13:02:23 -0800 Subject: [PATCH 13/13] updated one line --- windows/deployment/upgrade/setupdiag.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 2382a0a80a..53856948d2 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -140,8 +140,8 @@ The output also provides an error code 0xC1900208 - 0x4000C which corresponds to ``` C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:C:\Temp\BobMacNeill -SetupDiag v1.01 -Copyright (c) Microsoft Corporation. All rights reserved +SetupDiag v1.4.0.0 +Copyright (c) Microsoft Corporation. All rights reserved. Searching for setup logs, this can take a minute or more depending on the number and size of the logs...please wait. Found 4 setupact.logs.