Bug in WR v4.01

[Willy2]

- In repair #18 the program stalls. This repair opens on my Win 7 system a MSDOS windows and then tries to stop the WMI Service. But then a question pops up. The question is something along the lines of "When this Service is stopped then 2 other Services (Security Center, IP Helper) are stopped as well. Do you want to continue ? (J/N)". Then the MSDOS waits until I have pressed either the "J" or "N" key on my keyboard.

- Solution for this problem ??? Add the "/y" switch to the (multiple) commands "net stop winmgmt" that are in that repair.

[Boggin]

It sailed through when I ran the Pro version on my Win 7 - it was just the end result that I had problems with, but someone else has reported getting a prompt to continue which I think Julian is looking into.

[Willy2]

@Boggin & @Julian: do the following:
1) Restart your Win 7 system and only run repair #19 (Repair VSS). Does this bug show up ?
2) Restart your system and run 2 repairs: #5 & #19. does the bug show up ? I assume it won't.

When "Security Center" and "IP Helper" are running then this message is showing up. But repair #5 stops the WMI Service using a command WITH the "/y" switch. The "/y" switch surpresses the question (I assume that the "/y" switch gives a "Yes" answer to the question) and simply stops those 2 Services ("Security Center" & "IP Helper") as well. And then running repair #19 doesn't pose that question because these 2 Services have already been stopped by repair #5. That's why - IMO - the "/y" switch is so important.

- The story above gives a clue what to focus on, what to test.
- I am NOT surprised to see this bug pop up because the program code for #19 has been changed (relative to WR versions v3.xx).

[Boggin]

Well if running the default repairs on my Win 7 doesn't baulk, I can't see the point of doing that on mine.

I think Julian passed this onto Shane when he was dealing with the other member, but don't know what the outcome was.

[Willy2]

- The message is that when one runs #19 for the first time (after a restart) then this problem pops up. Every next time repairs #19 is run this bug doesn't show up anymore because the Services "Security Center" & "IP helper" don't run anymore.

[Willy2]

- BTW, I also have a Win 7 PRO system.

[Boggin]

I'm just running Win 7 x64 Home on a Toshiba laptop as well as Win 10 on two other machines upgraded from the same, but I don't think Toshibas like WR.

I ran WR on one of the Win 10 laptops and Event Viewer recorded 1453 Errors after the reboot so I did a repair install.

That isn't the only thing that doesn't work on my Toshiba Win 7 though because when I trialled a repair install, it got so far and then rolled back - it rolled back from the same point on a second try.

[Willy2]

- Then pass this on to both Shane & Julian. I know that they are able to confirm what I reported.

[Willy2]

- Here's how see what''s going on:

- Restart system.
- Run repair #19. The user will be prompted whether or not those 2 Services (Security Center, IP Helper) should be stopped. Choose "Yes" to stop those Services.
- Run repair #19 again. The user won't be prompted again.
- Start the 2 Services by typing the following commands in a MSDOS windows with Admin rights:

        net start wscsvc
        net start iphlpsvc

- run repair #19 again and the user is prompted (again) whether or not these 2 Services should be stopped.

- Adding the "/y" switch to the "net stop winmgmt" command solves this "prompting problem".

- This issue brings up another question: Shouldn't these 2 Services be re-started after being stopped (no matter what) ???

[Boggin]

I've already said that I can't replicate on my Win 7 as the repairs run though without any prompts.

I've passed this thread onto Shane.

[Julian]

shane has this figured out and it will be added to the next version in an update

[Willy2]

    

[Willy2]

- And it's fixed in WR v4.02