/build/static/layout/Breadcrumb_cap_w.png
06/04/2018 947 views

Hi Everyone,

Has anyone seen the issue with Windows 10 Pro - Build 1803 (or other), where Internet Explorer cannot be set as the default browser? No errors, it just doesn't appear as an available option via default programs or when trying to associate a program with a specific file type. I will see something like the screenshot below:

wCQVUh.png

In the past, I have not changed default programs prior to sysprep. I will then use a DISM command as a post task which has worked perfectly up to now. Prior to sysprep, it does appear as an option to select as default, however upon testing it does not appear as an option once imaged whether you select as default or not beforehand.

Otherwise, IE works perfectly fine. No issues launching it or using it.

Note, if I install any other browser; Chrome, Firefox, etc these will appear as available options. I know Microsoft are pushing Edge as the default browser, but seems odd that Chrome, Firefox etc can be set as default but not IE.

Has anyone else seen this? Any suggestions or solutions?

Thanks.

6 Comments   [ + ] Show comments

Comments

  • It looks like that DISM command may be doing something.

    I checked my refreshed Device with the 1803 ISO, and I see IE as an option.

    Are you running your DISM commands from a 1803 PE ADK?

    Could you share it with us?
    • Thanks again for your help. Ended up being an issue with the Unattend file. The .xml was fine for other builds but I guess not 1803. Created a new one and had no issues after that.
  • It actually happens whether I run that DISM command or not. So I just tested applying the image with no additional tasks and it is not an option either. However, I went back to my last check-point prior to sysprep and it was an option before I sysprepped it. Is it possibly a sysprep issue? Note, my unattend file was created a few months back for 1703/1709 so wondering if that has anything to do with it? I'm going to create an unattend with the latest tool from K2000 and see if that changes anything. I'll let you know how that goes. Thanks.
  • Hi Maherfed,

    Microsoft is doing you a massive favor in not allowing the least secure still commonly used web browser to be your default. My advice is you only use internet explorer on the services that require it. That being said you should be able to override this in HKEY_CLASSES_ROOT by adjusting the file associations and protocol handlers.

    Cheers,
    Christian
  • Thanks for your suggestion. We've always used IE as default but it sounds like we need to revisit. Thanks again.
  • Hi Maherfed, have you had other issues with sysprep on 1709 and up? It was working perfectly fine on 1607 until then we attempted to use it on 1709. It acts like it runs but Windows stops at the screen asking to choose language, keyboard, region etc. My apologies if this is off topic but I've been banging my head trying to figure it out. If anyone can help or guide me in the right direction I'd be greatful. I'm placing the unattend.xml file on the desktop with the sysprep executor, could that be the issue?
  • Hi TruckNorris, no problem. I didn't see any issues of that nature. That sounds like it is sysprepping the image back to the manufacturers default and possibly just running sysprep.exe with no customizations, ie it's not recognizing or pointing to the unattend file correctly.

    Are you using the same unattend file as with 1607? I had been doing that (used 1703 unattend on 1803 image) and it resulted in that strange issue I had above. To rule it out, I would create a new unattend via the Kace tool with the latest version (K2000 - Tools - Sysprep Creator Wizard (I only check the unattend creator and not executor).
    Once you generate the unattend.xml , copy it to C:\Windows\System32\Sysprep . Then I have a batch file saved in the same location with the below content:

    REM Syspreping Windows 10 64bit
    @echo off
    c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend:unattend.xml
    exit

    Then I just double click the batch to launch the process.

    Note, you can save the unattend anywhere, you just need to have that location reflected in the batch file or command line, for example:
    C:\Windows\System32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend:C:\users\administrator\desktop\unattend.xml

    Hope this helps.

All Answers

0
Ended up being an issue with the Unattend file. The .xml was fine for other builds but I guess not 1803. Created a new one and had no issues after that.
Answered 06/07/2018 by: maherfed
Yellow Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share