Oh ok those people should had mentioned it was VLSC. Copying iso name in to google didn't came up with any decent result. lol
The ESD decrypter links in post #1 seem to be dead. Downloaded the Enterprise version and really could use that decrypter (please and thank you).
anyone have 414ef8387f8af927730a309c199fcfaeec6eca39 *SW_DVD5_WIN_EDU_10_1703_32BIT_ChnTrad_MLF_X21-36543.ISO 271ddf627beab442f1041af55e9495cf89d93343 *SW_DVD5_WIN_EDU_10_1703_64BIT_ChnTrad_MLF_X21-36544.ISO 0531c926ab7f28c02df03f0608e9f5426a595681 *SW_DVD5_Win_Pro_10_1703_32BIT_ChnTrad_MLF_X21-36715.ISO 838ac7de225c026e8e3340f7b280ccb2578df3d3 *SW_DVD5_Win_Pro_10_1703_64BIT_ChnTrad_MLF_X21-36716.ISO
Hi Ahsan, While I accept this may not be the forum to discuss Applications, I posted the resolution here because the behavior is exhibited after updating to this Windows (Build 15063). Hence I considered it is Windows problem, but may be it should be discussed in the Office forum for the benefit of other users.. However, check for spelling mistakes, existing Paths, Drives and Folders and don't remove the quotes and spaces as below.. Mine looks like this and it works, you could use cut and paste (including qoutes) if your office is installed in the C drive and Excel.exe is in Office 16: "C:\Program Files\Microsoft Office\Office16\EXCEL.EXE" "%1" Please notice that if you have installed Office x86 on Windows 64 bit, then your path would be in \Program Files (x86)\. P.S. I hope you saved (exported) your registry keys before making changes to them!! Good luck,
The fastest and easiest route to completely remove it would probably be to use install_wim_tweak and type install_wim_tweak.exe /o /c "Windows-Defender" /r You could also use PShell/dism to remove them individually: Spoiler Windows-Defender-AM-Default-Definitions-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-AppLayer-Group-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-AppLayer-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-AppLayer-Group-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-AppLayer-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-AppLayer-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-CloudClean-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Core-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Core-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Core-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Management-Group-amcore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Management-Group-onecore-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Defender-Management-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Management-MDM-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Defender-Nis-Group-Package~31bf3856ad364e35~amd64~~10.0.15063.0 Windows-Shield-Provider-Core-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0 Windows-Shield-Provider-Core-Package~31bf3856ad364e35~amd64~~10.0.15063.0
few times my mail app comes up with error message google settings are out of date. I have to configure it again to sign in to my gmail account. Same thing happens with yahoo mail to. Has that happened to anyone else before
I used install_wim_tweak and it successfully removed the app but now I can't use Edge! Do you know a way to get back the old calculator without having to install the Old Calculator program? I want it the way it was in Windows 7 (it didn't appear in the installed programs list).
I personally remove Edge, too, but I ran the command on one of my testing VMs and had no problems using Edge after. That said, re-installing the Edge package is simple, anyways. What "old calculator"? You mean the Win32 calculator that LTSB has or the actual calculator app? Run install_wim_tweak /o /l and it will put a .txt file of all the packages installed on your system and see if Edge it still there. If so, a sfc /scannow may fix it.