J
James George
on two different machines, both having all updates and
antivirus running effectively, upon immediate reboot
after using this 'tool', system wouldnt connect to the
internet on both, AND bootup took 2 minutes longer than
normal , was the only common effects. on first system, i
got rpc error with 60 second to shutdown, no taskbar, no
items would load/boot/start and it took me 10 hours to
fix this system. on second system, taskbar came up, i
got a winsock2 error, and everything worked except no
internet connectivity, i immediately used system restore
and set it back prior to the scan.
what i want to know is, if this is microsofts scanner
working on its OS knowing the code, unlike other software
developers, WHY CAN'T THEY MAKE IT WORK BEFORE
RELEASSING? i am sure they tested this on many systems,
but on 2 of the 3 i put it on, i would say it failed.
luckily for me i am good at backwards engineering
microsofts failures.
thank you for any suggestions, other than do not use it
while its in beta.
antivirus running effectively, upon immediate reboot
after using this 'tool', system wouldnt connect to the
internet on both, AND bootup took 2 minutes longer than
normal , was the only common effects. on first system, i
got rpc error with 60 second to shutdown, no taskbar, no
items would load/boot/start and it took me 10 hours to
fix this system. on second system, taskbar came up, i
got a winsock2 error, and everything worked except no
internet connectivity, i immediately used system restore
and set it back prior to the scan.
what i want to know is, if this is microsofts scanner
working on its OS knowing the code, unlike other software
developers, WHY CAN'T THEY MAKE IT WORK BEFORE
RELEASSING? i am sure they tested this on many systems,
but on 2 of the 3 i put it on, i would say it failed.
luckily for me i am good at backwards engineering
microsofts failures.
thank you for any suggestions, other than do not use it
while its in beta.